Privacy Policy
How we collect, use, process, and safeguard your personal information and creative data.
Last updated:
Summary & Google API Compliance Notice
dimedimebaby (“we”, “our”, or “the Application”), hosted at https://dimedimebaby.org, is an AI viral dance video animation tool designed for entertainment and social media creators. We respect your privacy and enforce strict compliance with the Google API Services User Data Policy and the Google APIs Terms of Service, including strict prohibitions on Non-Consensual Intimate Imagery (NCII).
1. About dimedimebaby and Application Purpose
dimedimebaby is a web application that enables users to upload a single consensual portrait photo and animate it into a stylized, rhythmic 9:16 vertical “Dime Dime Baby” meme dance video. The primary purpose of the application is harmless social media entertainment, celebratory memes, and video creation for platforms like TikTok, Instagram Reels, and YouTube Shorts.
Visitors can freely browse all sections of our website — including dance motion templates, feature breakdowns, how-it-works guides, pricing packages, FAQ, and compliance guidelines — without needing to log in or create an account.
2. Information We Collect
We collect only the minimum information necessary to deliver our services:
- Google User Data (Google OAuth 2.0 Sign-In): When you choose to authenticate with Google, we access only non-sensitive identity scopes: your primary email address (
email), public display name (profile), profile avatar picture URL, and unique Google account identifier (sub). We never request access to your Google Drive, Google Photos, Contacts, Gmail, Calendar, or any other restricted Google scopes. - User-Uploaded Photos: When you submit a generation request, you upload a single portrait image. This image is processed exclusively in temporary computer memory to extract keypoint poses and animate the selected dance template.
- Account & Transaction Details: If you purchase video credits, our authorized third-party merchant of record (Dodo Payments) collects necessary billing information. We never store credit card numbers on our servers. We store order IDs, timestamp, and credit balance associated with your dimedimebaby account.
- Technical Telemetry & Cookies: We collect standard technical connection logs (IP address, browser user-agent, operating system) and use essential HTTP-only cookies solely for session security and fraud prevention.
3. How We Use Google User Data and Collected Data
We use your information exclusively for the following lawful and explicit purposes:
- To authenticate your identity, create and maintain your dimedimebaby account session.
- To display your display name and avatar inside your personal account dashboard.
- To associate purchased credits and generated dance videos with your account so you can view and download them.
- To communicate critical transactional notices (such as order receipts or generation status updates).
- To monitor for security, prevent automated abuse, and enforce our acceptable use policies.
4. Google API Services User Data Policy Compliance & Limited Use
dimedimebaby's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- No Sale of Google User Data: We do NOT sell, rent, lease, or monetize Google user data or user-uploaded content to data brokers, advertisers, or any third parties.
- No Generalized AI Model Training: We do NOT use Google user data or uploaded user photos to train, retrain, fine-tune, or develop generalized artificial intelligence, machine learning, or facial recognition foundation models without explicit affirmative consent.
- No Advertising Use: Google user data is NEVER used for serving advertisements, personalized promotions, or retargeted ad campaigns.
- Strict Human Access Limits: No human employees or contractors are permitted to inspect Google user data, except where required by law, with your affirmative consent for technical support, or in an aggregated and de-identified format for cybersecurity operations.
- Limited Infrastructure Transfer: Google user data is only transferred to secure infrastructure providers (specifically Cloudflare Workers hosting and D1 database) strictly necessary to run the web application, bound by strict confidentiality and data protection obligations.
5. Strict Prohibition of Non-Consensual Intimate Imagery (NCII) & Responsible AI
In strict compliance with the Google APIs Terms of Service and applicable international safety laws, dimedimebaby enforces a ZERO-TOLERANCE policy for AI-generated Non-Consensual Intimate Imagery (AI NCII) and non-consensual deepfakes.
Prohibited Activities: Users are strictly forbidden from uploading, creating, altering, or sharing:
- Any sexually explicit, nude, partially nude, or sexually suggestive imagery.
- Any non-consensual depiction or likeness modification of another person (AI NCII).
- Photos of public figures, political figures, or celebrities without verified authorization.
- Any imagery depicting minors (children under 18 years of age) without verified parental or legal guardian consent.
- Content designed to harass, defame, bully, intimidate, or exploit any individual.
Google APIs Safety Affirmation: Google APIs (including Google Sign-In) are strictly used for user authentication and account management. Google APIs are NEVER used to generate, store, process, facilitate, or distribute AI NCII or any prohibited content.
Mandatory Consent Requirement: You warrant and represent that you own all rights to any photo you upload, or have obtained express, informed, and documented consent from the depicted individual.
Automated Moderation & Immediate Termination: Every uploaded photo undergoes real-time automated content moderation to detect and reject nudity, explicit material, or unauthorized likenesses. Any user attempting to upload prohibited or NCII content will face immediate, permanent account termination, forfeiture of credits, and referral to law enforcement agencies where legally mandated.
6. Data Retention and Storage
- Account Data: Retained for the duration of your active account to maintain your library and credit records.
- Uploaded Input Photos: Stored in Cloudflare R2 for processing and scheduled for automatic deletion 15 days after upload.
- Generated Videos: Stored in Cloudflare R2.
Videos are stored for 15 days after they are saved, then automatically deleted. Download yours before it expires.
Your generation and credit records remain available after the video is deleted.
7. User Rights, Data Deletion, and Revoking Permissions
Under GDPR, CCPA, and Google User Data Protection standards, you have full ownership and control over your data:
- Right to Access & Export: You can inspect and download all your generated videos and account details in your personal dashboard.
- Right to Erasure (Data Deletion): You can delete individual videos in your dashboard. You may request complete deletion of your account, Google user data, and all associated records at any time by emailing support@dimedimebaby.org with the subject line “Data Deletion Request”. We will process and confirm your request within 30 calendar days.
- Revoking Google OAuth Access: You may disconnect dimedimebaby's access to your Google account at any time by visiting your Google Account Third-party apps & services permissions page.
8. Security Safeguards
We implement industry-standard administrative, physical, and technical controls to safeguard your data, including HTTPS/TLS 1.3 encryption in transit, Cloudflare WAF protection, encrypted cloud databases, isolated tenant storage buckets, and restricted least-privilege administrative access.
9. Contact and Abuse Reporting
If you have questions regarding this Privacy Policy, wish to exercise your privacy rights, or wish to report any content violation or suspected NCII abuse, please contact our team immediately:
Aggregate AI referral counts
We use Cloudflare Analytics Engine to count successful public-page requests with a recognized AI-service referrer. Each event contains only the service name, public page path, page language and a count. This measurement sets no cookies and records no IP address, account ID, full referrer URL, query string or uploaded media. These request counts help us understand how people discover our guides; they do not identify unique visitors or prove that an AI answer cited us.