This document outlines Aevum Encyclopedia's data storage architecture, retention lifecycles, security protocols, and user control mechanisms. As a globally distributed knowledge platform handling millions of editorial entries, user accounts, and AI processing logs, we maintain strict governance over data lifecycle management.
ℹ️ Note for Contributors & Editors
Editorial content is subject to different retention rules than personal/user data. See Section 3 for the complete schedule.
Storage Architecture
Aevum operates a multi-region, geographically distributed storage infrastructure designed for redundancy, low-latency content delivery, and enterprise-grade security.
- Primary Storage: Encrypted, distributed object storage across 4 major cloud regions (US-East, EU-West, APAC-Tokyo, SA-Brazil)
- Content Delivery: Edge-cached via global CDN with TTL-based invalidation for real-time editorial updates
- Database Layer: PostgreSQL clusters with synchronous replication for user accounts, contributor metadata, and audit logs
- AI & Vector Storage: Dedicated vector databases for semantic search indexing, isolated from PII and encrypted at the block level
Retention Schedule
Data retention is strictly categorized by data type, regulatory requirement, and operational necessity. All retention periods begin from the date of creation or last user activity.
| Data Category | Retention Period | Disposition Method |
|---|---|---|
| Published Editorial Content | Indefinite (until deprecated) | Archived to cold storage; metadata preserved |
| Editor Drafts & Revisions | 12 months after publication | Secure wipe; diff logs retained for audit |
| User Accounts (Active) | Duration of account + 7 years after closure | Anonymized & aggregated for analytics |
| Authentication Logs | 13 months | Automated purge; compliance snapshots kept |
| AI Processing & Search Queries | 90 days | Hashed & aggregated; raw queries deleted |
| Support Tickets & Communications | 3 years after resolution | Archived in encrypted compliance vault |
Security & Compliance
All storage systems are hardened according to industry best practices and independently audited annually.
- Encryption: AES-256 at rest; TLS 1.3 in transit. Customer-managed keys available for enterprise partners.
- Access Control: Zero-trust architecture with RBAC, hardware-backed MFA, and just-in-time provisioning for staff.
- Compliance: GDPR, CCPA, UK Data Protection Act 2018, SOC 2 Type II, ISO 27001:2022
- Incident Response: 24/7 security operations center with <15 minute detection SLA and 24-hour external notification for regulated breaches.
🔐 Data Sovereignty
EU and UK user data remains strictly within EEA/UK borders. Cross-border transfers only occur with explicit consent or standard contractual clauses where legally mandated.
User Data Controls
Users maintain full sovereignty over their personal data through the Aevum Privacy Dashboard.
Export & Portability
Contributors and registered users can export their complete data footprint in standard JSON or CSV formats, including:
- Profile metadata & contributor history
- Article edits, comments, and voting records
- Subscription preferences & notification logs
Deletion & Right to be Forgotten
When a user requests account deletion:
- Account is immediately deactivated
- PII is permanently purged from active systems within 30 days
- Editorial contributions remain attributed to "Former Contributor" to preserve article integrity
- Archival backups are scrubbed during next scheduled rotation (max 90 days)
Requests can be submitted via the Privacy Dashboard or by emailing privacy@aevum.com.
Frequently Asked Questions
How often is data backed up?
Continuous incremental backups every 6 hours, with full snapshots weekly. Backups are encrypted and stored in isolated, air-gapped vaults for disaster recovery.
Can I opt out of AI processing?
Yes. In Settings → Privacy → AI & Analytics, you can disable personalized AI features. Search queries will still be processed but will not be used for model training or personalization.
What happens when an article is deleted?
Deleted articles are moved to a shadow archive for 18 months to prevent accidental loss and maintain citation trails. After that period, content is permanently wiped from all nodes.