About & policies

Privacy policy

How Dime Dime Baby AI handles account data, uploaded photos, generated videos, browser storage and privacy requests.

Site editorial team · Updated

Who this policy covers

This policy covers Dime Dime Baby AI at dimedimebabyai.pro. Send privacy questions and requests to support@dimedimebabyai.pro. Include the account email and a task reference when relevant so the records can be located.

Information processed for the service

Account information includes the name and email you provide, sign-in credentials or the account identifiers supplied by a sign-in provider, and session records. These support authentication, account access and service-security checks.

A submitted generation includes your selected photo, the fixed scene instructions, task identifiers, status, credit charge, errors and the resulting video. Support requests include the message and any attachments you choose to send. Where checkout is enabled, order records include the product, amount, currency and payment status.

If generation-completion emails are enabled, task records also contain the delivery address, the message prepared for sending and delivery-status information. An accepted email submission records the email provider’s response. Check the task in your signed-in account for its latest result.

Requests to the website can include an IP address, browser information and technical diagnostics. Avoid sending identity documents, passwords or full card details in a support message.

Where a generation goes

When you confirm a generation, your photo is uploaded through Kie.ai and supplied to ByteDance Seedance 2 together with a motion reference and scene instructions. The provider needs access to those inputs to produce the video. Its processing and retention are also governed by its own terms.

Your uploaded photo passes through the application’s request memory to Kie.ai. The application records task information, including the fixed prompt, recipe parameters, identifiers and result-storage details, in its database. Completed video files are saved in project storage. The result endpoint checks the signed-in account before serving a file. Hosting, database, storage and email services process the information needed for their parts of the service.

A payment provider processes checkout information when you make a purchase. Its payment page explains its handling of payment details. Service providers may process data in countries different from your own. Contact support if you need provider or transfer information before submitting personal media.

Safety screening and human access

Waffo Prompt Sift receives the fixed scene text for the pre-generation safety check. Photo and video generation inputs follow the Kie.ai data flow described above.

Authorized reviewers can access the completed video in private storage to assess it before release. Safety records include prompt and file hashes, policy version, timestamps, decision references, reason categories and pseudonymous account or reviewer identifiers. These records support enforcement, appeals and investigation of a delivery or credit issue.

The review queue expiry controls the delivery decision and credit restoration. File and safety-record retention follow the purposes and manual removal process described below. Provider-held copies have their own lifecycle.

Cookies and this browser

Authentication uses session cookies to keep you signed in. The generator stores a request identifier in this browser’s local storage so it can look up the latest task after a refresh. Your selected photo is previewed in the browser before submission.

The pricing page stores a purchase request reference, pack details and any saved checkout link in this browser under the signed-in account to help resume an interrupted purchase. Card and payment credentials are entered through the payment provider’s checkout.

Where optional analytics is enabled, the site’s consent controls explain the available choice. Analytics configuration must keep account details, photos, private media links and task identifiers out of analytics events. You can use browser settings to clear site storage or restrict cookies. Clearing local storage can remove task-recovery details while the server-side task record remains.

Retention and deletion requests

Account, task, support and transaction records are retained according to their service, security, dispute-resolution and legal-recordkeeping purposes. Media stored by the generation provider has its own lifecycle. The upload receipt’s expiry controls submission permission and does not establish deletion of the photo.

Result files currently remain in project storage until an operator removes them. Media removal is handled manually through support. The provider-held input photo has a separate lifecycle that requires the provider’s handling.

Removal requests currently go through support. Identify whether you mean an uploaded photo, a generated video, account records or a copy on your device. Ask support for the current retention and deletion arrangements if a particular deadline matters to you. The timing for removal depends on the records involved, any provider-held copy and applicable obligations.

Requests are reviewed after proportionate identity verification. Some records may need to be retained to meet legal obligations or resolve a dispute. We will explain relevant limits in responding to a request. A file downloaded to your device or shared elsewhere requires separate handling by you or the destination service.

Your choices and rights

Depending on the law that applies, you may have rights to access, correct, delete or receive a copy of your data, and to object to or restrict certain processing. You may also have a right to withdraw consent or complain to a data-protection authority. Send a request to the support email above and describe the right you want to exercise.

The generation service is intended for adults. If you believe a child’s data or an unauthorized photo has been submitted, contact support with enough detail to locate it, using the content-report instructions. The date shown on this page identifies the current policy revision.