Privacy notice
What the product needs to describe before launch.
Status and scope
This is a draft for reviewing the intended data flows, not a completed privacy policy. The operator, processors, transfer locations, exact retention schedules, and rights contact are not yet declared here. They must be verified against the deployed service before launch.
Account and authentication
The account workflow uses information such as your email and display name, authentication records, and login-session cookies. API credentials are managed separately. Do not put passwords or complete API keys into prompts, public URLs, or support notes.
Generation inputs and providers
Once provider execution is enabled, your model input may be sent to the selected channel. Authorized fallback can send the same input to another compatible provider. A platform retention setting cannot be interpreted as a guarantee about every upstream provider’s practices.
Operational records
Tasks, timestamps, model and channel identifiers, usage, credit ledger entries, and payment references support delivery, troubleshooting, and accounting. Content logs and generated files need separate retention controls. Deleting an output must not silently erase its accounting history.
Controls and contact
The interface includes account and retention settings, but a visible setting is not a substitute for verified backend enforcement. A verified privacy contact and request-handling process will be added before public commercial launch. Use the help page to understand the current preview limitations.