Data handling and retention
Working version: 0.1 · No effective date
1. Information classification
Account data, financial records, receipts and audit logs should be classified by sensitivity. Configuration files and credentials are managed separately from user documents.
2. Access and necessity
Queries and operations should enforce authentication, authorization and record ownership, including when an identifier is manipulated in the browser. Administrative access requires an authorized purpose and auditability.
3. Storage and transmission
Communications should use HTTPS and private files should not be available through predictable public links. Secure passwords, secrets outside public code and protected backups require defined procedures.
4. Category-based retention
Different retention periods will be defined for active accounts, receipts, security records, support, commercial billing and backups. No fictional timelines are stated; periods must be documented after checking legal duties and technical capabilities.
5. Backup and recovery
Backups should be protected against alteration and unauthorized access and periodically tested through controlled restoration. Deletion from the primary system does not necessarily mean immediate removal from every backup; this distinction should be disclosed.
6. Transfers and processors
Vendor arrangements should address confidentiality, security measures, data location, official requests and cross-border transfer safeguards. Only actual verified suppliers should be listed.
7. Secure deletion
Deletion must distinguish deactivation, logical removal and permanent erasure. Technical procedures must cover databases, attachments and backups under an approved policy and applicable legal limits.
8. Periodic verification
Retention rules should be reviewed when modules, suppliers, service countries or business processes change. Final documentation should assign owners and record review dates.