# Data Retention and Deletion Policy | Zokrypt

Source: https://zokrypt.com/data-retention

# Data Retention and Deletion Policy · Zokrypt

Last updated: 12 November 2026. Applies: 12 November 2026.

Version 1.0. Effective from 12 November 2026.

## 1. Preliminary

1.1 This Data Retention and Deletion Policy (the "Retention Policy") is issued by Clausom Private Limited ("Clausom", "we", "us" or "our") and forms an integral part of the Terms of Service and the Privacy Policy. It sets out how long we retain each category of personal data processed through the Zokrypt Platform, the manner in which personal data is erased, and the exceptions that the law requires.

1.2 This Retention Policy is made in discharge of our obligations under section 8(7) and section 12 of the Digital Personal Data Protection Act, 2023 (the "DPDP Act"), rule 8 of the Digital Personal Data Protection Rules, 2025 (the "DPDP Rules") and, to the extent applicable, rule 5(4) of the SPDI Rules, 2011. Capitalised terms carry the meanings given in the Terms of Service and the Privacy Policy.

## 2. Principles

2.1 Purpose limitation. We retain personal data only for as long as it is necessary for the purpose for which it was collected, or for as long as retention is required or authorised by law.

2.2 Erasure on withdrawal or request. We erase personal data, and cause our Data Processors to erase it, when you withdraw the consent on which it rests or request erasure, unless retention is required by law.

2.3 The succession purpose. The Services exist to act when an Owner becomes inactive. Inactivity is therefore the event the Services are built to respond to, and does not of itself end the purpose of processing. We do not erase an Owner's account or Vault Content merely because the Owner has stopped using the Platform or because a Subscription has lapsed or been cancelled.

2.4 Minimum retention for security. From the date on which rule 8(3) of the DPDP Rules comes into force, we retain personal data, associated traffic data and processing logs for at least one year from the date of processing, for the purposes of preventing, detecting, investigating and remediating personal data breaches, unless a longer period is required by law. At present, system and processing logs and network edge logs are kept for 180 days, traces for 14 days, short-term container logs for 30 days, and audit records for 7 years.

2.5 Zero-knowledge content. We cannot read Vault Content. Its retention and deletion are therefore governed by the Owner's own actions and by the account lifecycle, not by any review of its contents.

## 3. Retention schedule

3.1 The following schedule applies to each category of personal data. "Account erasure" means the procedure in paragraph 4, under which data is permanently deleted 30 days after an erasure request.

| Category | Retention period | What happens at the end |
| --- | --- | --- |
| Name, mobile number, e-mail address, date of birth | For the life of the account | Deleted on account erasure |
| Vault Content (ciphertext) and its metadata | Until the Owner deletes the item, or account erasure | A deleted item can be restored for 24 hours, after which its stored file is permanently deleted; the item's record and its key copies are permanently deleted 30 days after deletion |
| Successor key copies (envelopes) | Until the item is deleted or its content replaced, the Successor's own account erasure, or the Owner's account erasure, including for Successors who can no longer claim, whose access is blocked by a server rule | Deleted with the item, or on account erasure |
| One-time passwords (a hash of the code, stored against a keyed hash of the mobile number) | 10 minutes from issue; send-rate counters 10 minutes and 24 hours | Expire automatically |
| OTP dispatch log (mobile number as a keyed hash) | 90 days from dispatch [to be extended to one year, see paragraph 2.4] | Purged automatically |
| Refresh tokens | 7 days after expiry | Purged automatically |
| Devices and public keys | While linked; when removed, marked removed (its keys revoked) and kept until account erasure completes; when removed, until the scheduled deletion date | Deleted on account erasure; purged automatically |
| Device display name | While the device is linked | Cleared when the device is removed or signed out |
| Push notification tokens | Until the platform (FCM or APNs) reports the token invalid, the Owner signs out on that device, or account erasure completes | Cleared or deleted |
| Check-in schedule, Check-ins, escalation and vacation records | For the life of the account | Deleted on account erasure |
| Facial check-in template | Until the Owner turns the feature off or withdraws consent, or account erasure | Deleted from our servers promptly; other phones delete their copy when the app next opens |
| Emergency Contacts | Until the Owner removes the contact, or account erasure | Permanently deleted, with no soft-delete period |
| Succession records (acceptance, Pass, claim, expiry, skip, revocation) | Until the Owner removes the Successor (revoking a Successor keeps the records), or the Owner's account is erased | Deleted. If a Successor erases their own account, their device identifiers and their link to these records are cleared, their open invitations are ended and stripped of the phone number, and the owner is notified about the erasure of the successorâs account. |
| Consent records | For the life of the account; a withdrawn consent is kept, marked as withdrawn | Deleted on account erasure; see the audit records row |
| Audit records of consent and security events | 7 years in write-once storage (S3 Object Lock, compliance mode); the database copy is kept with no end date | When account erasure completes, the link to the user is removed; the archived entries hold no name, phone number or user link, but erasure entries keep the account's internal random identifier |
| Parental consent records | Until the child's account is erased | If the parent erases their account, the record stays unlinked from the parent's account, keeping a one-way hash and the last four digits of the parent's mobile number, as evidence that consent was given |
| Billing records, invoices, credit notes, payment records | For the period required by section 36 of the CGST Act, 2017 and section 128(5) of the Companies Act, 2013, whichever is longer (at present, not less than eight financial years) | On account erasure, the subscription is closed, saved payment tokens are archived, and the customer record is anonymised in our billing system (Odoo); GSTIN, state and country are kept on the invoice record; statutory records are kept for the remainder of the period |
| Payment gateway webhook records | Personal fields are removed on receipt; processed records are kept for 1 year after processing; failed records are kept until reviewed | Purged automatically |
| ZoPoints ledger and referrals | For the life of the account; an idle balance expires after 12 months | Deleted on account erasure |
| Credential-hygiene summary counts | For the life of the account | Deleted on account erasure |
| ZoKey records (wrapped key, redeeming device) and ZoKey redemption requests (device identifier, key fingerprint, platform) | For the life of the account, including ZoKeys that are no longer valid | Deleted on account erasure |
| Notification delivery records (event type, channel, provider message ID, error text) | For the life of the account | Deleted on account erasure |
| Unverified e-mail address | Held on our servers, marked unverified, until it is verified or changed, another account verifies that address, or account erasure | Deleted from our servers |
| Website logos cached on the phone | Fetched again when shown if older than 30 days | Deleted on the phone at sign-out, or when the operating system clears the app cache |
| Product analytics events (PostHog, EU region; anonymous, sent only with consent) | 1 year (PostHog free plan) | Deleted by the analytics provider |
| Crash reports (Sentry, Germany) and performance reports (Expo EAS Observe) | Sentry: 30 days; EAS Observe: 90 days, deleted monthly, so a record may remain for up to about 120 days | Deleted by the reporting service |
| WhatsApp message data | Meta: up to 30 days; Fast2SMS: kept permanently under its current terms | Deleted by Meta; Fast2SMS's terms say it does not delete logs, even on request |
| Support and grievance correspondence | 3 years from closure of the matter, or until any related proceeding ends | Deleted |
| Database backups | 3 days, on a rolling basis (encrypted automatic point-in-time snapshots) | Overwritten |

## 4. Account erasure

4.1 Request. An Owner may request erasure of the account at any time in Settings in the mobile app or on the web, after a biometric check and typing the confirmation phrase, or by writing to dpo@clausom.com from the verified e-mail address. We may verify the requester's identity before acting.

4.2 Immediate effects. On a verified request, we shall, promptly: (a) mark the account for deletion and revoke all sessions; (b) suspend every Check-in, escalation and transfer workflow, so that no further Welfare Check is sent and no Asset is transferred; and (c) close any Subscription so that no further charge is made.

4.3 Cooling period. For 30 days after the request, the account data is retained in a deactivated state, so that an erasure made in error or by an unauthorised person can be reported to us. On the expiry of that period, the account and all personal data listed for deletion on account erasure in paragraph 3 are permanently deleted, together with every stored file. A verified sign-in with a one-time password within that period cancels the erasure and restores the Vault; Successor assignments on Assets not yet handed over, Successor invitations and the Subscription are not restored. The cooling period does not apply to erasures under paragraph 6.

4.4 Prior notice. Where we erase personal data on our own initiative because the purpose has ceased, we shall inform you at least 48 hours before erasure, so far as Rule 8 of the DPDP Rules so requires.

4.5 What erasure cannot recall. Erasure does not recall copies that a Successor downloaded or stored in the Successor's own vault before the request. Those copies are under the control of the Successor.

4.6 Backups. Deleted data may persist in encrypted database backups until those backups expire on their rolling 3-day cycle. Backups are isolated, are used only for disaster recovery and are not otherwise accessed. If a backup is ever restored, we shall re-apply every erasure made since the backup was taken.

## 5. Erasure of particular data

5.1 Without erasing the account, you may at any time: delete any vault item; remove a Successor, unless an Asset assigned to that Successor has already been transferred, in which case you must first withdraw the claim (you may still revoke that Successor); remove an Emergency Contact; remove a linked device; turn off facial check-in; and withdraw any withdrawable consent. Each such action leads to deletion in accordance with paragraph 3.

5.2 You may request correction, completion or updating of inaccurate or incomplete personal data under section 12 of the DPDP Act.

## 6. Children's accounts

6.1 Where a date of birth below 12 years is given at onboarding, before a vault is created, the account is erased promptly with no cooling period. An account that already holds a vault is locked, not erased.

6.2 Where a parent withdraws consent for a child aged 12 to 17 years and does not give it again within 30 days, or where consent is never given within 30 days of a pending sign-up for which no vault has been created, the child's account is erased with no cooling period. An account whose holder reaches 18 years is not erased on that account.

## 7. Death of an Owner

7.1 A Succession Event does not of itself erase the Owner's account. The account and its remaining data are retained, so that Successors may complete their claims within the Claim Windows.

7.2 The nominee appointed by the Owner under section 14 of the DPDP Act, or, failing a nominee, the Owner's legal representative upon production of a death certificate and proof of representation, may request erasure of the Owner's account. Such a request has the effects stated in paragraph 4, including the ending of any open claim.

## 8. Exceptions

8.1 We may retain personal data beyond the periods in paragraph 3 where retention is required: (a) by any law, including tax, company and anti-money laundering law; (b) by an order of a court, tribunal or competent authority; (c) for the establishment, exercise or defence of a legal claim, until the claim is finally resolved; or (d) for the investigation of a personal data breach or security incident. Data so retained is restricted to that purpose.

## 9. Data Processors

9.1 We require each Data Processor to delete or return personal data on our instruction and on termination of its engagement, subject to its own legal obligations. Where we erase personal data, we shall cause our Data Processors to erase the same.

## 10. Review

10.1 This Retention Policy is reviewed at least once a year, and whenever a new category of personal data or a new Data Processor is introduced.

## 11. Contact

11.1 Requests and questions about retention and erasure may be sent to dpo@clausom.com. Grievances are handled under the Grievance Redressal Policy.

11.2 Grievances and acceptable use. Any grievance concerning retention, deletion, correction or processing of personal data under this Policy may be raised through the channels and procedure set out in the Grievance Redressal Policy. The Acceptable Use Policy continues to apply to all use of the Platform and Vault Content; nothing in this Retention Policy authorises any use otherwise prohibited by that Policy.