Privacy Policy

The data RapZap keeps

We designed RapZap to run on very little personal information. Making a video never asks for your name or email. The full list of what we do hold follows.

• The photos you upload. We re-save every one in a standard image format, which wipes embedded metadata such as the camera model or GPS position, and we delete the original upload as soon as that re-saved copy exists.
• The clip generated from them.
• A session cookie with no identity attached: just a random token, good for 30 days, that connects your browser with its drafts, clips and credit balance.
• Records of payments. Your card details go to Stripe, not us; we get back only the status, the amount, the currency and Stripe’s reference numbers, and never the whole card number.
• Lightweight product events like “photo uploaded” or “video downloaded”, stored against the anonymous session. No photo, clip link or email address is ever part of an event.
• Your arrival details: any campaign tags on the link that first brought you to RapZap (utm_source, for example) and the referring site’s address minus its query string. A first-party cookie holds this for 30 days; when you start a video we copy it onto your anonymous session, and it travels to Stripe with your checkout.
• Usage analytics collected by Google Analytics, among them the pages you visit, your device and browser type, an approximate location estimated from your IP address, plus the product events already listed. To distinguish one visit from another, Google Analytics sets cookies of its own.
• Operational data required to keep RapZap running and secure, for instance server request logs and error codes.
• The contents of any support message you send, such as your email address and what you wrote.

Purposes

• Generating your clip, holding it for you and delivering it.
• Charging payments, crediting and debiting your balance, and restoring credits after a failed generation.
• Spotting abuse, upholding the Acceptable Use Policy and keeping RapZap secure.
• Learning from totals, never individuals, which steps trip people up, so we can fix them.

We never sell personal information. Your photos and clips are kept out of advertising and are never fed into AI model training.

Kie, fal.ai and the AI models behind them

To render a clip, RapZap passes your photo or photos to Kie, our AI provider, together with fixed instructions describing the scene. Kie saves copies of those files on a file host it runs and executes the job using underlying models: OmniHuman and Seedance from ByteDance, and Nano Banana from Google, each built and operated by its maker.

Hotel Lobby and Bulin 47 clips have one extra route. If Kie cannot finish the animation step, the identical job is handed to fal.ai, which runs that same OmniHuman model from ByteDance. What fal.ai gets is the stills Kie created from your photos, a mask that marks where the people are, and the audio track, all downloaded by fal.ai from Kie’s file host.

Outstanding Tiny Desk AI clips use fal.ai as the first choice for every shot that has singing in it, running ByteDance’s OmniHuman, and fall back to Kie. Here fal.ai gets the stills Kie created from your photos and a brief excerpt of the song, again downloaded from Kie’s file host.

Your photos may be processed by these companies on servers located abroad. Kie, fal.ai and each model maker operate under their own terms and keep data according to their own retention rules, none of which we control. Every deletion deadline in this policy describes our own storage and nothing beyond it.

Stripe, Google Analytics and our hosts

Payment processing is done by Stripe, which follows its own privacy policy. Google, through Google Analytics, processes site usage information on our behalf, subject to its own terms and privacy policy. The only thing analytics events are tied to is a random video ID; your photos, clip files and email address are never attached. We also depend on infrastructure companies that host the site, its database and its private file storage, and they handle data for us strictly to keep RapZap working.

Deletion schedule

• Photos you upload: wiped within 24 hours once the video they belong to has finished, failed or been blocked.
• Abandoned uploads and drafts that were never run: wiped within 24 hours from when they were made.
• Finished clips: wiped 7 days from the moment they are ready.
• Anonymous session cookie: lapses at 30 days.
• Arrival (referral) cookie: also lapses at 30 days.
• Cookies set by Google Analytics: lapse within 2 years at the latest. The analytics data itself is held for whatever retention period our Google Analytics account is set to, capped at 14 months.
• Records of payments and credits: retained while our accounting, tax, fraud-prevention or legal duties still call for them.

Private links, not public posts

RapZap never puts your photos or clips on public display. Each clip page and download link works solely in the browser session that made the clip, which means passing the link along lets no one else in. When you want others to see it, save the file and share the file itself.

What you control

• Skip uploading and no session cookie is created, though the generator cannot run without one.
• Google Analytics can be switched off with your browser’s privacy controls, with a content blocker, or with Google’s official opt-out add-on at https://tools.google.com/dlpage/gaoptout. The generator keeps working either way.
• Wiping the cookie from your browser settings is possible at any time, but past drafts and clips from RapZap will then no longer open.
• Email us if you want to know what personal data we hold or would like it removed ahead of schedule. With no accounts to search, we may ask for a pointer such as the address of your video page.

Under-18s

RapZap is not designed for children, and the Acceptable Use Policy bans photos showing anyone younger than 18.

Keeping data safe, and revisions

Photos and clips sit in private storage and are only ever served back to the session they belong to. Perfect security does not exist anywhere, which is why we collect little and delete early. Revisions to this policy may happen; check the date at the top for the version currently in force.

Contact