Privacy Information — Product Preview

What the public Preview handles

The public Review surface does not offer account creation, sign-in, upload, generation, payment, or the protected Studio. It serves ordinary request metadata needed to deliver public pages and the rights-cleared Case. No public analytics or revenue tracking is enabled in the checked-in configuration.

Repository-tested protected behavior can record owner-scoped product data:

• account and session identifiers used to authenticate the owner;
• Project and Reference metadata, including a rights confirmation and provenance fields;
• Generation Request settings, Attempts, Version records, and Version decisions;
• internal Credit Holds and ledger entries created with test credits; and
• Reference bytes handled through the configured storage seam.

Those are engineering-tested product behaviors, not active public collection and not a promise about future production hosting or data practices.

Current external-service boundary

• Generation uses a local fake model. Reference content is not sent to a real generation provider by this preview.
• Paid plans and checkout are not active.
• The checked-in marketing configuration does not enable product analytics or revenue tracking.
• No production hosting region, subprocessor list, cross-border transfer arrangement, or public privacy contact has been accepted.

References and deletion

You must confirm that you are authorized to use a Reference before adding it. The preview implements owner-scoped access and an individual Reference deletion path. Its account-deletion path removes currently stored Reference objects before deleting the account and cascading its current Studio database records. Production retention periods, backup deletion timing, future provider-output deletion, and any legally required record exceptions have not been set.

Decisions required before publication

An effective privacy policy must be based on the final operator and real data flow. Before publication, alts.video still needs to confirm:

• the operator identity, contact channel, launch regions, and applicable legal bases;
• the production data categories, purposes, hosting regions, and subprocessors;
• retention, production account deletion, backup handling, legally required record exceptions, and security-incident procedures;
• whether any provider may retain or use inputs or outputs for model improvement; and
• user rights, cross-border transfer safeguards, and region-specific notices.

See Support status for the current contact boundary.