Checking sign-in…

Privacy policy · draft pending review

Minimum data for account, credits, and support.

This page explains the intended P0 privacy boundary. Retention, deletion, analytics consent, and provider configuration still require legal and technical approval.
Draft frontend content for review. It is reachable and substantive, but not yet legal, payment, or production approval.
01

Identity data

The service stores an internal user ID and verified Google subject. Email and profile fields are limited to what is necessary for account access and support. The product does not request Google Photos, Drive, Gmail, or contacts.

02

User content

Photos, text prompts, jobs, and results are separated from identity and payment records. The default product position is not to use user content for advertising, public galleries, cross-service profiles, or model training without explicit approval and consent.

03

Payment data

The site does not store card numbers or CVV. Creem-related records are limited to external IDs, plan snapshots, amount, currency, status, and audit references needed for subscription and ledger consistency.

04

Deletion

Deletion must distinguish identity, user content, payment records, logs, backups, and third-party provider records. Exact retention windows remain pending and must be disclosed before launch.