VachanSetu

Privacy notice

Last updated 20 November 2026

Draft. This document is under legal review and will change before the product is offered for production use.

The short version

  • VachanSetu is a consent management platform for organisations that are Data Fiduciaries under the Digital Personal Data Protection Act, 2023. When an organisation uses VachanSetu, that organisation decides what consent data is recorded and who sees it. We process it on its behalf and only on its instructions.
  • For an organisation's account, billing, support and our website, we are responsible for the data and explain here what we do with it.
  • We do not sell personal data and do not use it for advertising.
  • Consent records, their backups and the archive are kept in India. Some service providers, such as email delivery, may process limited data outside India under contractual safeguards.
  • You can ask to access, correct or delete your data, withdraw consent, and complain to us or to a regulator. Section 10 explains how.

1. Who we are

VachanSetu ("the Service") is provided by DBTEZ Technologies Private Limited ("DBTEZ", "we", "us"), a company incorporated in India (CIN U72900KA2018PTC119829), with its office at WeWork, Block-L, Embassy TechVillage, Outer Ring Road, Devarabisanahalli, Bellandur, Bengaluru, Karnataka 560103, India.

This policy covers the VachanSetu application, its API, the sign-in and sign-up pages, our support channels and the vachansetu.in website. It does not cover the consent notices, preference centres or rights pages that an organisation publishes to its own users with VachanSetu. For those, that organisation's own privacy notice applies.

2. Our role and your organisation's role

Privacy law gives different duties to the party that decides how data is used and to the party that processes it on that party's behalf.

DataWho decides (controller / Data Fiduciary)Our role
Customer Data: everything an organisation and its users put into VachanSetu, such as its purpose inventory, notices, consent records, decision checks, rights requests and the personal data of the people those records concern (Data Principals)The organisation (our customer)Processor / Data Processor. We act only on the customer's documented instructions under our agreement with it, including our Data Processing Addendum.
Account and Service Data: sign-in identity, organisation membership, billing contacts, support conversations, security logs and service usage recordsDBTEZController / Data Fiduciary
Website and enquiry data from vachansetu.in, including contact requestsDBTEZController / Data Fiduciary

If you are a person whose consent an organisation records with VachanSetu, that organisation controls your data. It decides what is collected and how long it is kept. Please send requests about that data to the organisation. If you contact us, we will pass your request to it and help it respond.

DBTEZ is not a Consent Manager registered under section 6 of the Digital Personal Data Protection Act, 2023.

3. What we collect

3.1 Information you or your organisation give us

  • Identity and contact: name, work email address, phone number (if given), job title, time zone and language.
  • Organisation and role: the organisations you belong to, your roles and permissions, and invitations you send or accept.
  • Sign-in credentials: a password stored only as a salted hash by our sign-in service, or the identifier returned by your organisation's single sign-on provider. If multi-factor authentication is on, we also hold its configuration.
  • Billing: billing contact, company name, address, tax identifiers (such as GSTIN) and invoices. Online payments are handled by a payment processor. We never see or store full card numbers.
  • Support and feedback: what you write to us, attachments, and our replies.
  • Customer Data: whatever your organisation records in VachanSetu (see section 2). This includes consent events, a pseudonymous identifier for each Data Principal, and contact details that the Service keeps encrypted in a store separate from the consent ledger.

3.2 Information collected automatically

  • Security and service logs: IP address, browser and device type, time of each request, the action called, error references, and sign-in events (success, failure, multi-factor).
  • Audit history: who created, changed, approved or removed a record, and when. This history is part of the Service and your organisation can see it.
  • Acceptance records: which version of this Privacy Policy and our Terms you accepted, when, through which screen, and your browser's user-agent string.
  • Essential cookies and browser storage used to keep you signed in and remember screen state (section 13). We use no advertising or third-party analytics cookies.

3.3 Information from others

We may receive your details from your organisation (for example when an administrator invites you) or from your single sign-on provider.

4. Why we use it, and on what basis

We use personal data only for the purposes below. Under India's Digital Personal Data Protection Act, 2023 ("DPDP Act") we rely on your consent, or on a legitimate use allowed by section 7 of the Act, such as data you voluntarily provide for a specified purpose, employment-related purposes for your employer, or a legal obligation. Under the EU and UK GDPR, the legal bases are listed for each purpose.

PurposeData usedGDPR legal basis
Provide the Service: create and secure your account, sign you in, apply your organisation's permissions, store and display Customer DataIdentity, organisation and role, credentials, Customer Data, logsPerformance of a contract (Art. 6(1)(b)); for Customer Data, the customer's instructions
Send service email: invitations, password resets, alerts and notices you or your organisation configureName, email, notification preferencesContract; legitimate interests
Keep the Service secure: detect abuse, investigate incidents, prevent fraud, enforce our TermsLogs, audit history, account dataLegitimate interests (Art. 6(1)(f)); legal obligation
Support you and improve reliability: diagnose errors, answer requests, fix defectsSupport content, error references, logsContract; legitimate interests
Bill and keep business recordsBilling data, invoicesContract; legal obligation (tax and accounting law)
Product announcements to business contactsName, work email, companyConsent where required, otherwise legitimate interests. You can opt out at any time.
Comply with law and respond to lawful requestsAs requiredLegal obligation (Art. 6(1)(c))

We do not use Customer Data for our own purposes, such as marketing or building profiles. We do not make decisions about you that produce legal or similarly significant effects based solely on automated processing.

5. Automated decision checks

The Service answers decision checks from your organisation's systems, for example whether a person has consented to a purpose. The answer follows the consent records and the rules your organisation configures. We do not add any other criteria. Your organisation is responsible for how it uses the answer.

6. Who we share it with

We do not sell or rent personal data, and we do not share it for cross-context behavioural advertising. We share it only with:

  • Your organisation and its authorised users, according to the permissions your organisation sets.
  • Sub-processors who help us run the Service, under written contracts that require confidentiality, security and processing only on our instructions. The current list is in Annex 3 of our Data Processing Addendum.
  • Professional advisers (lawyers, auditors, insurers) under confidentiality.
  • Authorities, when the law requires it. Where the law allows, we notify the affected customer first and challenge requests that are overbroad.
  • A successor in a merger, acquisition or sale of assets. This policy, or one at least as protective, will continue to apply.

We give customers at least 30 days' notice before adding or replacing a sub-processor. A customer may object to the change on reasonable data-protection grounds.

7. Where data is stored and transferred

Customer Data, including consent records, backups and the archive, is stored in India. Account Data is stored in India. Some data may be processed outside India by sub-processors: for example, the content and recipient address of transactional email. The DPDP Act permits such transfers, except to countries the Government of India restricts by notification. We will not transfer data to such a country.

When personal data of people in the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, we use the European Commission's Standard Contractual Clauses, together with the UK Addendum or Swiss amendments where relevant, plus supplementary measures. You can ask us for a copy of these safeguards.

8. How long we keep it

DataRetention
Customer DataFor as long as the customer's subscription is active and as the customer configures. Consent ledger entries are append-only and cannot be edited. When personal details are erased, the contact details are destroyed and the ledger keeps only the pseudonymous proof, for the period the customer configures or the law requires. After the subscription ends, the customer has 30 days to export its data. We then delete it within a further 30 days, unless the law requires us to keep it.
BackupsEncrypted backups roll off automatically, within 14 days of creation.
Account DataWhile your account is active. Members are deactivated, not erased, so your organisation's audit history stays accurate. When your organisation or you ask us to delete an account, we erase or anonymise personal details unless the law requires us to keep them.
Security and access logsAt least one year, as the DPDP Rules require, and no longer than 2 years unless an investigation needs them.
Records of accepting this policy and the TermsFor as long as the account exists, and then for the limitation period for claims (currently up to 8 years), so we can show what was agreed.
Billing and tax recordsFor the period Indian tax and company law requires (currently up to 8 years).
Support conversationsUp to 3 years after the request is closed.
Marketing contactsUntil you opt out, or after 2 years without engagement.

9. How we protect it

We take reasonable security safeguards, as the DPDP Act and Rules require, and appropriate technical and organisational measures under GDPR Art. 32. Our security programme is designed around the AICPA Trust Services Criteria (security, availability, confidentiality, processing integrity and privacy) that are used for SOC 2 reports. We do not hold a SOC 2 report or an ISO 27001 certificate today. Measures include:

  • Encryption in transit (TLS 1.2 or later, with HSTS) and encryption at rest (AES-256) of storage volumes holding databases, files and backups.
  • Tenant isolation enforced in the database, not only in the application.
  • Single sign-on, optional multi-factor authentication, session timeouts, and immediate effect when an administrator deactivates a member.
  • Role-based access with least privilege. Administrative access to production is limited to named staff using key-based authentication.
  • An immutable audit history of important changes, and security logging with review.
  • Daily backups, retained for 14 days, and documented change management for deployments.
  • Vendor due diligence for sub-processors, confidentiality commitments from staff, and security awareness training.

10. Your rights

Depending on where you live, you may have the right to:

  • Access a summary of the personal data we process about you, the processing activities, and who we have shared it with (DPDP Act s.11; GDPR Art. 15).
  • Correct, complete or update inaccurate data (DPDP s.12; GDPR Art. 16).
  • Erase data that is no longer needed or that you consented to and now withdraw (DPDP s.12; GDPR Art. 17).
  • Withdraw consent at any time, as easily as you gave it. Withdrawal does not affect processing that happened before it.
  • Object to or restrict processing based on legitimate interests, including direct marketing (GDPR Arts. 18, 21).
  • Data portability: receive data you provided in a structured, machine-readable format (GDPR Art. 20). Organisation administrators can also export records from within VachanSetu.
  • Nominate another person to exercise your rights if you die or become incapacitated (DPDP s.14).
  • Grievance redressal: complain to us first (section 16). We will resolve it within the time the DPDP Rules allow, and no later than 90 days.
  • Complain to a regulator: the Data Protection Board of India, the supervisory authority in your EU member state, or the UK Information Commissioner's Office.
  • If you live in a US state with a consumer privacy law: know, delete and correct your data, and not be discriminated against for using these rights. We do not sell or "share" personal data as those laws define it.

How to make a request: email [email protected], or use the profile and settings screens in VachanSetu. We may need to verify your identity. We respond within one month (extendable by two months for complex requests, as GDPR permits), and within the DPDP timelines. If your request concerns Customer Data, we will send it to your organisation, which decides on it.

11. Children's data

VachanSetu is a business service and is not directed at children. We do not knowingly collect personal data directly from anyone under 18 (the age of a "child" under the DPDP Act), or under the age of digital consent in the EU. A customer may record consent concerning children. In that case the customer is the Data Fiduciary or controller. It must obtain verifiable consent from a parent or lawful guardian where the law requires it. We process such records only on the customer's instructions. If you believe we have collected a child's data in error, contact us and we will delete it.

12. Health information

VachanSetu is not designed to store health records. Customers should not put protected health information, as defined by the US Health Insurance Portability and Accountability Act, into the Service. Other health or sensitive information should be stored only where your organisation has a lawful basis and our agreement permits it.

13. Cookies and browser storage

We use only the cookies and browser storage needed to sign you in and run the Service. Because these are strictly necessary, the law does not require consent for them. We use no advertising cookies, cross-site tracking or third-party analytics. If we ever add optional cookies, we will ask first.

PurposeSet byDetailDuration
Keep a sign-in attempt together and protect it from forgerySign-in serviceSession cookiesSession
Keep you signed inSign-in serviceIdentity and session cookiesSession, or up to the "Remember me" period your organisation allows
Remember your username, only if you tick "Remember me"Sign-in serviceCookieUp to 1 year
Hold your current session token and sign-in configurationVachanSetu appBrowser storageUntil you sign out
Remember filters, expanded rows and drafts while the tab is openVachanSetu appSession storageUntil the tab closes

You can delete cookies in your browser settings. If you do, you will be signed out.

14. Data breaches

If a personal data breach affects data we hold, we will:

  • Inform affected customers without undue delay, and give them the information they need to meet their own obligations.
  • Where we are the Data Fiduciary, notify affected individuals without delay. We will report to the Data Protection Board of India within the time the DPDP Rules set (an initial intimation without delay and a detailed report within 72 hours).
  • Notify the relevant GDPR supervisory authority within 72 hours where required.

15. Changes to this policy

We will post any change here with a new date. If a change materially affects how we use personal data, we will tell organisation administrators by email or in the product at least 30 days before it takes effect. Where your consent is needed, we will ask for it again.

16. Contact and grievance officer

TopicContact
Privacy requests, security issues and support[email protected]
Grievance Officer (DPDP Act; Information Technology Act, 2000)Gerard Antony, Founder & CEO, DBTEZ Technologies Private Limited, WeWork, Block-L, Embassy TechVillage, Outer Ring Road, Devarabisanahalli, Bellandur, Bengaluru, Karnataka 560103, India · [email protected]

If we have not resolved your grievance, you may complain to the Data Protection Board of India once you have used our grievance process.