TENX ARENA / product policy
Clear periods. Honest limits.
These owner-selected defaults apply to new commercial schedules. Your invitation shows the agreed version and any contractual changes. Historical schedules retain their original meaning.
Invitations and support
Invitation contact information: 30 days after expiry or closure, including earlier revocation or project closure. Support correspondence: 30 days after the case closes. Open cases are not silently treated as closed. Expired separately stored content is hidden from normal reads and eligible for recorded physical disposal.
Work and evidence
The default is 180 days after project closure for mission payloads, artifacts, revisions, AI interactions, reviewer evidence and Candidate Intelligence. The approved contract can configure the period. For an episode with different category periods, the shortest governs ordinary access. Closing a project is an explicit recorded action; starting or submitting a mission does not start this clock.
Accounts, operational logs and integrity
Account and profile information is needed while the account is active, then reviewed 90 days after account closure unless another legitimate obligation applies. Operational and security logs have a 90-day review period. Minimal integrity metadata has a 365-day review period where needed, with personal content minimized. These review periods do not claim automatic physical deletion of canonical records or provider logs.
Accounting, backups and research
Eligible accounting and tax documents are retained for the applicable Estonian seven-year period, with the legal start date determined for that document. This does not apply to every commercial enquiry. The rolling recoverable-backup target is 30 days, not a verified guarantee that every existing copy expires then. Research has no automatic commercial retention: a copy requires its own purpose, protocol, permission and schedule.
Work payload access
Mission events, artifacts, AI interactions and reviewer content share an episode. The shortest configured access period for those categories closes ordinary work, evidence and interpretation access. This is an access restriction and retention-review deadline, not a claim that immutable canonical content has been erased.
Erasable contact and support content
Invitation contact details and support correspondence are stored separately from immutable references. They become unavailable to ordinary reads when their configured period expires and are eligible for the operator's recorded disposal operation. A fulfilled contact-erasure request does not erase an authentication account or the canonical work history.
Integrity and retained canonical records
Canonical facts, version hashes, author bindings, permission and disposal receipts preserve provenance. Some records remain identifiable or pseudonymous; hashes do not make them anonymous. Continued retention requires operator/controller review under the configured schedule and applicable obligations. Erasure requests can be refused or partly fulfilled with an explicit result. A deleted payload cannot be represented as successfully replayed.
Accounts, research and backups
Accounts have a separate review period because an identity may belong to more than one organization. Research copies require separate permission and a separate governed export; accepting research permission creates no copy automatically. Logical backups can contain older data. Restored data must be quarantined until later restrictions and disposal records are reconciled. Backup-wide erasure and automatic deletion from every provider system are not promised.