Privacy Notice

1. Scope

This notice describes information handled by Reader Remix. The service is for adults and is primarily intended for users in the United States. Neither age nor location is verified by this statement.

2. Information the application handles

The current application handles the following categories:

• Account information from Google sign-in: a Google account identifier, email address, and available display name/profile image, plus application account and session records. The requested scopes are identity, email, and profile—not access to your Gmail or Drive.
• Creative content: projects, pages, lettering, prompts, references/uploads, generation tasks and results, review notes, and saved creative snapshots used for eligible forks.
• Public interactions: publications, comments, reactions, and the information submitted with a report. Public comments can show your account display name; do not assume a pseudonymous profile.
• Operational records: credit grants and reservations, command status, account restrictions, moderation decisions, and request/error information needed to run the service.
• Network and browser information: requests reach our hosting provider, and abuse controls use keyed network-derived identifiers. Some authenticated activity is associated with an account. Aggregate public metrics are not a promise that infrastructure receives no identifying information.

3. Why information is used

Information is used to sign you in, save and render projects, run requested generation, track credits, publish and fork revisions, support social features, detect abuse, troubleshoot failures, respond to requests, and meet applicable legal obligations.

We do not need your Google password. Do not include passwords, session cookies, API keys, confidential third-party material, or unnecessary sensitive personal information in prompts, uploads, or support messages.

4. Public pages and complete project forks

Projects are private workspaces until you use sharing features. Publishing exposes the final page and its public title/license/social information. Anonymous readers do not receive the underlying project ingredients through the public page.

A signed-in user can fork an eligible published revision into a separate private workspace. That fork includes the whole saved creative project represented by the snapshot: other pages, prompts, references, lettering, supported assets, and candidate/review information—not just the published page. Credentials, balances, and account authority are excluded.

Completed forks and downloaded public images cannot be recalled simply by archiving the source. Recipients may subsequently use or share material subject to the applicable license and law. Do not publish personal or confidential material merely because the destination copy is initially called private.

Reports are not displayed as public comments. Staff may need to share relevant information with service providers, affected people, counsel, or authorities to investigate or comply with law. We cannot promise absolute report anonymity; formal copyright notices may be forwarded as part of the legal process.

5. Service providers and processing

Google provides sign-in and Google Cloud hosts application storage, databases, and infrastructure. OpenAI is the integrated image-generation provider and is also used for configured content-safety checks. Depending on the feature, prompts, reference images, uploads, or generated content may be sent to the provider for processing. Uploads can undergo safety processing even before you choose to publish.

Provider contracts, enabled features, safety obligations, and account settings affect how providers handle information. Do not assume providers retain nothing or have a particular account-level training setting. Reader Remix does not operate a first-party model-training program.

Reader Remix uses starter credits. Credit purchases and subscriptions are not available. Any future payment handling will need to be described in the privacy and purchase information.

Providers may process information in jurisdictions different from yours.

6. Cookies and browser storage

Sign-in uses a short-lived OAuth state cookie and a signed application session cookie, currently configured for up to 14 days. Restricted site access also uses an access cookie. These are distinct from the browser's local storage.

Local storage holds editor drafts, interface preferences, and retry identifiers for certain commands. Signing out is not a promise to erase all browser-stored drafts. Clearing site data can remove unsaved local work; save what you need first and use a trusted browser profile on shared devices.

The public metrics implementation uses server-side aggregate events without issuing an anonymous tracking cookie. This is not a claim that the whole application is cookie-free, that all records are anonymous, or that future advertising technology is already covered.

7. Retention, removal, and security

Saved projects, account records, publications, snapshots, and operational records are retained in the service's storage. Archiving does not erase them. Some records have manual pruning controls; their minimum eligible ages are not automatic deletion schedules or maximum retention promises.

There is no guaranteed maximum retention period or self-service account-deletion feature. Backups, security or legal records, provider-held information, and independent recipients' copies may require separate handling. We will not describe data as deleted when only public visibility has changed.

The service uses access controls and hosted infrastructure safeguards, but no system or transmission is guaranteed secure. Authorized personnel and providers may access information when necessary for the purposes described here.

8. Questions, access, and deletion requests

Available contact methods and request limitations are listed on Support & Account Requests. You may request information about your data, correction, access, or deletion; applicable rights and exceptions depend on your circumstances and law. We may need proportionate identity verification to avoid disclosing someone else's information.

The app does not currently offer self-service account deletion or a general private-project export. A privacy request must not require you to publish your project. Applicable statutory response duties are separate from ordinary support targets.

A free service or U.S. focus does not remove applicable privacy obligations.

9. Children and notice changes

Reader Remix is not for people under 18. If we learn a child has provided personal information, the operator must assess the appropriate restriction, preservation, and removal steps under applicable law. Google sign-in alone is not age verification.

Material changes to data use require an updated notice and any additional steps required by law. These pages do not authorize undisclosed new uses.