Contents · 16 sections
1. Preliminary
1.1 This Privacy Policy (the "Policy") is issued by Clausom Private Limited, a company incorporated under the Companies Act, 2013, bearing Corporate Identity Number U62099ME2026PTC476149 and having its registered office at Nanded- 431605, Maharashtra, India ("Clausom", "Zokrypt", "we", "us" or "our"). Clausom owns and operates the Zokrypt mobile application for Android and iOS, the Zokrypt web application, the Zokrypt browser extension and the payment page at https://pay.in.zokrypt.com (together, the "Platform"), and the services offered through them (the "Services").
1.2 In respect of the personal data processed through the Platform, Clausom is a Data Fiduciary within the meaning of section 2(i) of the Digital Personal Data Protection Act, 2023 (the "DPDP Act"). This Policy constitutes the notice required by section 5 of the DPDP Act and rule 3 of the Digital Personal Data Protection Rules, 2025 (the "DPDP Rules"). To the extent they remain in force, it is also the privacy policy required by rule 4 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (the "SPDI Rules") and rule 3(1)(a) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 (the "IT Rules").
1.3 This Policy applies to every individual whose personal data we process through the Platform, namely: (a) persons who create a Zokrypt account ("Owners"); (b) persons whom an Owner nominates to receive assigned vault items ("Successors"); (c) persons whom an Owner names as emergency contacts ("Emergency Contacts"); (d) parents and lawful guardians who give consent on behalf of a child; and (e) visitors to the payment page.
1.4 This Policy shall be read in conjunction with the Terms of Service, the Grievance Redressal Policy, and the Refund and Cancellation Policy, each of which is incorporated by reference. You may ask to read this Policy in English or in any language specified in the Eighth Schedule to the Constitution of India by writing to dpo@clausom.com. In the event of any inconsistency between language versions, the English version shall prevail.
1.5 Grievances and acceptable use. Any grievance concerning the collection, use, disclosure, correction or erasure of personal data, or any other matter relating to this Policy, may be submitted and shall be handled in accordance with the Grievance Redressal Policy. Your access to and use of the Platform, including the storage, transmission and sharing of Vault Content, remains subject to the Acceptable Use Policy. Nothing in either policy expands Clausomâs and Zokryptâs technical ability to access plaintext Vault Content.
2. Definitions
2.1 Capitalized terms used but not defined in this Policy carry the meaning given to them in the DPDP Act or the Terms of Service. In this Policy:
- "Vault Content" means every item an Owner stores in the vault, including passwords, notes, cards, documents, media, one-time password (OTP) secrets and their titles, fields and attachments.
- "Secret Phrase" means the passphrase an Owner sets at onboarding, from which the key that protects the Owner's private keys is derived.
- "ZoKey" means the printable recovery kit an Owner may generate from Settings to recover their vault on a new device as a last resort.
- "Check-in" means an Owner's explicit welfare confirmation, made on a registered phone through the designated process configured by the Owner on the mobile app, that the Owner is alive and active.
- "Succession Event" means the moment at which an asset assigned to a Successor becomes claimable, whether by expiry of the inactivity period and escalation window set for that asset or by arrival of the release date set for it.
- "Welfare Check" means a message or call that Zokrypt sends to an Emergency Contact when the Owner has not responded to Check-in reminders.
3. The zero-knowledge architecture and its legal consequences
3.1 Vault Content is encrypted on the Owner's device before it leaves the device, by envelope encryption (X25519 key agreement with AES-256-GCM, including a hybrid post-quantum construction). Our servers receive and store ciphertext only. The Owner's private keys are held on our servers solely in a form wrapped under a key derived from the Secret Phrase, which we do not receive.
3.2 Accordingly, Clausom does not possess, and is technically incapable of accessing, the plaintext of any Vault Content, any private key or any Secret Phrase. We cannot read, scan, index, moderate or disclose Vault Content, whether to you, to a Successor, to any third party or to any authority. Where we are lawfully compelled to produce information, we can produce only ciphertext and the metadata described in paragraph 3.4.
3.3 Clausom maintains no key escrow and offers no mechanism to reset a Secret Phrase. An Owner who forgets the Secret Phrase, has not generated a ZoKey and has no other signed-in device shall permanently lose access to the vault. This limitation is disclosed and acknowledged at onboarding, and is not a defect in the Services.
3.4 To operate the Services we necessarily see limited metadata, namely: the existence, size and creation and modification times of each item; the kind of each item (for example password, note, document, card, bank account, investment, loan, crypto wallet, medical or family contact), the kinds listed after "document" being visible only with your consent under the "vault-item-kinds" purpose; the assignment of an item to a Successor and its trigger settings; and the ciphertext key copies ("envelopes") prepared for each Successor. Titles, field values and notes of every item remain encrypted.
4. Personal data we collect
4.1 We collect only the personal data that is necessary for the purposes set out in paragraph 5. The table below states each category, its source and whether it is required.
| Category | What it includes | Source | Required? |
|---|---|---|---|
| Identity and contact | Name, mobile number, e-mail address (verified in the app), date of birth | You | Yes, except email until you verify it |
| Authentication and device | One-time passwords (held briefly), public device keys, passkey public credentials, session and refresh tokens, device identifier, platform, model, OS version, app version, the display name you give a device, push notification token | Your device | Yes |
| Recovery events | ZoKey status, and where a ZoKey recovery is attempted, the platform of the recovering device and an approximate city or region, shown to you in the alert | Your device; derived by us | Only if you use ZoKey |
| Check-in data | Check-in schedule, timestamps of Check-ins, missed Check-ins, vacation periods, escalation state | Your device; generated by us | Yes, where succession is armed |
| Facial check-in template | Five numerical face fingerprints computed on your phone and encrypted to your key before upload; camera frames and images are never stored or sent | Your device | No (optional feature) |
| Succession data | Successor account links; an invited Successor's mobile number, kept only as a peppered one-way keyed hash and its last four digits; asset assignments; trigger policies; records of acceptance, Pass, claim, expiry, skip and revocation | You and Successors | Only if you nominate Successors |
| Emergency Contacts | Name and mobile number of each Emergency Contact, encrypted at rest and decryptable only by the welfare-check service | You | No |
| Parental consent | A parent's mobile number as a peppered keyed hash and last four digits; the link between parent and child accounts; the decision, the consent wording version and timestamps | You and your parent | Only for users aged 12 to 17 |
| Billing | User ID, plan, amounts, gateway subscription, order and payment identifiers, invoices and credit notes, and the email and phone on your billing record. We never receive card numbers, bank details or UPI credentials | You; Razorpay; Odoo | Only if you subscribe |
| ZoPoints and referrals | Points ledger, referral codes, referral status; device integrity signals only with your fraud-check consent | Generated by us | Only if you take part |
| Security summaries | Aggregate counts of breached, reused and weak passwords and a scan time, never a password or hash; your Peace Score band | Your device | No |
| Product analytics | Named in-app and in-web events, a random device or browser ID, device and OS model, app version, update identifiers | Your device or browser | No (consent; never for users under 18) |
| Diagnostics | Crash reports with stack trace, device and OS model, app version and non-personal context; app start and screen timings | Your device | No |
| Browser extension | Data accessed. The Extension accesses the domain of the web page you visit and the sign-in or payment fields on it, solely to identify your saved credentials and offer autofill at your instruction. When you choose to save a login, it accesses the credentials you enter at that time. It does not collect your browsing history or other page content. Data transmitted to us. Saved credentials are encrypted on your device before transmission, and we cannot access or read them. We do not receive the websites you visit. With your consent under the Digital Personal Data Protection Act, 2023, we receive anonymized usage events, error reports, the Extension version, and a random identifier not linked to your account, none of which contains web page addresses or vault contents. Data is retained only on your device. Decryption keys and credentials are matched to the page you are viewing. | Your browser | Only if you use the extension |
| Communications | Your correspondence with support and the Grievance Officer | You | No |
| Audit records | Consent grants and withdrawals, security events, account erasure requests | Generated by us | Yes |
4.2 We do not collect your precise location, your device's advertising identifier, your address book (the contact picker returns only the single contact you choose), or your payment instrument details. We do not use Vault Content for any purpose, because we cannot read it.
4.3 Where you give us the personal data of another individual, such as a Successor's or Emergency Contact's name and number, you represent that you are entitled to do so and that you have informed that individual of this Policy. We inform such individuals when we first contact them, tell them who nominated them and give them a means to object.
5. Purposes and grounds of processing
5.1 We process personal data on the basis of your consent under section 6 of the DPDP Act, or for a legitimate use under section 7 of the DPDP Act, as stated below. Consent is collected by purpose at onboarding and can be managed in Settings, Privacy.
| Purpose | Ground | Consent category |
|---|---|---|
| Create and secure your account, authenticate you, link devices, prevent fraud and abuse | Consent | essential |
| Confirm your identity and apply the age and parental-consent rules | Consent | essential (identity-verification) |
| Store encrypted Vault Content and its metadata, and show item kinds | Consent | vault_storage |
| Run Check-ins, reminders, the escalation ladder and Welfare Checks | Consent | essential and notifications |
| Notify Successors and deliver their key copies at a Succession Event | Consent | nominee_sharing |
| Send account, security, billing and Check-in notices by push, SMS, WhatsApp and email | Consent | notifications |
| Facial check-in | Explicit consent, separately given | face check-in purpose |
| Bill you, issue GST invoices and keep tax records | s.7(a); s.7(d) and (e) (legal obligation) | none |
| Run ZoPoints and referrals | Consent | essential; fraud-check (optional) |
| Measure product usage to improve the Services | Consent | analytics |
| Diagnose crashes and performance faults | Consent in production builds | analytics |
| Answer grievances, comply with law, court orders and lawful requests, establish or defend legal claims | s.7(d) and (e) | none |
5.2 We do not sell personal data, do not display third-party advertising and do not build advertising profiles. We shall send promotional messages only with a separate, specific consent that you may withdraw at any time.
5.3 We process the personal data of Successors and Emergency Contacts only to deliver the notices and key copies described in paragraphs 7.1 and 7.2. Each of them may exercise the rights in paragraph 13 by writing to dpo@clausom.com, and may object to being named.
6. Consent and its withdrawal
6.1 Every consent we seek is free, specific, informed, unconditional and unambiguous, and is given by a clear affirmative action. We record the purpose, the wording version, the time and the device of each grant and withdrawal in an append-only audit record.
6.2 You may withdraw any consent, other than the essential consent, at any time in Settings, Privacy or by writing to dpo@clausom.com, with the same ease with which you gave it. On withdrawal, we shall cease, and cause our Data Processors to cease, the processing concerned within a reasonable time, unless the processing is required or authorized by law. Withdrawal does not affect the lawfulness of processing carried out before it.
6.3 The essential consent sustains the account itself. To withdraw it, you must erase your account as described in the Data Retention and Deletion Policy. Withdrawing a functional consent may disable the feature it supports; for example, withdrawing nominee_sharing prevents Successors from receiving assigned items.
6.4 Where a Consent Manager registered under section 6(7) of the DPDP Act becomes available, you may give, manage, review and withdraw consent through it.
7. How succession and welfare checks use your data
7.1 Where you arm succession for an asset, we send you Check-in reminders at the frequency you choose. If you do not check in, we escalate by push notification, SMS, WhatsApp and email to you, and then by Welfare Check to your Emergency Contacts. Welfare Checks disclose to the Emergency Contact only that we are trying to reach you; they disclose no Vault Content.
7.2 At a Succession Event we notify the Successor and make available the ciphertext of the assets assigned to that Successor, together with the Successor's own key copy. Your vault itself never moves; only the assigned assets move, and only to the Successor to whom you assigned them. Successors learn nothing about assets not assigned to them, and nothing about any chain of Successors until a claim reaches them.
7.3 Transfers proceed automatically once the escalation window is exhausted. No member of our staff can approve, block or accelerate a transfer, and no member of our staff can read what is transferred.
8. Children and persons with disability
8.1 The Services are not available to any individual below 12 years of age. Where a date of birth below 12 years is entered at onboarding, we refuse the registration and erase the account promptly.
8.2 An individual aged 12 to 17 years is a child under section 2(f) of the DPDP Act. We process a child's personal data only after obtaining verifiable consent from a parent or lawful guardian in accordance with section 9 of the DPDP Act and rule 10 of the DPDP Rules. The parent must hold their own Zokrypt account, which serves to establish that the parent is an identifiable adult.
8.3 We do not undertake tracking, behavioral monitoring or targeted advertising directed at children. The analytics consent cannot be granted for a user below 18 years, and any analytics consent granted before the date of birth was known is withdrawn automatically.
8.4 A parent may withdraw consent at any time. On withdrawal the child's account is locked promptly and the child's Check-in deadlines are paused. If consent is not given again within 30 days, the child's account is erased.
8.5 A lawful guardian of a person with disability may give consent on that person's behalf under section 9(1) of the DPDP Act by writing to dpo@clausom.com with proof of guardianship.
9. Disclosure to Data Processors and others
9.1 We engage the following Data Processors under contracts that bind them to process personal data only on our instructions and to maintain reasonable security safeguards.
| Processor | Function | Personal data shared | Location |
|---|---|---|---|
| Amazon Web Services | Hosting, database, storage, transactional email (SES) | All server-side data, including ciphertext | India (Mumbai and Hyderabad regions) |
| Razorpay | Payment collection | User ID, plan, amount; Razorpay collects your payment details directly | India |
| Odoo | Subscription billing and GST invoicing | Email, phone, pseudonymous customer name, billing history, saved payment tokens | India (primary); backups in France, the Netherlands and Canada |
| Fast2SMS | SMS and WhatsApp delivery | Mobile number and message text | India |
| Meta Platforms (WhatsApp Cloud API) | WhatsApp delivery | Mobile number and message text | May be outside India |
| Google (Firebase Cloud Messaging) | Push to Android and web | Push token and notification text | Outside India |
| Apple (Push Notification service) | Push to iPhone | Push token and notification text | United States |
| PostHog | Product analytics | Events, random device ID, device and app details | European Union |
| Expo (EAS Observe) | App start and screen timings | Timings, device and app details | Outside India |
| Sentry | Crash and error reporting | Crash reports with stack trace, device and OS model, app version and non-personal context | Europe |
9.2 Notification texts are composed so as to carry no names, phone numbers, e-mail addresses or Vault Content. Crash reports are sent to Sentry, listed in paragraph 9.1, and may be processed outside India. We mask personal data before a report leaves your device.
9.3 Two services are contacted directly by your device or browser and never through our servers: (a) Have I Been Pwned, which receives only the first five characters of a hash of a password you check, together with your IP address, so as to tell you whether that password appears in a known breach; and (b) the websites whose logos the Platform displays, which receive a request for their icon from your device or browser. Their handling of that request is governed by their own policies.
9.4 We may disclose personal data: (a) to a Successor, to the extent of the assets you assigned and the notices required by the succession process; (b) where required by law, or by an order of a court, tribunal or competent authority, including under section 69 of the Information Technology Act, 2000 or section 94 of the Bharatiya Nagarik Suraksha Sanhita, 2023; (c) to protect the rights, property or safety of any person, where permitted by law; and (d) to a successor entity in a merger, amalgamation, acquisition or sale of business, subject to this Policy and to prior notice to you.
10. Transfer of personal data outside India
10.1 Our production infrastructure and databases are located in India. Personal data is transferred outside India only to the extent stated in paragraphs 9.1 and 9.3, and only to countries or territories not restricted by the Central Government under section 16 of the DPDP Act. We shall review these transfers whenever the Central Government notifies any restriction.
11. Security safeguards
11.1 We implement reasonable security safeguards under section 8(5) of the DPDP Act and rule 6 of the DPDP Rules, including client-side encryption of Vault Content, encryption of personal data in transit and at rest, keyed hashing of third-party phone numbers, certificate pinning in the mobile app, least-privilege access controls, append-only audit logs held in write-once storage, monitoring for unauthorized access, and backups.
11.2 In the event of a personal data breach, we shall inform each affected Data Principal without delay, describing the breach, its likely consequences, the measures taken and the steps you can take, and shall intimate the Data Protection Board of India without delay and furnish a detailed report within 72 hours of becoming aware of the breach, as required by section 8(6) of the DPDP Act and rule 7 of the DPDP Rules. We shall also report cyber security incidents to CERT-In as required by law.
11.3 No method of transmission or storage is wholly secure. You are responsible for keeping your Secret Phrase, ZoKey and devices secure.
12. Retention
12.1 We retain personal data only for as long as is necessary for the purpose for which it was collected, or as required by law. Retention periods for each category, and the account erasure process, are set out in the Data Retention and Deletion Policy. In summary, on a request to erase your account we suspend all succession workflows promptly and permanently delete your account data 30 days later, save for records we are bound by law to keep.
12.2 We retain personal data for the following periods, unless a longer period is required by law:
| Category | Retention period |
|---|---|
| Application logs | 30 days in live systems, then archived for one (1) year |
| Product analytics events | One (1) year |
| Billing, invoice and GST records | Eight (8) years from the end of the relevant financial year |
| Audit records | One (1) year from creation |
On expiry of the applicable period, we delete or irreversibly anonymize the data.
13. Your rights as a Data Principal
13.1 Subject to the DPDP Act, you have the right to: (a) obtain a summary of the personal data we process and the processing activities, and the identities of the Data Fiduciaries and Data Processors with whom it has been shared (section 11); (b) correction, completion, updating and erasure of your personal data (section 12); (c) readily available means of grievance redressal (section 13); (d) nominate an individual to exercise your rights in the event of your death or incapacity (section 14); and (e) withdraw consent (section 6(4)).
13.2 A nominee under section 14 of the DPDP Act exercises your rights over your personal data. That nominee is distinct from a Successor, who receives assigned vault items under the Terms of Service. You may appoint the same person to both roles.
13.3 You may exercise these rights in Settings, Privacy, or by writing to dpo@clausom.com from your verified e-mail address. We may ask you to verify your identity before acting. We shall respond within the period prescribed by Rule 14 of the DPDP Rules, which shall in no case exceed 90 days, and we aim to respond within 30 days.
13.4 Under section 15 of the DPDP Act, you are under a duty not to impersonate another person, not to suppress material information, not to register a false or frivolous grievance and to furnish only verifiably authentic information when seeking correction or erasure.
15. Changes to this Policy
15.1 We may amend this Policy from time to time. We shall publish each revision with a new version number and effective date and, where a revision materially affects how we process your personal data, shall notify you in the app or by email at least 30 days in advance and, where the law requires, seek fresh consent.
16. Contact and Grievance Officer
16.1 For any question or grievance about this Policy or our processing of your personal data, contact our Grievance Officer and Data Protection contact:
Grievance Officer
CLAUSOM PRIVATE LIMITED
H NO.1/23/26/5 B G NO.263, P NO.04 BASERA COLONY,
Taroda BK, Nanded, Nanded- 431605, Maharashtra
Email: dpo@clausom.com
16.2 The procedure and timelines for grievances are set out in the Grievance Redressal Policy. If you are not satisfied with our response, you may complain to the Data Protection Board of India under section 13(3) of the DPDP Act after exhausting this procedure.