Data processing addendum
Last updated 20 November 2026
Draft. This document is under legal review and will change before the product is offered for production use.
This Data Processing Addendum ("DPA") forms part of the agreement under which DBTEZ Technologies Private Limited (CIN U72900KA2018PTC119829), WeWork, Block-L, Embassy TechVillage, Outer Ring Road, Devarabisanahalli, Bellandur, Bengaluru, Karnataka 560103, India ("DBTEZ") provides VachanSetu, a consent management platform for organisations that are Data Fiduciaries under the Digital Personal Data Protection Act, 2023 (the "Service"), to the customer named in the signature block ("Customer"). That agreement is the VachanSetu Terms of Service together with any order form or master subscription agreement (the "Agreement"). Where this DPA and the Agreement conflict on the processing of personal data, this DPA prevails. Where this DPA and the Standard Contractual Clauses conflict, the Standard Contractual Clauses prevail.
1. Definitions
- Applicable Data Protection Law means all laws on the processing of personal data that apply to a party's processing of Customer Personal Data. These include, where applicable: India's Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 ("DPDP Law"); Regulation (EU) 2016/679 ("GDPR"); the UK GDPR and Data Protection Act 2018; the Swiss Federal Act on Data Protection; and US state consumer privacy laws such as the California Consumer Privacy Act as amended ("CCPA").
- Customer Personal Data means personal data within Customer Data (as defined in the Agreement) that DBTEZ processes on the Customer's behalf in providing the Service, including consent records.
- Controller, processor, data subject, personal data breach and processing have the meanings given in the GDPR. For the DPDP Law, "controller" includes Data Fiduciary, "processor" includes Data Processor, and "data subject" includes Data Principal. For the CCPA, "processor" includes service provider.
- Sub-processor means a third party that DBTEZ engages to process Customer Personal Data.
- Standard Contractual Clauses or SCCs means the clauses annexed to Commission Implementing Decision (EU) 2021/914. UK Addendum means the International Data Transfer Addendum issued by the UK Information Commissioner.
2. Roles and scope
- The Customer is the controller (Data Fiduciary) of Customer Personal Data, and DBTEZ is its processor (Data Processor) for consent records. Where the Customer is itself a processor for a third party, DBTEZ is its sub-processor, and the Customer confirms that its instructions are authorised by that third party.
- DBTEZ is an independent controller only for account, billing, security-log and support data that it needs to run its business. Its Privacy Policy governs that data, not this DPA.
- Annex 1 describes the subject matter, duration, nature and purpose of the processing, and the categories of data and data subjects.
3. Customer obligations
- The Customer is responsible for having a lawful basis, and for giving the notices and obtaining the consents that Applicable Data Protection Law requires, for the processing it instructs. This includes notices under section 5 of the DPDP Act and Rule 3 of the DPDP Rules.
- Where Customer Personal Data concerns children, the Customer must obtain verifiable consent from a parent or lawful guardian where the law requires it. It must not instruct tracking, behavioural monitoring or targeted advertising directed at children.
- The Customer must not upload protected health information under HIPAA. It must not upload other special-category or sensitive data unless it has a lawful basis and the Agreement allows it.
4. DBTEZ obligations
- Instructions. DBTEZ processes Customer Personal Data only on the Customer's documented instructions, including for transfers, unless the law requires otherwise. If it does, DBTEZ will tell the Customer before processing, unless the law forbids this. The Agreement, this DPA, and the Customer's configuration and use of the Service are the Customer's complete instructions. DBTEZ will tell the Customer promptly if it believes an instruction infringes Applicable Data Protection Law.
- Confidentiality. DBTEZ ensures that everyone it authorises to process Customer Personal Data is bound by confidentiality, and gives access only as needed to provide, secure and support the Service.
- Security. DBTEZ implements the technical and organisational measures in Annex 2. These are reasonable security safeguards under section 8(5) of the DPDP Act and Rule 6 of the DPDP Rules, and appropriate measures under GDPR Article 32. DBTEZ may update them, provided the overall level of protection does not fall.
- No other use. DBTEZ will not sell or share Customer Personal Data (as the CCPA defines those terms). It will not retain, use or disclose that data for any purpose other than providing the Service, including any commercial purpose. It will not combine it with personal data from other sources except as the Service requires. DBTEZ certifies that it understands and will comply with these restrictions.
- Assistance. Taking into account the nature of the processing, DBTEZ will assist the Customer, through the Service's features and otherwise on reasonable request, with: requests from data subjects; data protection impact assessments and prior consultations; and the Customer's own security and breach-notification obligations.
5. Data subject requests
If DBTEZ receives a request from a data subject about Customer Personal Data, it will not respond itself, except to direct the person to the Customer. It will pass the request to the Customer within five business days. The Service lets the Customer's administrators access, correct, export and erase Customer Personal Data, subject to the append-only nature of the consent ledger described in Annex 1. Where the Customer cannot do something itself, DBTEZ will help within a reasonable time. Requests under the DPDP Law, including grievance redressal within the period the DPDP Rules set, are the Customer's to answer as Data Fiduciary, and DBTEZ will assist.
6. Personal data breaches
- DBTEZ will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. This lets the Customer meet the 72-hour duties to report to the Data Protection Board of India under Rule 7 of the DPDP Rules and to supervisory authorities under GDPR Article 33.
- The notice will describe, as far as then known: the nature, extent, timing and location of the breach; the categories and approximate number of records and individuals affected; likely consequences; the measures taken or proposed to contain and remedy it; and a contact point. DBTEZ will provide further information as it becomes available.
- DBTEZ will take reasonable steps to contain and investigate the breach and prevent it recurring. It will cooperate with the Customer's notifications to individuals and authorities. Notifying a breach is not an admission of fault.
7. Sub-processors
- The Customer gives DBTEZ general authorisation to engage Sub-processors. Annex 3 lists those engaged at the date of this DPA.
- DBTEZ will notify the Customer's administrators at least 30 days before adding or replacing a Sub-processor. If the Customer has a reasonable data-protection objection, it may object in writing within that period. The parties will then discuss it in good faith. If DBTEZ cannot reasonably accommodate the objection, the Customer may terminate the affected part of the Service and receive a refund of prepaid fees for the remaining term.
- DBTEZ imposes data-protection obligations on each Sub-processor by written contract that are no less protective than this DPA. DBTEZ remains liable to the Customer for each Sub-processor's performance.
8. Location and international transfers
- DBTEZ keeps consent records, their backups and archives in India. Transfers out of India comply with section 16 of the DPDP Act. DBTEZ will not transfer Customer Personal Data to a country that the Government of India has restricted by notification.
- For personal data subject to the GDPR that is transferred to DBTEZ in India, or onward to a Sub-processor in a country without an adequacy decision, the SCCs apply and are incorporated by reference. Module 2 (controller to processor) applies where the Customer is a controller, and Module 3 (processor to processor) where the Customer is a processor. The following options apply:
- clause 7 (docking) applies;
- clause 9 option 2 (general authorisation), with the notice period in section 7.2;
- the optional wording in clause 11 does not apply;
- clauses 17 and 18: the law and courts of Ireland;
- Annexes I to III are completed by Annexes 1 to 3 of this DPA;
- the competent supervisory authority is determined under clause 13.
- For UK personal data, the UK Addendum applies and amends the SCCs, with the information in its tables completed by this DPA. For Swiss personal data, the SCCs apply as adapted for the Swiss Federal Act on Data Protection, with the Swiss Federal Data Protection and Information Commissioner as the competent authority.
- DBTEZ applies supplementary measures, including encryption in transit and at rest and challenging overbroad requests from public authorities. Where the law allows, it will notify the Customer of any legally binding request for disclosure of Customer Personal Data.
9. Audits and information
- DBTEZ will make available the information reasonably needed to show that it complies with this DPA. This includes its security documentation and policies and, once issued, its independent audit reports, shared under confidentiality.
- If that information is not enough to meet a requirement of Applicable Data Protection Law or a regulator, the Customer may audit, itself or through an independent auditor bound by confidentiality, at most once in any 12 months. The Customer must give at least 30 days' written notice, agree the scope in advance, audit during business hours without disrupting the Service or other customers' data, and bear its own costs. Additional audits are allowed after a personal data breach, or where a regulator requires one.
10. Return and deletion
During the subscription, the Customer may export Customer Personal Data at any time using the Service's export features. When the Agreement ends, the Customer has 30 days to export. DBTEZ then deletes Customer Personal Data from the live Service within a further 30 days, and from backups as they expire (currently within 14 days). The exception is where the law requires DBTEZ to keep it, in which case DBTEZ keeps it confidential, isolates it and processes it only for that purpose. On request, DBTEZ will confirm the deletion in writing.
11. Liability and term
Each party's liability under this DPA is subject to the exclusions and limits in the Agreement, except where Applicable Data Protection Law does not permit limiting it, or the SCCs provide otherwise. This DPA lasts as long as DBTEZ processes Customer Personal Data. Sections 6, 10 and 11 survive its end. This DPA is governed by the law that governs the Agreement, except where the SCCs require otherwise.
Annex 1: Description of the processing
| Categories of data subjects | The Customer's employees and contractors who use the Service; and the people (Data Principals) whose consent, preferences and rights requests the Customer records in it, such as its customers, users and applicants. |
|---|---|
| Categories of personal data | Identity and contact details of the Customer's users (name, work email, phone, job title); organisation, role and permission data; for Data Principals, a pseudonymous identifier, consent events (purpose, decision, notice version, time, channel), preference choices, decision checks, rights and grievance requests, and contact details held encrypted in a store separate from the consent ledger; webhook delivery records; audit history; and any other personal data the Customer chooses to store. |
| Special categories / sensitive data | Not intended. Only as the Customer chooses and the Agreement permits. |
| Nature and purpose | Hosting, storage, retrieval, display, signing and sealing of consent records into an append-only ledger, answering decision checks, delivering webhooks and notifications, backup and support, all to provide the Service under the Agreement. |
| Frequency | Continuous, for the term of the Agreement. |
| Duration and retention | The term of the Agreement plus the return and deletion periods in section 10. Consent ledger entries are append-only. On erasure, personal contact details are destroyed and the ledger keeps only pseudonymous proof, for the period the Customer configures or the law requires. |
| Location | Consent records, backups and archives are kept in India. |
| Data exporter / importer | Exporter: the Customer (controller or processor). Importer: DBTEZ (processor). |
Annex 2: Technical and organisational measures
| Encryption | TLS 1.2+ with HSTS for all traffic. AES-256 encryption at rest for storage volumes holding databases, files and backups. Contact details of Data Principals are encrypted separately from the consent ledger. |
|---|---|
| Tenant isolation | Each organisation's data is separated in the database and enforced on every request path. |
| Identity and access | Single sign-on through the Service's sign-in system or the Customer's identity provider; optional multi-factor authentication; session timeouts; role-based permissions configured by the Customer; immediate effect of deactivation; no shared accounts. |
| Administrative access | Production access limited to named DBTEZ staff, using individual key-based authentication. Management interfaces are not exposed publicly. Least privilege applies. |
| Logging and audit | An immutable history of important changes to records; security and access logs kept for at least one year; recorded acceptance of legal documents. |
| Availability and resilience | Daily backups of databases and files, retained for 14 days; monitored services; documented deployment and rollback procedures. |
| Network security | Host firewall exposing only HTTPS and SSH; databases and object storage bound to loopback or private networks. |
| Secure development | Code review through merge requests; strict typing; parameterised database access; separation of development, test and production environments; dependency and secrets hygiene (secrets kept out of source control). |
| Personnel | Confidentiality obligations, security awareness, and access removed promptly on role change or departure. |
| Vendors | Due diligence and written data-protection terms for every Sub-processor. |
| Incident response | A documented breach-response process with the notification timelines in section 6. |
Annex 3: Sub-processors
| Sub-processor | Purpose · Location |
|---|---|
| Hosting provider (to be named before production use) | Hosting, compute, database and file storage, backups · India |
| Postmark (ActiveCampaign, LLC) | Transactional email delivery · United States |
| Payment processor (to be named before production use) | Payment processing for the Customer's subscription, where the Customer pays online. Receives billing data only, not Customer Data |
Signatures
| Customer | DBTEZ Technologies Private Limited | |
| Name | Gerard Antony | |
| Title | Founder & CEO | |
| Signature | ||
| Date | ||
| Privacy contact | [email protected] |