Data Retention Policy

EEZ DATA RETENTION POLICY — Version 3.1
Effective October 7, 2026.

Principle

EEZ seeks to retain information only as long as reasonably necessary for product operation, user-requested functionality, safety, security, legal obligations, shared records, or service recovery.

Active account data

Profile, Employment, schedule, earnings, preferences, Group membership, and other private account information may be retained while the account is active and as needed to provide the service.

Messages and shared schedules

Shared records may remain for other participants even after one user's account changes or is deleted. EEZ may remove or de-identify authorship while preserving shared-history continuity where appropriate.

Safety reports

User safety reports are designed for bounded retention and are scheduled for deletion after 90 days, unless a longer period is required by law or a specific unresolved safety/legal need.

Operational blocks

Block relationships are operational safety state and may be removed when an account is deleted.

Authentication attempts

Short-lived authentication-attempt data is retained only long enough to complete or reject an authentication attempt and related cleanup.

Push registrations

Push registrations are removed or invalidated when no longer needed, subject to ownership/reassignment safeguards and bounded expiry.

AI/parser caches

Content-addressed parser/schedule-processing caches may be retained temporarily for reliability/performance using bounded TTL behavior.

Purchase and entitlement records

EEZ may retain limited purchase-lineage, deleted-owner, binding-token, and lifecycle tombstones to prevent stale purchase evidence from restoring deleted ownership or being reassigned incorrectly. These records may be pseudonymous and are not described as anonymous.

Deletion receipts and anti-abuse guards

EEZ may retain bounded deletion-receipt/recovery information and credential reuse guards necessary to prevent account resurrection, repeat complimentary access abuse, or incomplete cleanup.

Diagnostics

Technical diagnostics may be retained for service reliability and security. Production diagnostics should exclude secrets, tokens, private keys, authorization codes, and unnecessary private content.

Backups and provider records

Data may persist temporarily in backups or third-party systems subject to provider retention schedules. Marketplaces may retain billing/purchase history under their own policies.

Contact

Support: support@EEZapp.com