Privacy Policy | Rain Dance Trend
How Rain Dance Trend handles accounts, inputs, task records, checkout, storage, support and measurement.
Last updated: 2026-11-15
Scope and contact
Rain Dance Trend is operated by John Yan in Hong Kong. Contact support@raindancetrend.com for privacy requests. When Pricing enables checkout, Stripe hosts card entry and this application stores the order records needed to reconcile a payment. If checkout is unavailable, no payment is collected.
Accounts and support
When Google sign-in is enabled, Google supplies account details such as your name, email address and profile image. Account and session records support login and access controls. Support messages contain the information you choose to send and are handled through the site's Migadu-hosted mailbox. Do not send passwords, full payment-card details or unnecessary sensitive information.
Selected photos and generated media
In an enabled upload form, selecting a file can upload it before you press Generate. Removing the file from the form or signing out does not prove that the stored copy has been deleted. Only use images you have the rights and necessary permissions to process.
The planned two-subject generation workflow sends the selected image references, scene instructions and workflow reference material to fal for AI generation and video processing. Its tested model path uses MiniMax H3 Reference-to-Video. The final enabled provider route must match the information shown here; internal experiments using other providers are not public functionality.
The service records task identifiers, input and output references, instructions, status, errors, timestamps and credit changes. Uploaded media and persisted outputs use configured Cloudflare R2 storage; account, task and order records use Cloudflare D1. A media URL may be accessible to anyone who obtains it. An account-only history screen does not make the underlying media URL private. Do not upload confidential material or treat saved results as an encrypted private archive.
Payments when enabled
Stripe is the payment processor. Card information entered in Stripe-hosted checkout is handled by Stripe. The application receives order and transaction information needed to reconcile payments and credits, including amounts, currency, status and processor references.
Measurement and operational records
The application includes first-party visitor attribution and product events. These can record the landing page, referrer, campaign parameters, advertising click identifiers, device or browser context and actions such as registration, checkout or generation. A visitor identifier can be associated with an account after sign-in. The sf_visitor_id cookie has a configured lifetime of 180 days; that does not set the retention period of related server records.
Microsoft Clarity is configured for browser interaction measurement and session recordings. The Plausible integration uses our self-hosted service at plausible.online for pageview measurement when the production site configuration enables it. The basic Plausible script sends the visited page URL, referrer and browser context; this integration does not enable its file-download, outbound-link, custom-event or revenue extensions. These services are separate from first-party account, payment and task records. See Cookies and measurement for the current browser controls and limitations. Blocking these scripts does not disable first-party operational records.
Purpose and service providers
Information supports requested account and generation features, saved history, payment and credit reconciliation, troubleshooting, abuse prevention and responses to support or rights requests. It may be retained or disclosed to meet legal obligations or resolve disputes. Cloudflare provides hosting, database and media storage; Google provides sign-in; fal is the planned generation and processing provider; Stripe handles enabled checkout; Migadu hosts support email.
Read the providers' notices for their own processing: Cloudflare, Google, fal, Stripe and Migadu. We do not extend any provider's account-deletion deadline into a promise about all uploaded media, or promise that every processing route excludes model-improvement uses.
Retention, deletion and international processing
We have not established a fixed automatic deletion deadline for all account records, uploads, outputs and provider copies. Saved media is not guaranteed permanent storage. Processing can occur internationally; we do not promise a particular data-residency region.
To request access, correction or deletion, email support with your account and affected task or file references. We may verify authorization. A request requires review of database, storage and relevant provider records, subject to applicable legal, security and accounting requirements. Removing a history entry or clearing cookies is not proof that every copy has been erased. Where data must be kept, the response should identify the affected category and reason. Applicable mandatory rights remain available.
This service is intended for adults. Do not submit prohibited or sensitive content. The notice will be revised when actual processing changes.
PVUV full-site analytics
PVUV.ai loads on every rendered page, including account, billing, generation-history, administration and query-bearing pages, to measure use and distinguish people, bots and crawlers. It can process the page route and relevant query parameters, referrer and campaign/click identifiers, country, device and browser information, entry and exit activity, 404s, downloads, outbound clicks and authenticity signals.
PVUV uses first-party cookies and may use local storage for visitor identity, sessions and attribution. PVUV states that it stores IP addresses only as truncated hashes and fingerprint data as hashes or conclusions rather than raw fingerprints. Any separate analytics preference does not disable this full-site measurement. Do not place prompts, media URLs, credentials, payment details or other secrets in URLs.