Privacy for your photos and videos.

The current service

Dime Dime Baby AI uses one portrait with a prepared performance clip and provides a private result page. One-time credit purchases, monthly subscriptions and video generation can use an anonymous browser session. That session controls access to its private media, wallet and subscription management until an account is saved; clearing site data or changing browsers or devices can lose access without canceling a subscription.

Your browser displays selected photos before submission and keeps them in local browser storage for up to 24 hours, so they can remain available after checkout. They are removed when you sign out or submit a generation. Selecting a portrait or opening the review dialog does not send it to the generation provider. Submission occurs when you confirm Generate.

Photos, source clips and results

Submitted portraits are processed into usable image references and stored with the source segment for the generation request. The resulting video is checked, paired with the original audio and saved for playback and download.

The current workflow uses private storage by default. Portrait references and private result pages are not published in a public gallery. The dance demonstration is a separate public asset.

A request identifier lets you return to a saved result. Keep private result links and downloaded files to yourself unless you intend to share them. Once you publish or forward a downloaded video, copies are outside this site’s control.

Google sign-in

If you choose Continue with Google, Google provides an ID token for authentication. Supabase verifies that token and may store your Google account identifier, verified email address, name and profile image when available. We use this information to create or sign in to your Dime Dime Baby AI account, associate your credits and private videos with it, and show basic account details. Google account information is not sent to the video generation provider or used to train the video model. We do not request access to Gmail, Google Drive, or other Google account content.

Usage analytics

The site can store first-party product events in Supabase, including page and studio visits, anonymous visitor and 30-minute session identifiers, referring domain and campaign tags, coarse device type and country, studio settings, checkout state, verified purchases, generation outcomes, downloads and optional result feedback. Signed-in activity can be linked to the account identifier so we can understand conversion, reliability and repeat use.

When Google Analytics is enabled, the site also sends page views, selected browser interactions, purchase button clicks, and verified checkout returns to Google Analytics 4. A confirmed return includes the pack, amount, currency and a transaction reference for purchase measurement and deduplication. We do not intentionally include your email address, portrait filenames or files, source footage, generated video, full referrer URL or raw IP address in our first-party product-event records. Google may receive technical information supplied by your browser and processes its analytics data under its own terms.

Service providers

An AI video processing service processes the video and portrait references to generate the edit. Supabase stores request records, and Cloudflare R2 stores submitted and generated media. The workflow provides temporary access to input files for generation rather than making the storage bucket public.

These providers may process or retain data under their own terms. We do not promise that they retain no copies or use no submitted data beyond what their policies allow. Consider those terms before submitting sensitive material.

Supabase manages anonymous browser sessions and registered accounts. Stripe handles live one-time credit purchases and monthly subscription payments. We store payment references, the checkout email when Stripe supplies it, subscription references and a credit transaction history, rather than card numbers. A Stripe checkout email does not by itself grant access to a guest wallet or private video.

Retention

Inputs, request records and completed outputs can remain in private local or cloud storage so that saved requests can be checked and results recovered. A fixed automatic deletion schedule is not currently active.

Removal may require action by the project operator. Active or unresolved requests may still need their input files until processing and provider accounting are settled. Deleting a local browser reference does not remove stored media or cancel an accepted request.

We do not promise seven-day photo deletion or thirty-day video deletion. Contact support with the relevant request reference to ask about removal.

Your choices

You can replace or remove selected portraits before submitting and leave the review dialog without generating. Confirm the person’s permission before using their image.

The account page shows your credit balance and activity and lets you sign out. Stored requests may need separate manual removal. The contact page provides the monitored support address.

Do not place API credentials, payment details or portrait files in a public message when asking for help. Share only the request reference needed to identify the issue through an appropriate private support channel.