CoExyst Legal
Version: 2026-10-23-v2
Effective at (UTC): 23 October 2026
This policy explains how CoExyst keeps and deletes information. Read it with the Privacy Policy and Terms of Service. Contact support@coexyst.app for a data request or a question about a particular record.
Retention depends on the record’s purpose, your account and household state, legal obligations, billing, support, disputes and security needs. Shared records may continue to be needed by other household members after you leave or close your account. Leaving a house is not the same as deleting your account or every record associated with it.
You may request account deletion using the account tools or support. There is no fixed completion deadline. Applicable document holds, household or billing transfers, pending purchases and unresolved retention checks can delay completion. Removal of files and sign-in access must also be verified. Follow the steps shown for your request or contact support for its status. Deletion does not cancel obligations or require destruction of records that must lawfully be retained.
Where Mya conversation is available, its messages older than 180 days are removed when the conversation is next opened or written to. An inactive conversation can therefore retain older rows until that processing occurs. A row limit may remove older messages sooner. Unfinished tasks are resumable for up to seven days after their last touch; eligibility expiry is not a promise that every associated record is physically deleted at that moment.
Clear history deletes that conversation’s messages and pending work. It does not undo household changes you already confirmed, or delete a separate support report. Completed account deletion removes the Mya conversation and its linked records. House deletion also removes the linked conversation. If you leave a house you can no longer open or clear that conversation. It stays until you rejoin and clear it, your account deletion completes, or the house is deleted. Contact support to ask for earlier removal.
Backups and service records are kept on their own schedules, described in the Third-Party Notices, and clearing history does not change them.
CoExyst tries to mask amounts and withhold detected credentials before storing your typed Mya words. Looked-up personal or money details are represented by references and resolved under current access. Detection can miss information. The AI section explains what may reach a provider.
CoExyst does not store a separate outbound Mya model prompt, raw model response or the temporary placeholder lookup. It retains conversation state and operational metadata such as the outcome, timing and usage counts. A message held while permission is pending can remain in that state after permission expires until the conversation is next processed for cleanup; permission expiry is not a deletion deadline. This is separate from provider-side retention. That retention is described in the Privacy Policy’s AI section and the linked provider terms. Clearing history or declining later requests does not recall a request already processed by a provider.
Voice recordings, and any transcripts created before voice transcription was removed, are stored as message content and follow the applicable message and account lifecycle. CoExyst does not send recordings to an outside service for transcription. Where CarPlay Ask Mya’s voice setting is used, Apple’s speech service has its own retention rules; no common deadline is promised.
Support tickets and any conversation excerpt you deliberately submit are separate support records. A later history clear does not automatically remove them. Where Mya improvement and answer reporting are available, contribution is optional and starts off. Contributions you select may be used to evaluate Mya and prepare reviewed examples, and are not eligible for external provider training. Before sending a report, you can review its excerpt and choose whether to include your typed words. Turning improvement off stops future eligible use under that choice; it does not automatically delete a support ticket already submitted. Contact support to request deletion of a report. Using Mya or accepting these policies does not itself opt you into improvement or provider training.
When Mya reminders are enabled, pending-task state determines eligibility. Delivery records can contain recipient and conversation identifiers, reminder step, timing, channel and outcome, but the reminder payload uses fixed wording without conversation text. Cancelling or finishing a task, clearing history, losing access or disabling reminders prevents later eligible delivery after the checks run. A message already delivered cannot be recalled from an email inbox or device notification history.
The iPhone offline vault described in the Privacy Policy keeps accepted copies until you remove them or a verified deletion or access revocation requires removal. Its offline access period is separate from physical retention. Expiry hides the information; opening a copy does not extend access. Revocation can reach an offline device only when it reconnects. A temporary decrypted document preview is removed when closed.
Unsent changes remain on the device until sent or discarded. Account and house changes invoke the app’s removal controls. Another person’s saved export, screenshot or independently kept copy is outside those controls. Mya’s online conversation is separate from the household offline vault.
We aim to keep consent records for the life of your account plus two years, and de-identify them if you ask us to erase your data. A suppression record is kept for as long as needed to honour your withdrawal. Individual campaign delivery records are kept for 13 months and then reduced to totals. Click and conversion records are separated from identity when marketing consent is withdrawn. These are CoExyst’s record rules, not a promise that every email provider copy has the same lifetime.
Deleting an active record is distinct from expiry of operational backups, provider logs, delivery records and records under a legal hold. Retention varies with the system and applicable obligations; this policy does not promise an immediate purge of every backup or a single provider deletion deadline. We assess requests against the purpose and legal basis for retaining each record. Ask support about access, correction, deletion or the reason a record remains.