Your photos tell a story.
They remain yours.

01

Scope and who operates the app

This Privacy Policy applies to the AI Baby Face Generator & Maker mobile application, its support interactions, and this policy website (together, the “Service”). The app is provided by its independent developer (“we”, “us”, or “our”).

By using the Service, you acknowledge the practices described here. If you do not agree, do not submit photos for live AI processing. During onboarding, you may fill missing parent slots with clearly labeled, fictional app-provided samples; generating with those samples still uses the normal Pro and Firebase AI processing flow.

02

Information collection and use

We limit processing to what is needed to provide the feature you request, maintain purchases, protect the Service, and diagnose failures.

Information you choose to provide

• Source photos. Parent, child, family, or maternity photos you select from your camera, photo library, or files.
• Creative settings. The mode, age, presentation, resemblance balance, or styling choices you select. These are creative instructions and are not used to verify genetics, identity, paternity, or health.
• Support communications. If you email us, we receive the email address and content you decide to send.

Information processed automatically

• Firebase installation and analytics identifiers, app version, operating system, device type, IP-derived network information, request timing, safety events, and similar operational data.
• Subscription product, entitlement, receipt or purchase-token data, transaction dates, store, country, and a random anonymous RevenueCat App User ID.
• Crash and performance diagnostics if those Firebase services are enabled in the released build.

03

Data processing for contract and app functionality

We process the limited information described above to:

• prepare photos and generate requested portraits;
• save, display, share, export, or delete creations at your direction;
• confirm Pro access, process purchases, and restore subscriptions;
• authenticate requests and prevent fraud, abuse, or unauthorized clients;
• remember onboarding and recover an interrupted local workflow;
• diagnose crashes and maintain reliability; and
• respond to support, legal, privacy, or security requests.

Where applicable law requires a legal basis, these activities rely on performance of the service you request, your consent or device permission, our legitimate interests in security and reliability, and compliance with legal obligations. You may withdraw a device permission in system settings, although the related feature may stop working.

04

AI features, image processing, and generated portraits

Photo access and preparation

The app opens the camera, photo library, or file picker only after you choose that action. The original image remains where you selected it. The app creates a compressed working JPEG in its own temporary storage, corrects orientation, limits size, and removes EXIF metadata from that working copy.

On-device preparation

The app converts working copies to JPEG, corrects orientation, removes EXIF metadata, compresses them, and enforces the 4 MB API-compatible size limit. It does not run a separate face-count, blur, lighting, duplicate, quality, or suitability classifier. Reference photos are sent for live AI processing only after you intentionally continue with Pro access.

Live Firebase AI processing

When you intentionally start a live personal-photo feature and have an active Pro entitlement, the prepared photos, creative settings, and an application prompt are sent to Google Gemini through Firebase AI Logic. Google processes these inputs to return a generated image or related response. Gemini's safety systems may evaluate requests and outputs.

The app uses Firebase AI Logic with Google's Agent Platform Gemini API (formerly the Vertex AI Gemini API). Under Google Cloud's current terms, Google will not use Customer Data to train or fine-tune AI or machine-learning models without prior permission or instruction. The specific service-side storage periods that can apply to these requests are stated in the Face Data and Retention sections below.

Fictional entertainment, not sensitive inference

Results are creative, fictional images. They are not genetics, paternity, pregnancy, medical, biometric, identity-verification, or factual resemblance results. We do not use submitted faces to recognize people across images or services.

Saving, exporting, and sharing

Every successfully generated portrait is saved automatically in the app's private application-support storage and appears in Creations. It remains there until you delete it or uninstall the app. Operating-system backups may retain or restore app data according to your platform and backup settings. Export to Photos, Files, or another app occurs only after you choose the relevant save or share action. The receiving app or service then applies its own privacy practices.

05

Face data: complete collection and handling disclosure

What face data the app processes

The only face data the app processes is visible facial imagery in a parent, child, family, or maternity photo that you deliberately select or capture, plus the synthetic facial imagery in the resulting fictional portrait. The app does not access Face ID or TrueDepth data and does not collect or create facial geometry, landmarks, depth maps, faceprints, biometric templates, or facial recognition identifiers. It does not use a face to identify, authenticate, or verify any person.

Why face data is used

Selected photos and creative settings are used only to provide the entertainment feature you request: generating a fictional future baby, age-journey, maternity, or family-resemblance portrait and applying Google's safety controls. Face data is not used for advertising, tracking, user profiling, identity verification, or inferences about genetics, paternity, pregnancy, health, or other sensitive facts.

Who receives it and where it is stored

After you see the in-app AI-processing disclosure and choose “Allow & Continue,” the metadata-free working photos, creative settings, and application prompt are sent over an encrypted connection to Google through Firebase AI Logic, using the Agent Platform Gemini API in the global location, solely to return the requested AI result. Google is the only external service provider that receives selected photos for this purpose. Face data is not sent to RevenueCat, Firebase Analytics, Firebase Crashlytics, advertisers, or data brokers. The app does not upload these photos to Firebase Storage, Firestore, or an app-operated remote photo database.

On the device, the app keeps a compressed, metadata-free working JPEG in app-owned temporary storage while the creation flow is open. The photo bytes may also remain in working memory during that open flow so you can retry or replace an input. A generated portrait is stored separately in the app's private local application-support directory.

Exact retention and deletion

• Device working copies: replaced or removed source-photo files are deleted immediately. Remaining working files are deleted when you leave the flow, generation completes or fails, or interrupted-session cleanup runs at the next app start. In-memory copies are released when the flow or app process ends.
• Saved generated portraits: retained in private app-local storage until you delete the creation in the app or uninstall the app. Copies you deliberately export are controlled by Photos, Files, backups, or the receiving app.
• Firebase AI Monitoring: sampled AI request and response content can include selected source photos, prompt and setting content, and generated output. It is stored in the developer's access-controlled Google Cloud Logging project and is automatically deleted after the configured 30-day retention period. This operational logging is used only to diagnose and secure the AI feature, not for advertising or model training.
• Google service processing: Google-published Gemini models may keep project-isolated inputs, outputs, and derived data in memory, not at rest, for up to 24 hours to improve service performance. If automated safety systems flag suspicious activity, Google may securely retain the flagged prompt for up to 90 days solely to investigate abuse. Google states that this data is not used to train or fine-tune its AI or machine-learning models.

Provider-side operational and safety records expire according to the periods above. Because the app has no user account and sends requests using anonymous service identifiers, it cannot offer an in-app control to locate and delete an individual completed cloud log early. You may contact us using Section 17 for a privacy or deletion request, and we will evaluate any records that can be located and deleted consistently with legal, security, and provider requirements.

06

RevenueCat and in-app purchases

The app uses RevenueCat to display subscription products, determine whether the Pro entitlement is active, complete purchases, and restore purchases. We configure RevenueCat without your name or email and rely on its randomly generated anonymous App User ID. Automatic device-identifier collection and RevenueCat diagnostics are disabled in the app configuration.

RevenueCat may process the anonymous App User ID, app and device technical information, product and entitlement identifiers, purchase receipt or Google purchase token, transaction history, subscription status, store, and timestamps. It may infer a country from a transaction or briefly from an IP address. This processing is necessary to provide and restore purchases and reduce subscription fraud.

Apple App Store or Google Play processes the payment. Neither the app nor RevenueCat receives your full payment-card number from the store. Store purchase history is also governed by the privacy terms of Apple or Google.

07

Firebase AI and cloud services

The app uses these Firebase components:

• Firebase AI Logic to send the photos and creative settings you explicitly approve to the selected Google Gemini model for portrait generation.
• Firebase Analytics to understand aggregate app operation. It may process installation identifiers, device and OS details, app-open and session events, and approximate network information. Source photos and generated portraits are not added to analytics events.
• Firebase Crashlytics to diagnose crashes and reliability failures. It may process crash traces, app state, device and OS details, installation identifiers, and approximate network information.
• Firebase AI Monitoring and Google Cloud Logging to inspect sampled AI request and response content for feature reliability and security. Content is access-controlled and has a configured 30-day retention period, as described in Sections 5 and 11.

Source photos, generated portraits, local file paths, application prompts, and facial details are not added to Firebase Analytics events or Crashlytics reports. AI Monitoring content logging is a separate, access-controlled operational service and is disclosed explicitly above.

The app does not use Firebase Authentication and does not create a Firebase user account. Firebase App Check is not enabled in the current release and no App Check attestation token is collected by the app.

08

Cookies and this policy website

The mobile app does not use browser cookies. This policy website does not intentionally add analytics, advertising pixels, forms, local storage, or cookies.

The site is hosted by Vercel. Like most hosting providers, Vercel may process network request data such as an IP address, user agent, timestamp, requested URL, and security signals to deliver the page, prevent abuse, and operate its infrastructure. That provider-side processing is governed by Vercel's privacy terms.

09

Service providers and disclosure

We do not sell personal information. We do not share it for behavioral advertising or cross-context advertising. Limited information is disclosed only to providers needed for the requested feature, or when required for security or law.

We require service providers that receive user data to protect it consistently with this policy and applicable Apple requirements, and use it only to provide, secure, or support the contracted service.

We may also disclose information if reasonably necessary to comply with law, protect users or the public, investigate fraud or abuse, or establish and defend legal claims. If the Service is transferred as part of a business transaction, applicable safeguards and notice requirements will apply.

10

Security

We use data minimization, app-owned storage, metadata stripping, transport encryption supplied by platform services, minimized service identifiers, and access controls to reduce risk. Live AI requests require an active entitlement and are sent over encrypted connections to Firebase AI Logic.

No method of electronic storage or transmission is completely secure. We cannot guarantee absolute security, but we will investigate credible reports and take reasonable steps to address issues within our control.

11

Retention and deletion

• Prepared source photos: kept in the app's temporary storage while a creation is open so a failed photo check can be retried or an input replaced. Replaced and removed photos are deleted immediately. Remaining prepared photos are deleted when the flow closes, generation completes or fails, or during interrupted-session cleanup.
• Generated creations: saved automatically in private app-local storage until you delete them or uninstall the app. Operating-system backups may retain or restore app data according to your platform and backup settings.
• Local preferences: kept until reset, deletion, or app removal.
• Subscription records: retained by Apple, Google, and RevenueCat as needed to provide purchases, restore access, meet accounting obligations, prevent fraud, and resolve disputes.
• Face data in Firebase AI Monitoring: sampled AI request and response content may include selected photos and generated outputs and is automatically deleted after 30 days.
• Face data during Google service processing: project-isolated in-memory caching can last up to 24 hours. Prompts flagged as suspicious by automated abuse controls may be securely retained for up to 90 days. These records are not used for AI or machine-learning model training.
• Other Firebase records: Analytics and Crashlytics records are retained according to their configured settings and applicable Firebase and Google terms. Photos and generated portraits are not added to Analytics events or Crashlytics reports.
• Support email: retained only as long as needed to answer the request, keep necessary support history, or meet legal obligations.

Deleting a local file does not delete a copy you previously exported, shared, backed up, or sent to another service.

12

Your choices, access, and deletion

• Decline camera or photo-library permission in system settings.
• Use a clearly labeled fictional sample for a missing parent slot.
• Cancel before live processing begins.
• Delete saved creations in the app.
• Delete exported copies from Photos, Files, backups, or receiving apps.
• Manage or cancel subscriptions through Apple or Google.
• Contact us to request access, correction, deletion, restriction, or objection where local law provides that right.

Because the app uses anonymous identifiers and keeps saved portraits locally, we may need an anonymous App User ID, transaction ID, or other verification to locate a provider record. We may be unable to identify a record from a name or email alone. We will not discriminate against you for exercising a privacy right.

The app does not sell or share personal information for cross-context behavioral advertising, so there is no sale or advertising share to opt out of. The Service does not respond to browser “Do Not Track” signals because it does not perform browser-based behavioral tracking.

13

Children's privacy

The app is intended for adults aged 18 or older and is not directed to children. We do not knowingly create accounts for or solicit personal information from anyone under 18.

An adult may submit a child's image only when they are the child's parent or legal guardian, or otherwise have all required permission and lawful authority. Do not submit a child's photo if you do not have that authority. If you believe a minor has submitted information directly or an image was submitted without proper permission, contact us so we can investigate.

14

International processing

Firebase, Google, RevenueCat, Apple, Google Play, and Vercel may process information in countries other than where you live. Privacy laws in those countries may differ. Providers describe their transfer safeguards, contractual protections, and relevant certifications in their own privacy and data-processing terms.

15

Links to other sites and services

The Service may link to provider policies, store subscription management, email, Photos, Files, or sharing destinations. We do not control those services and are not responsible for their content or privacy practices. Review their policies before providing information.

16

Changes to this policy

We may update this policy when features, providers, laws, or data practices change. The current version will be posted at this URL with a revised effective date. If a change materially affects how previously collected personal information is used, we will provide additional notice when required by law.