Data Retention and Deletion
Effective: 2026-09-22
Daybreak minimizes retention by category. Exact provider backup and support-record periods are production release gates and must be confirmed in executed provider terms before launch.
| Category | Retention | Deletion |
|---|---|---|
| Unfinished calendar and routine edits | Kept in this browser tab for up to 24 hours; availability depends on browser storage | Cleared on save, discard, sign-out or session cleanup; expired copies removed on next access |
| Recently deleted calendar activities | Recoverable for 30 days; expired copies removed by the daily retention job | Removed on restore, permanent deletion, or account deletion |
| Account, profile, tasks, plans, calendar mirrors, health and user content | While the account is active | Removed by user action, disconnect-with-deletion, or account deletion |
| OAuth, push, and notification credentials | While connected or subscribed | Revoked/removed on disconnect or account deletion |
| AI permits | Two-minute authorization; expired records cleaned after one hour | Automated daily retention job |
| AI cache | No more than two hours | Automated daily retention job and immediate consent-change purge |
| Rate-limit records | Up to two days | Automated daily retention job |
| Product analytics | Up to 365 days | Automated daily retention job; no health or sensitive content |
| Anonymous audit/security events | Up to 365 days after account linkage is removed | Automated daily retention job unless a narrow legal/security hold applies |
| Deletion status receipt | 45 days | Automatic expiry; contains no raw user identifier |
| Rights and support workflow | While the account exists and as required to complete or evidence the request | Account deletion or approved legal schedule |
| Backups | Provider-configured recovery lifecycle | Expires through backup rotation; not returned to active use except permitted recovery/security/legal needs |
Account deletion
Settings provides deletion after reauthentication. Daybreak immediately restricts the account, invalidates AI authorization, signs out sessions, and queues a durable worker that revokes connected providers before deleting credentials, storage, user rows, generated and derived records, then the authentication identity. Transient provider failures retry with backoff; permanent failure is shown as blocked rather than falsely completed. An opaque status capability works after authentication deletion and expires after 45 days.
Exceptions and verification
Narrow records may be retained where law, fraud prevention, dispute preservation, or security response requires it. Holds must be authorized and scoped; they do not permit product use of deleted content. Retention automation supports dry-run reporting and records category counts without personal values. Contact valeyardvisuals@gmail.com for questions.