Data Retention & Deletion Policy

Atlas Mind policy

Last updatedDraft, not yet in force

1. Purpose and application

This policy sets the rules for lifecycle handling of source documents, derived memory and operational records.

2. Substantive provisions

2.1. Retention schedule

Assign evidenced retention criteria to account data, billing documents, source caches, embeddings, indexes, knowledge graph vertices and edges, task logs, security logs, backups and litigation holds. Public schedules must disclose periods or criteria rather than invented fixed numbers.

2.2. Deletion cascade

Deletion of a source or project must trigger a traceable assessment of copies, derived summaries, vector entries, cached retrievals, graph relations and downstream copies. Dependencies and shared project permissions must be considered before finalising deletion.

2.3. Disconnection is distinct

Revoking an OAuth token or switching off sync does not necessarily remove previously ingested content. Interfaces and support responses must explain and implement distinct controls for stopping collection and deleting stored records.

2.4. Backups and holds

Backup retention, restore procedures, immutable logs and preservation duties can justify bounded exceptions where legally permissible. Exceptions must be documented, access restricted, excluded from ordinary processing and eventually purged.

2.5. Evidence and confirmation

Deletion operations need recorded initiation, scope, completion or partial failure, retry strategy and relevant user confirmation. A success screen must not be presented until downstream deletion status is known.

3. Customer rights, administration and changes

Nothing in this document is intended to restrict rights that cannot lawfully be excluded, including applicable statutory consumer and data protection rights. Where this document conflicts with mandatory law, the mandatory rule prevails. Complaints, concerns and requests should be directed through the verified contact details published by Forlais.

Forlais may revise this policy to reflect changes in the service, third-party requirements or applicable law. Any revision that materially affects customer rights will be communicated in the manner and timeframe required by the applicable agreement and law.