Ritorno a casa

Privacy Policy

How photos, account details and payments are handled.

Aggiornato: 2026-10-19

Raindance AI Video Generator is operated by Zhou Guowei, an individual developer based in China, under the TrendReel brand.

Current service

The Raindance AI trend refers to the Dave and Tems song and a two-person scene on a dock and sunset beach: one person waits while another sings. This site makes a new 15-second, 4:3 silent video from two adult photos. There is no rain, original song or original music-video footage. Account details, uploaded images, generation settings, job status and output locations are used to provide the service. Payment orders and credit transactions are stored to manage purchases and usage.

Service providers

Sign-in uses Google. We receive the Google account identifier, email address and basic profile details, such as your name and profile image, to create and authenticate your Raindance AI Video Generator account. Your Google password is not entered on this site.

The generator sends your photos and generation instructions to Kie, the configured AI provider. Kie receives a temporary photo upload before generation. Provider-held inputs, outputs and logs are subject to that provider's policies; deleting a video here does not instantly delete those copies. We do not make a promise about a provider's model-training practices.

When purchases are enabled, Waffo handles card entry and payment processing. This application stores order references, payment status and credit records; it does not collect full card numbers through its own forms.

For the paid two-photo video sequence, our server prepares each photo and sends each separately to Kie as a character reference for one video generation task. A free preview, when submitted, separately combines the two people into a scene still; that still is not a video frame. The service does not provide an original song or music-video footage, ask for a voice recording, or clone your voice.

Access and retention

When TrendReel sites share an account system, your account, credit balance, orders and stored creations can be available on those sites after you sign in separately. Login cookies are limited to the current domain.

Accounts restrict access to generation jobs and credit history. Sign-in and language preferences use cookies or browser storage. The generators temporarily save photos and editing choices in this browser tab so you can continue after signing in or paying. If you press the create button and are sent to sign in or to Checkout, the tab also keeps a short note that you had confirmed permission and pressed the button, so the same request can continue when you return; it is used once, expires within an hour, and is cleared if you untick the permission box. A plan you choose while signed out is remembered the same way to open its Checkout after sign-in. Removing the photo, signing out, or switching accounts clears that saved photo draft; browser session restoration follows your browser's settings.

For a submitted free preview, we save both prepared input photos and the original and watermarked preview images in private R2 storage. The two photos and preview images are deleted after 24 hours by the hourly cleanup job. Outside this preview flow, the generator does not save input photos in our database or R2 storage. Completed videos and edited images are archived to private R2 storage, and account-authorized downloads use short-lived links. We do not currently run an automatic expiry job for those stored outputs.

In My videos or My creations, you can delete a completed or failed job. Once deletion succeeds, its stored R2 output copy is removed, its media locations are cleared, and the job disappears from your account. An active generation or file transfer must finish first. If storage is temporarily unavailable, deletion reports a retryable error rather than claiming success. Previously downloaded files cannot be recalled. Minimal job identifiers, account records and billing/credit history remain; this is not an account-deletion tool.

We use a signed first-party session cookie to remember the initial source category and the first public page visited. Only a fixed list of public page paths is recorded; full URLs, query strings, referral URLs, IP addresses, private page paths, photos and prompts are not collected by this feature. Unknown source labels are reduced to “other”. The cookie has no persistent expiry and follows the browser's session handling.

Our private operator report counts public visits, photos selected in the browser, registrations, plans shown (the plans dialog or the pricing page), Checkout sessions started, generation requests, confirmed results and paid orders. These records use a pseudonymous session identifier, source category, public landing path, event type and time; they do not contain your account ID or email. Selecting a photo records only that action, not its contents. Source categories still link to accounts at registration. Orders keep the session attribution needed to link confirmed payments. An order also records which public page of this site its Checkout was started from and whether that was the pricing page, a pricing section, or the plans dialog; this comes from the same fixed list of public page paths and is not sent to Waffo. This is limited first-visit session attribution, not tracking across websites. We do not send these records to advertising services or currently run an automatic event-expiry job.

New collection respects Global Privacy Control or Do Not Track. Browser signals or blocking may therefore leave gaps in the report. Results of a generation or payment already started can arrive later and remain associated with its original session. Internal tests are separated from ordinary traffic; session counts are not a count of distinct people.

Google Analytics

When analytics is enabled, we use Google Analytics 4 for visits to public pages on raindancevideoai.com. Our integration sends the canonical public page address and a fixed page label; it removes URL query strings and fragments. Recognized source channels are reduced to fixed names and referral origins, without referral paths or query strings. Unknown referral addresses and campaign text are not forwarded. Google receives network and browser information as part of processing these requests and uses an Analytics browser identifier; our configuration uses session cookies rather than a persistent cookie expiry.

We do not send account IDs, email addresses, photos, prompts, job IDs, private account or administrator page addresses, or purchase details to GA4. Automatic enhanced measurement, advertising personalization and Google signals are disabled. Private-page visits, internal test sessions, Do Not Track and Global Privacy Control are excluded. Our first-party operational report above remains separate from GA4; browser blocking and these exclusions can cause differences between reports. Google's handling of Analytics data is described in its privacy policy.

Only upload photos you have permission to use. Do not submit sensitive documents or information unrelated to the requested effect.

Requests and operator details

For questions about your data, access, correction or account deletion, email [email protected]. Signed-in users can also submit a text-only request in Support tickets and read replies there. We verify account ownership before handling requests affecting account data. Records needed for payment accounting, disputes or applicable legal obligations may be retained after an account-deletion request.

Do not include passwords, payment card details or sensitive documents. Deleting a work does not confirm that provider-hosted images or videos have been deleted. No response-time commitment is published here.