Data Retention & Deletion
Specific existing controls, without a promise of complete erasure.
1. Retention is not yet scheduled by policy
Memory Space and profile information, preferences and some memory/chat state can persist in browser storage. Other paths store records or media through the configured cloud services. Signing out ends the relevant session; it does not erase memories, profiles, uploads or all browser caches.
[REQUIRES CONFIRMATION] No approved retention periods are established here for accounts, media, chat, consent, logs, backups or provider data. Actual deployed schedules, backup expiry, legal holds and deletion obligations require verification.
2. Existing deletion controls & limits
The Memory screen has individual delete actions. Its implementation removes the local memory entry and attempts deletion of the authenticated user's cloud memory record; a cloud failure is reported. The inspected delete helper does not remove the uploaded storage object.
A removed record is not evidence that the associated file, browser copies, backups, logs or provider-held data have been erased. Existing profile/chat editing or reset paths are not an account-wide legal erasure workflow.
Clearing browser storage can lose local-only memories and is not a cloud-deletion request. Keep originals before using destructive browser controls; this Legal section does not clear any data.
3. Account deletion, export & withdrawal
Account-wide deletion requests, a complete personal-data export and general policy-consent withdrawal are not implemented as self-service backend workflows. No new delete/export buttons or false request-success messages are provided.
The separate gated voice-clone feature has its own request/revocation path where configured. A request is not proof of completed provider deletion. General policy acknowledgements do not enable or replace that path.
Prepare a minimal request using Grievance & Support, but do not assume it has been submitted: the approved contact channel is still pending.
4. Required verification before approval
[REQUIRES CONFIRMATION] Define verified account ownership, scope discovery across database/storage/providers, retention exceptions, backup handling, request tracking, completion evidence and a secure export method. Confirm applicable legal deadlines with an India-qualified technology/privacy lawyer.
No fixed completion time, complete erasure guarantee or indefinite safe storage promise is made by this draft.
