Company OS · CEOPRENEUR AG
Retention & deletion.
Proposed data profile for Company OS customer engagements.
Version: 1 November 2026
Target standard v0.1. These periods are a proposed contractual and operational profile. They apply to an engagement only after agreement and verified implementation. They do not imply already active automatic deletion in the existing pilot.
Proposed default periods
- Unneeded raw messages
- No additional persistent storage of complete webhook payloads. Process only for the required task; necessary content is explicitly classified as task data.
- Task content
- Up to 30 days after confirmed completion unless the engagement requires a different period.
- User and access association
- While authorization is active, then up to 30 days for orderly closure. Access revocation is distinct from deletion.
- Technical security logs
- Up to 30 days, using minimized metadata without passwords, tokens or complete chat contents.
- Execution and approval evidence
- Up to 180 days after completion. Longer necessary retention requires a recorded reason and restricted access.
- Replay and revocation records
- Default profile: 180 days. Delete only when old messages and revoked associations will still be rejected safely; deleting blocking records must not reauthorize them.
- Backups
- Target: rolling retention of at most 35 days. Following a restore, data removed from active systems is blocked or deleted again before ordinary use resumes.
- Contract and billing records
- Follow actual statutory duties and documented evidence needs, separately from chat and usage data.
Acceptance for each deployment
Before processing starts, data categories, responsible parties, deletion ownership, exceptions and provider/backup periods are established. Evidence must cover retention, revocation, export, deletion, replay protection and recovery, including partial failures. Only then is the profile recorded as implemented for that engagement.
Longer retention needs a documented purpose, period or verifiable end criterion and restricted access. Session expiry alone does not erase stored records. Requests can already be addressed to the deletion contact.