Retention and deletion
The practical retention rules behind DECYD today, including what stays briefly for safety or compliance and what you can request to remove.
Retention basics
Different data types have different retention rules. Payment records, abuse and security logs, user content, and transient voice inputs do not all belong on the same timer.
The right standard is clarity: keep what is required for the product, law, or safety posture, and do not make retention promises that the system cannot actually keep.
Current practical model
The live legal and privacy content already describes concrete examples such as payment-history retention for compliance, short-lived voice handling, and user-controlled deletion flows.
Where deletion requires queueing or follow-up steps, DECYD now treats that as an explicit workflow rather than an invisible back-office process.
If you want your data removed
Use the in-product deletion and export controls first when available. Those paths are faster and more traceable than manual email alone.
If something does not look right, contact privacy@decyd.io so the request can be reviewed against the exact data category involved.
More trust topics
Privacy and data controls
What DECYD stores, where it is processed, and the controls you have when you want to review, export, or delete your data.
Security and backups
How DECYD approaches access control, recovery readiness, and the operational safeguards behind a production AI platform.
Reliability and incidents
How DECYD handles degraded systems, incident communication, and the difference between customer-facing health and internal operational signals.