Privacy and photo handling

Updated 5 October 2026. Public paid generation is still being prepared. This page describes the handling used by the site when each feature is available.

Your photos and prompts

Selected photos remain in your browser until you submit a generation request. A submission sends your photos and scene direction to the site for processing. Images are screened using OpenAI services. Scene prompts are screened using the configured payment or moderation provider. Approved reference images and scene direction are sent to Kie’s generation service. These services have their own handling and retention policies.

Source photos are not offered as a public gallery. The site stores account information, credit and purchase records, task history, moderation decisions and completed videos so it can provide account access, reconcile transactions and deliver results. Selecting a photo does not make it a public post.

Accounts and payment information

A browser session keeps your account signed in. If an available Google or email sign-in is linked, the site stores the account details needed to identify that account. Payment checkout is handled by Waffo Pancake; full card numbers and card security codes are collected by the payment provider, not stored on our server; payment status and order references are used to reconcile credits and refunds. Never email us card details, passwords, private keys or your recovery code.

Browser storage, operational data and support

The site uses an HttpOnly session cookie for account access, with a maximum browser lifetime of one year. Logging out clears the current cookie. Browser local storage holds preferences and account recovery state; clearing it may affect account access, so save your recovery code first. Optional first-party visit and pricing-view analytics require opt-in and service availability. They record event type, account identifier, time and a broad source category such as direct, Google or ChatGPT, rather than your prompt or photo. We also keep operational errors and security information needed to protect the service. Support emails and their contents are received through our support mailbox.

Purposes, sharing and safeguards

We process account and generation data to provide the requested service, purchase records to reconcile payments, and security and support records to prevent misuse and resolve issues. Where applicable, these purposes rely on contract performance, legitimate interests, consent for optional analytics, or legal obligations. We do not sell personal information. We share only data needed for hosting and delivery, payment processing, configured AI processing, email delivery or lawful requirements. Cloudflare provides our public HTTPS entry point. Providers may process data outside your country; their locations and applicable transfer arrangements must be considered before submitting sensitive material.

Public connections use HTTPS. Server data and credentials have restricted access, and account session and recovery secrets are stored as hashes. No system can guarantee absolute security. If a reportable incident occurs, we will make the notices required by applicable law.

Retention

Session authorization expires after one year unless renewed or revoked. Email sign-in codes expire after ten minutes; challenge records are removed on successful use or during expiry cleanup triggered by subsequent requests. These expiry rules are not general account deletion schedules. Account records, purchase ledgers, tasks, completed outputs, support records and backups currently have no automatic age-based deletion. Requests are reviewed for deletion or restriction, subject to necessary transaction and security record retention. A fixed retention schedule for these categories remains to be established before paid launch.

Data rights and policy changes

Depending on applicable law, you may request access, correction, deletion, export, restriction or objection to processing, and withdraw consent for optional processing. Contact [email protected]; we may verify account ownership and respond within the period required by applicable law. You may complain to your relevant privacy authority. Material policy changes will be announced on this website and the date updated; new uses requiring consent will not rely solely on continued browsing.

Age and third-party policies

This service is intended for adults aged 18 or older. If you believe a child submitted personal information, contact support for review and deletion. This policy covers our handling; external providers have separate policies: OpenAI, Kie.ai, and Cloudflare. Waffo Pancake displays its payment terms and notices in its checkout.

Consent and sensitive images

Only submit images you own or are authorized to use, with consent from each person pictured. Do not upload private or sensitive material you do not want processed by the named services. See the acceptable-use rules.

Access and deletion requests

Contact [email protected] to request help with your stored account information or deletion. Provide an account or order reference if available; we may need to verify that the request belongs to you. Some transaction or security records may need to remain for reconciliation or applicable obligations. This page does not promise automatic deletion or a fixed retention period. External providers’ handling must also be considered when a request concerns submitted material.

Account access · Creation terms · Questions before creating

Optional Microsoft Clarity analytics

With your analytics permission, we load Microsoft Clarity (project yswzukc4my) to understand page usage through interaction recordings and heatmaps. Clarity may process page URLs, browser and device information, interactions and analytics cookies. Microsoft is a third-party provider. Our generation studio and account dialogs are marked for content masking. We do not intentionally send uploaded photos, generation instructions, email addresses or recovery codes as custom analytics data. Clarity is not loaded on pages with URL query parameters.

You can decline without affecting account, payment or generation functionality. Use Analytics settings to change your choice. We store this choice in browser local storage separately from first-party analytics preferences. Advertising storage consent is denied. See Microsoft’s privacy statement for its processing practices.

Google Tag Manager

We install Google Tag Manager container GTM-5GDZ4BZF on public pages to manage measurement tags. The container loader contacts Google when a page opens. Google analytics and advertising storage consent default to denied; Analytics settings updates analytics consent, while advertising storage, advertising user data and personalization remain denied. Depending on the configured Google tags, limited cookieless measurement may occur when consent is denied. Google Analytics 4 is configured directly on the website with measurement ID G-B4RFR03MTN, alongside Google Tag Manager. It measures page usage and may use analytics cookies when permitted. The configured page location and referrer omit query parameters and fragments; Google signals and ad personalization signals are disabled in this configuration. Backend reporting and tags inside the Tag Manager container require separate verification.

When JavaScript is disabled, a hidden Google Tag Manager fallback iframe is included. Our on-page analytics controls require JavaScript. We do not intentionally put account identifiers, uploaded images, prompts, email addresses or recovery codes in the data layer. See Google’s privacy policy.

The installed script initializes automatically when a public page loads. Installation does not confirm dashboard reporting or payment-conversion tracking.

Plausible website statistics

We also load Plausible Analytics on public pages to measure page usage and traffic sources. This is separate from the optional cookie-based Google analytics and Clarity recording controls. According to Plausible’s data policy, its standard analytics does not use cookies or persistent visitor identifiers. It processes page paths, referral and supported campaign information, browser and device categories, approximate location and engagement measurements. We have not added account identifiers, uploaded photos, prompts, recovery codes or revenue as custom Plausible properties or events.

The installed script initializes automatically when a public page loads. Installation does not confirm dashboard reporting or payment-conversion tracking.