Data retention notice (under review)
Retention boundaries for drafts, files, billing and service requests
Retention periods remain unconfirmed
The operator must define separate retention periods, starting points and cleanup mechanisms for conversations, input images, generated files, support records, payment and billing audits, logs and backups. Neither permanent retention nor immediate deletion is promised here.
Actions that do not establish deletion
Signing out does not erase cloud conversations. Clearing browser storage does not delete server-side works. Removing or hiding works should not be treated as physical erasure; consult the operation description. Submitting or closing a deletion request does not establish that ledgers, backups or provider-held data have been removed.
Requests
Use Data privacy to request export or account deletion and track a conclusion. Identity, scope, pending tasks, orders, asset dependencies and necessary audit retention require review. Actual execution must be recorded separately. If sign-in is unavailable, use Contact.