Arkynox Legal
Data Retention Policy
How long we keep each category of data, why we keep it for that long, and how it is securely disposed of when the period ends.
1.Purpose and Scope
This Data Retention Policy sets out how Arkynox retains, archives and disposes of personal data processed through the ArkyDesk support platform. It is designed to satisfy our legal obligations, to meet legitimate business and evidentiary needs, and simultaneously to minimise the risk that personal data is kept longer than necessary.
This policy applies to all personal data processed in connection with the Service, including account data, support tickets and their communications, file attachments, and system and access logs. It supplements the Privacy Policy; where the two conflict on how long data is kept, this policy governs retention.
2.Retention Principles
- Purpose limitation. Data is collected for specified, explicit purposes and is not used for an incompatible purpose without a fresh lawful basis and notice.
- Storage limitation. Personal data is kept only as long as is necessary for the purpose for which it was collected, then for as long as a specific legal or evidentiary obligation requires. This mirrors Section 5(1)(e) of the EU GDPR and Rule 8 of India’s Digital Personal Data Protection Rules, 2025.
- Minimisation. We do not retain fields that have no support, security or legal purpose.
- Local law prevails. Where a jurisdiction imposes a longer mandatory minimum (see Clause 9) or a shorter maximum, that local rule prevails for data subject to it.
- No indefinite retention. Data is not retained indefinitely “just in case”. Any data whose retention period has expired is deleted or irreversibly anonymised under Clause 4.
3.Retention Schedule
The following schedule is our default retention position. Periods run from the date the trigger event occurs, and are subject to Clause 9 and Clause 10.
| Data category | Retention period | Justification |
|---|---|---|
| User account information | 3 years after last activity | Business continuity and service history |
| Support tickets | 7 years | Legal compliance, dispute evidence and knowledge-base contribution |
| Ticket communications | 7 years | Support continuity and agent training |
| File attachments | 3 years after ticket closure | Technical reference and troubleshooting |
| System access logs | 90 days | Security monitoring and troubleshooting |
| Error logs | 1 year | System improvement and debugging |
| Performance metrics | 2 years | Service improvement and capacity planning |
| Customer feedback | 5 years | Quality improvement and trend analysis |
| Billing records | 7 years | Tax and regulatory compliance (India and international) |
4.Data Lifecycle
4.1Active phase
While a ticket is open and for the retention period in Clause 3, data is held in the production systems and is fully accessible to authorised agents working the ticket. Access during this phase is governed by least-privilege rules and logged.
4.2Archive phase
Once the active retention period ends, data moves to an encrypted archive that is logically separated from production. Archived data is not queryable by agents or customer-facing features and is accessible only by a restricted, logged, engineering and compliance group for legal hold, security investigation and integrity verification. Archives are deleted in full at the end of the retention period.
4.3Disposal phase
At the end of its retention period, data is deleted from primary systems and from backups as those backups rotate out, or is irreversibly anonymised where the data is used in aggregate analytics. Deletion is performed using methods proportionate to the data, including cryptographic erasure where we hold the keys.
5.Legal Hold
Where we are notified of a claim, investigation, regulatory enquiry, or court order requiring the preservation of data, we place that data on legal hold. A legal hold suspends all deletion and archiving for the affected data, regardless of the retention period in Clause 3, until the hold is released in writing by the Arkynox legal function.
Holds may be placed on individual tickets, entire accounts, or defined data categories. We do not notify affected individuals of a hold where notifying them would prejudice the matter.
6.Erasure Requests and Backups
Where you validly request erasure under Clause 8 of the Privacy Policy, we delete your data from active systems and, where you request it, from archives, within the statutory response window (90 days for Data Principals in India under the DPDP Rules, 2025; one month in the EU/UK).
Under Rule 8 of the DPDP Rules, 2025 we give a Data Principal at least forty-eight (48) hours’ notice before their personal data is erased. We use that notice to invite you to withdraw or export your data.
We do not erase data that we are required to retain — for example, invoices for statutory tax-record keeping periods, or data subject to a legal hold under Clause 5. Where we refuse or limit an erasure request, we explain why and identify the lawful basis for retaining the data.
7.Deletion Verification and Evidence
Automated retention jobs run on a schedule, and their completion is logged. We retain internal records (not the deleted data itself) confirming that a given data category was deleted on a given date, and we sample-test deletions quarterly. These controls correspond to the “information deletion” and “documented information” controls in Annex A of ISO/IEC 27001:2022 (Controls 8.10 and 7.5).
8.Security of Retained Data
Retained data is protected at rest by encryption, in transit by TLS, and by access controls that are more restrictive for archived than for active data. Access to archived data requires a documented business justification, is approved by the data protection function, and is logged and reviewed. This aligns with Annex A Controls 5.15 (access control), 8.2 (privileged access) and 8.12 (data leakage prevention) of ISO/IEC 27001:2022.
9.Country-Specific Minimums
The table below records the mandatory retention requirements or limitation periods that affect Arkynox in the principal markets we serve, and the effect on our default schedule in Clause 3.
| Country | Key requirement | Typical period | Effect on our schedule |
|---|---|---|---|
| India | DPDP Act 2023 and Rules 2025: delete when the purpose is served. Companies Act, 2013 s.128: books of account 3 years (private) / 8 years (others). Income-tax records: statutory assessment window. | 3–8 years | Deletion on request per the DPDP Act; 7-year ticket default covers corporate book-keeping needs |
| EU/EEA | GDPR Art. 5(1)(e): kept no longer than necessary; national limitation periods for contracts. | 3–6 years | Our 7-year maximum covers EU limitation periods; erasure on request |
| United Kingdom | UK GDPR storage limitation; Limitation Act 1980: 6 years for contracts. | 6 years | 7-year retention aligns with UK requirements |
| United States | Federal and state record-keeping rules 3–7 years; CCPA/CPRA impose no fixed period but require disclosure of retention. | 2–7 years | 7-year ticket default covers US federal and state variation |
| Canada | PIPEDA retention principle (as long as necessary); Quebec Law 25 requires a documented retention framework and mandatory privacy impact assessments for sensitive data. | Necessity-based | Purpose-based retention; Quebec data subject to Law 25 assessment requirements |
| Mexico | LFPDPPP (2025): data must be deleted or anonymised when the purpose ends; implementing regulation by the Secretaría Anticorrupción y Buen Gobierno pending. | Necessity-based | Purpose-based retention; deletion on ARCO cancellation request |
| Japan | APPI: delete when the purpose is achieved; Civil Code: 5 years for contractual claims (reduced from 10 in 2020). | 5 years | Deletion on request; 5 years for contractual records |
| Australia | Privacy Act 1988: destroy or de-identify when no longer needed; Corporations Act: 7 years for financial records. | 7 years | 7-year retention aligns with the Corporations Act |
| Brazil | LGPD Art. 16: retention permitted for compliance, research or anonymisation; Civil Code limitation 3–10 years. | 3–10 years | 7-year default covers most LGPD requirements |
| Turkey | KVKK: delete or anonymise when the purpose ends; Code of Obligations: 10 years. | 10 years | Extended to 10 years for Turkish users where required |
| South Africa | POPIA: retention must be justifiable; Prescription Act: 3–6 years. | 3–6 years | 7-year default covers POPIA |
| Nigeria | Nigeria Data Protection Act 2023: retain only as long as necessary; CAMA: 6 years for records. | 6 years | 7-year default covers CAMA |
| Kenya | Data Protection Act 2019: necessary duration; Limitation of Actions Act: 6 years for contracts. | 6 years | 7-year default covers Kenyan requirements |
| Russia | 152-FZ: purpose-based; Tax Code 4–6 years for accounting records; in-country storage required. | 4–6 years | Purpose-based retention with in-country storage |
| Indonesia | UU PDP: delete when the period expires; Civil Code: 30 years for certain claims. | 30 years | Extended retention for Indonesian users where the Civil Code requires it |
| Thailand | PDPA: no fixed period; Civil and Commercial Code: 10 years for contracts. | 10 years | Extended to 10 years for Thai users where required |
| Philippines | Data Privacy Act 2012: necessary duration; Civil Code: 10 years for written contracts. | 10 years | Extended to 10 years for Philippine users where required |
| South Korea | PIPA: destroy when purpose achieved; Consumer Protection Act: 5 years for transaction records. | 3–5 years | 5-year minimum for records, deletion on request |
| Sri Lanka | PDPA No. 9 of 2022: destroy when purpose fulfilled; Prescription Ordinance: 6 years for contracts. | 6 years | 7-year default covers Sri Lankan requirements |
| Kazakhstan | Law No. 94-V: purpose-based; Civil Code 3 years general; in-country storage required. | 3 years | Purpose-based retention with in-country storage |
10.Exceptions and Approvals
Any retention period longer than this policy requires is a documented exception, approved by our data protection function and recorded in our processing register with a review date. Valid reasons for an exception include:
- an outstanding legal claim, regulatory enquiry or legal hold (Clause 5);
- an unresolved security investigation, where log data is essential to attribution;
- statutory record-keeping obligations, such as invoices, tax records and books of account;
- defect diagnosis where anonymised or aggregate data cannot serve the purpose; or
- an express instruction from you, for example where you require a longer period for your own compliance.
Exceptions are reviewed at least annually and expire automatically if not renewed.
11.De-identification and Aggregation
Where we need to retain analytical value after the retention period has expired, we convert the data to an irreversibly anonymised form first. Anonymised data is outside the scope of the GDPR, the DPDP Act and equivalent laws because it can no longer be linked back to an individual, and it is used only in aggregate to improve the Service.
12.Review and Contact
We review this policy at least annually, and on any significant change to the Service, our data flows, or the law. Retention settings are enforced by automation, with a quarterly compliance audit and an annual management review of the results, consistent with ISO/IEC 27001:2022 Clause 9.1 and Annex A Control 5.33 (protection of records).
To ask about a retention period, request early deletion, or place data on hold, email privacy@arkynox.com or use the privacy controls inside your ArkyDesk account. We respond within the statutory window described in Clause 6.

ArkyDesk