Data processing terms
Last updated 20 October 2026
These terms say how we handle personal data for our clients, as their processor. They form part of every proposal that names them.
1. Who these terms apply to
1.1 These terms are made by Dubs Enterprises Pvt. Ltd.
1.2 For anything about data under these terms, email privacy@dubsenterprises.com.
1.3 When these terms apply. They apply when we handle personal data for you as part of work in a proposal you have signed: a website, an online store, a WhatsApp flow, an assistant, back-office automation, a custom app, or a monthly care plan for any of them.
1.4 Words we use.
- Personal data: any information about a person who can be identified, such as your customers' names, phone numbers, orders and chat messages, or your staff's logins.
- Controller: the business that decides why and how personal data is used. India's DPDP Act calls it the Data Fiduciary.
- Processor: a business that handles personal data only for a controller and on its instructions. The DPDP Act calls it the Data Processor.
- Provider: another company we use to handle your data (the law calls it a sub-processor).
- Breach: see clause 8.1.
- Data protection law: India's Digital Personal Data Protection Act 2023 and the DPDP Rules 2025 (and, until their duties start, section 43A of the IT Act 2000 and its rules of 2011); the EU GDPR; the UK GDPR and the Data Protection Act 2018; the Swiss Federal Act on Data Protection; and any other law named in your proposal.
- The EU clauses: the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914).
1.5 Your role and ours. You decide why and how your customers' data is used, so you are the controller. We handle it only to do the work for you, so we are your processor.
1.6 If you are a processor yourself. If you hold the data as a processor for another business, say so in the proposal. We then follow that business's instructions as you pass them to us, and clause 9.2 uses the EU clauses for that case.
1.7 What these terms don't cover. The contact details of you and your staff, which we use to run the project and send invoices, are ours to look after as a controller. Our privacy notice applies to them.
1.8 For businesses only. Our services are for businesses and professionals, not for personal or household use, as our Terms say.
1.9 How these terms become part of our agreement. They become part of our agreement when we both sign, by hand or electronically, a proposal that names them and fills in Annex A. We don't touch real personal data before then. Each of us keeps a copy of the version that applied.
1.10 If documents disagree. On data protection, this order applies: first the EU clauses or the UK Addendum, where they apply (clause 9); then any line in Annex A that gives the people whose data it is more protection; then these terms; then your proposal; then our Terms.
1.11 Representatives. When we act only as your processor, you remain the contact for the people and authorities in the EU and the UK. If we appoint representatives there for our own website, our privacy notice names them, and you can reach them about this work too.
2. What we do with the data
2.1 Set in each proposal. For each project, Annex A of the proposal sets out the subject of the work; how long it lasts (from the start of the work until the project or care plan ends, plus the time in clause 10); the nature and purpose of what we do with the data; the kinds of personal data; the kinds of people the data is about; and where the data is kept and which providers hold it.
2.2 Only for your purpose. We use your data only for the purpose in your proposal, and only as much of it as that purpose needs. We never sell it, never use it for our own marketing or our own products, never use it to train AI models, and never put it in examples or case studies.
2.3 Your accounts, in your name. Your data stays in accounts in your name: hosting, store, WhatsApp Business, payments, analytics, email and any AI model provider. We work in them as an invited user with our own logins, and we never ask for your owner password. By default we keep none of your data in accounts of ours (clause 6.2).
2.4 Your data is always yours. Our Terms say the code we make for you becomes yours once each stage is paid. That payment rule applies to the code only, never to your data. We never hold back your data over an unpaid invoice.
2.5 Made-up data first. We build and test with made-up data wherever we can. We work with real data only when a task needs it, and in your accounts rather than in copies.
2.6 Children's data and sensitive data. Tell us in the proposal if the data includes anyone under 18, or sensitive data such as health, money matters, identity numbers, passwords, or anything the GDPR treats as a special category. We start that part of the work only once the proposal lists the extra steps and we have both signed it, and we may decline it. As a minimum:
- we build nothing aimed at children, and no tracking, profiling or targeted ads that reach children;
- where Indian law requires a parent's or guardian's verifiable consent before a child's data is used, your flow asks for it and you check it;
- sensitive data stays in your accounts, is encrypted where the platform allows, can be reached only by the people named in Annex A, and never goes into an AI tool unless Annex A names that tool.
3. Your instructions
3.1 Written instructions. We act only on your documented instructions: these terms, your proposal, and what you or the contact named in Annex A tell us in writing. Email is enough.
3.2 Moving data abroad. That includes sending data to another country: we do it only as these terms and your instructions allow, unless a law we are subject to requires it. If a law does, we tell you before we act, unless that law forbids telling you.
3.3 If an instruction looks unlawful. If we think an instruction breaks data protection law, we tell you straight away and may pause that part of the work until we have agreed what to do.
3.4 Your part. You are responsible for having a lawful reason to collect and use your customers' data, for telling them about it in your own privacy notice (including the providers in your accounts and any we engage), and for any consents you need. When the proposal includes it, we build what that needs, for example a consent box that starts unticked, or a short notice under a form. We may give you draft wording to start from. It isn't legal advice: you decide what to use.
4. Confidentiality of our staff
4.1 Only those who need it. Only the people working for us who need your data for your project can reach it, and only for as long as they need it.
4.2 Bound to confidence. Each of them signs a written confidentiality undertaking before getting access, covering the time during and after their work with us.
4.3 Trained and removed. Each of them knows these terms and our client-work rules before they get access. We remove a person's access as soon as a task no longer needs it, and on the day they stop working with us.
4.4 Contractors. A contractor who is not on our staff gets access to your data only if Annex A names them, or after we have told you under clause 6.4. They have the same duties as our staff.
5. Security
5.1 Our measures. We protect your data with the technical and organisational measures in Annex B, suited to the risk to the people whose data it is (GDPR art. 32; DPDP s.8(5) and Rule 6; until the DPDP duties start, IT Act s.43A and the 2011 rules).
5.2 Kept up to date. We review the measures whenever a build changes, and keep them up to date. A change to a measure never lowers the overall protection.
5.3 Your own accounts. The security of the accounts in your name is yours to manage: your own users' passwords and two-step sign-in, and your providers' own security. We recommend settings, and set up what the proposal includes. Your providers' access logs are yours to keep. Where the proposal includes it and the platform allows, we switch on logs that show who reached the data, kept for at least one year.
5.4 Our own accounts. For any account of ours that holds your data, we keep the record of who signed in and what changed for one year.
6. Other providers
6.1 Providers in your accounts. The services in your own accounts (for example your hosting, store platform, payment provider, email, any AI model provider, and the WhatsApp Business Platform, which we connect directly through Meta's Cloud API in your account, with no other company in between) work for you under your own contracts with them. We don't engage them; we use them only as your invited user, and your privacy notice names them. When we recommend one, we tell you what we know about where it handles data and whether it offers data processing terms, and you choose it and sign up in your name.
6.2 Providers we engage. By default we engage none. We use another company to handle your data only if Annex A names it. If Annex A says part of the work runs on our own Cloudflare account, Cloudflare, Inc. (United States) handles that data for us under its Customer Data Processing Addendum, which applies to our account through Cloudflare's terms. We give you a copy on request, and Cloudflare publishes the list of its own providers.
6.3 Our own tools stay clear of your data. We don't put your data into our own email, chat apps, personal devices, screenshots, tickets, code repositories or test files. We don't put it into any AI tool unless Annex A names that tool and the tool runs under business terms that say your data is not used to train models. If you send us real customer data some other way, for example in an email, we move it to where it belongs or delete it within 2 working days, deleted items included, and tell you.
6.4 Your general permission, and changes. By signing the proposal, you allow us to use the providers Annex A names. Before we add or replace a provider we engage, we tell you by email at least 30 days ahead, with its name, what it will do and where it handles data. We pass on any notice Cloudflare gives us about its own providers as soon as we get it.
6.5 Your right to object. You can object within those 30 days, on reasonable data protection grounds. We then try to find another way. If we can't, you can end the part of the work that needs that provider: you pay for the work done in it so far, and we refund anything you paid in advance for the time after it ends. If a provider fails and the only fix is a new one, we pause that processing rather than move your data without notice, unless you agree in writing.
6.6 Same duties down the line. Each provider we engage is bound in writing to data protection duties at least as protective as these terms, and we stay responsible to you for what it does with your data.
7. Helping you with requests and assessments
7.1 Requests that reach us. If one of your customers, or anyone else, asks us about their data, we pass the request to you the same working day. We don't answer it ourselves unless you ask us to.
7.2 Helping you answer. We help you answer people's requests about their data: to see, correct, complete, update, delete or move it, to restrict or object to its use, or to withdraw consent, and under India's DPDP Act to have a grievance handled or to name a nominee. Often that means finding the data in your accounts, exporting it or deleting it there. We act within 5 working days of your asking, or sooner when your legal deadline needs it.
7.3 Assessments and authorities. We help you with your own duties on security, breaches, data protection impact assessments and consulting an authority before high-risk processing (GDPR arts. 32 to 36). If you are named a Significant Data Fiduciary in India, we help with your yearly impact assessment and audit (DPDP s.10). Our help takes into account what the work involves and what we know.
7.4 Cost of this help. Passing on requests, finding, exporting or deleting a person's data in your accounts, and our help with a breach on our side are free. Larger work, such as writing an impact assessment with you or answering an authority's audit, is charged at the rates in your proposal, and we agree it in writing before we start. We never charge for help that is needed because we broke these terms.
7.5 If an authority asks us. If a data protection authority, or the Data Protection Board of India, asks us about your data, we tell you, unless the law forbids it, and work with you on the answer.
8. Breaches
8.1 What counts. A breach is anything that lets someone see, change, lose or block personal data they should not: for example someone getting into an account, data sent to the wrong person, a lost laptop or phone, or data deleted by mistake.
8.2 Telling you. If a breach affects your data, whether on our side or at a provider we engage, we tell you without undue delay and within 48 hours of becoming aware of it, that is, of being reasonably sure it has happened. We tell you by email to the contact named in Annex A, and by phone too where we can. If we suspect a breach but are not yet sure, we tell you within the same 48 hours what we are checking.
8.3 What we tell you. We tell you what we know: what happened and when; which data and whose (kinds of people, roughly how many, which countries); what it could mean for them; what we have done and what we suggest; and who to contact at our end. If we don't know everything yet, we send what we have and follow up as we learn more.
8.4 What we do. We act straight away to stop the breach and limit the harm, keep the evidence, and record the breach and every step we take in our breach log.
8.5 Who tells others. You decide whether to tell the authorities and the people affected, and you do the telling; we help with the facts and the wording. We tell your customers or an authority ourselves only if you ask us to, or a law requires it of us. For example, India's CERT-In directions require certain cyber incidents to be reported within 6 hours. If a law does require it, we tell you first where we can, and share only what the report needs.
8.6 Breaches at your own providers. If a breach happens in an account in your name, the provider you contract with tells you under its own terms. If we learn of it first, we tell you on the same basis as clause 8.2.
9. Transfers
9.1 Where we work. We are in India and work on your data from India. Providers we engage may handle it in other countries; Annex A says where.
9.2 Clients in the EU or the EEA. If the GDPR applies to your processing, sending your data to us in India is a transfer under the GDPR. The EU clauses then apply between us and form part of these terms: module 2 where you are the controller, module 3 where you are a processor for another business. Annex A fills in their Annex I, Annex B their Annex II, and the providers named under clause 6 their Annex III. The choices in them are:
- clause 7 (docking): included;
- clause 9(a): option 2, general permission, with the 30 days' notice in clause 6.4;
- clause 11: the optional wording is not used;
- clause 13: the authority of the EU country where you are established; if you are not established in the EU but have a representative there, the authority of that representative's country; otherwise the authority of the EU country where the people whose data it is mainly are;
- clause 17: option 1, the law of the EU country where you are established, or Ireland if you are not established in the EU;
- clause 18: the courts of the same country.
If the European Commission adopts clauses for importers whose processing is already subject to the GDPR, and they apply to this work, we use those instead.
9.3 Clients in the UK. If you are in the UK, the ICO's International Data Transfer Addendum to the EU clauses (version B1.0, in force since 21 March 2022) also applies, with the details from Annex A. In its Table 4, neither of us may end the Addendum when the ICO changes it, so the ICO's revised versions apply as the ICO issues them.
9.4 Clients in Switzerland. If the Swiss Federal Act on Data Protection applies, the EU clauses apply with the changes Swiss law requires: the Federal Data Protection and Information Commissioner is the authority for transfers under Swiss law, “Member State” also covers Switzerland so that people there can bring claims where they live, and references to the GDPR include the Swiss Act.
9.5 Clients in India. If you are in India, these terms are the contract the DPDP Act requires between a Data Fiduciary and its Data Processor (s.8(2)). Your data may be handled outside India only by the providers in Annex A. We won't send it to a country the Indian government has restricted under s.16, and we follow any conditions set under the DPDP Rules for data going outside India. If a sector rule makes you keep data in India, say so in the proposal and we keep it there. Until the DPDP duties start, where your data includes sensitive personal data under the IT Act's 2011 rules, we and any provider we engage keep at least the protection those rules require, and send it to another company only where the work needs it or the person has agreed.
9.6 Clients outside India. When we handle data of people outside India under a contract with a client outside India, section 17(1)(d) of the DPDP Act means most of the Act's duties don't apply to that work. The duty to keep the data secure (s.8(5)) still does, and we keep to it. If some of the people are in India, we handle their data as the Act requires and tell you.
9.7 US state privacy laws. If US state privacy laws apply to you, such as California's, we act as your service provider: we don't sell or share the data, don't keep, use or disclose it for any purpose other than the work in your proposal, don't combine it with data from elsewhere except as those laws allow, and tell you if we can no longer meet these duties.
9.8 Other countries. If your country has its own rules for processor contracts or data going abroad (for example Saudi Arabia, the UAE, Australia or Canada), your proposal adds what they need.
9.9 Requests from public authorities. If a court or public authority anywhere asks us for your data, we tell you straight away unless the law forbids it, check that the request is lawful, challenge it where there are good grounds, and give only the minimum the request needs. Some Indian laws, such as section 69 of the IT Act, can forbid us to tell you about a request; if so, we tell you as soon as we lawfully can.
9.10 Our transfer assessment. Before we receive data from you under the EU clauses, we give you our written assessment of the Indian laws that let public authorities ask for data (clause 14 of the EU clauses), for you to use in your own.
9.11 If we can't keep to these terms. If we can no longer meet the transfer terms in this clause, we tell you straight away, and you can stop the transfer or end the affected part of the work.
10. End of the project
10.1 Return or delete. Your data already lives in accounts in your name, so at the end it stays with you. When the project ends (including any care plan), or earlier if you ask, within 30 days we:
- delete every copy of your data that we hold (exports, test copies, anything on an account of ours), or first hand those copies back to you, as you choose;
- remove every login and key of ours from your accounts;
- confirm both to you in writing.
10.2 Restore copies. A copy in a provider's automatic backups or restore history on an account of ours goes when that history runs out, within 30 days at most, and we use it only to recover from a fault. Backups in your own accounts are yours to keep or delete.
10.3 If a law makes us keep something. If a law requires us to keep some of your data, for example access logs that India's CERT-In directions or the DPDP Rules require for up to one year, we tell you what and why, keep it only for that reason, protect it under these terms, and delete it when the law allows.
11. Audits
11.1 Our record. We keep a record of what we do with your data: which data, which providers, which countries, who at our end has access, and the security we use (GDPR art. 30(2)).
11.2 Information on request. When you ask, we give you the information you need to check that we keep these terms, including that record, our security measures, and our providers' own audit reports and certificates.
11.3 One audit a year. Once a year, you, or an independent auditor bound to keep what they see confidential, may audit how we handle your data, with 30 days' written notice, in working hours. We first try to answer the audit with documents and a call. Providers we engage are audited through their own reports and certificates, not visits.
11.4 Extra audits, and costs. An audit more often than once a year is possible after a breach that affects your data, where there are signs we are not keeping these terms, or when an authority requires it. Each of us pays our own costs. If an audit shows we have broken these terms in a way that matters, we pay its reasonable cost and fix what it found.
12. Law
12.1 Which law. Indian law governs these terms, except where the EU clauses or the UK Addendum name another law for the matters they cover (clause 9).
12.2 Disputes. We first try to settle a dispute by talking, for at least 30 days. If that doesn't settle it, the courts of the city of our registered office decide it, except where clause 9 names other courts.
12.3 Liability. The limits on liability in our Terms apply to these terms too: capped at the fees you have paid for the stage concerned, or for care at the care fees you paid in the 12 months before the event, with no liability for indirect loss. They apply only as far as the EU clauses and the law allow. Nothing in these terms limits what either of us owes the people whose data it is.
12.4 Changes. We may update these terms, for example when the law changes. The version in your signed proposal keeps applying to that project. For a care plan, we tell you of a new version by email at least 30 days before it applies to you, and you can end care before then under the old version. A change never lowers the protection for your data without your written agreement, unless the law requires it.
12.5 If one part fails. If any part of these terms can't be enforced, the rest still applies.
12.6 Contact. Questions about these terms: privacy@dubsenterprises.com.
Annex A. Project details (filled in each proposal)
- You
- Business name, address, registration number if any, and the contact for data matters (email and phone, also used for breaches under clause 8.2)
- Us
- Our details from clause 1.1
- Your role
- Controller, or processor for another business (clause 1.6)
- Subject
- What the work is
- How long
- Start date; end (the project or care plan ends); then clause 10
- Nature and purpose
- What we do with the data and why
- Kinds of personal data
- For example names, phone numbers, addresses, orders, chat messages, staff logins
- Children's or sensitive data
- None, or which, with the extra steps agreed (clause 2.6)
- Kinds of people
- For example your customers, your staff, people who message you
- Your accounts that hold the data
- Your providers, in your name (clause 6.1)
- Providers we engage
- None, unless named here with what each does and where (clause 6.2)
- People outside our staff with access
- None, unless named here (clause 4.4)
- AI tools that see the data
- None, or which, with their business terms (clause 6.3)
- Logs
- Which access logs we switch on in your accounts, and for how long (clause 5.3)
- Countries where the data is handled
- For example India, and the countries your providers and any we engage use
- How often data moves
- One-off, or continuous while the work runs
- Transfer terms
- None; EU clauses module 2 or 3; UK Addendum; Swiss changes; US state law terms; India; other (clause 9)
- For the EU clauses
- Your EU country (clauses 13, 17 and 18), or none
- Deletion rule
- For every table, inbox and store of personal data the build creates, the time after which it is deleted
Annex B. Security measures
Access
- One login per person, two-step sign-in on, no shared passwords.
- The least access that does the job: read-only where it is enough.
- Access removed as soon as a task no longer needs it, and on a person's last day (clause 4.3).
- On any account of ours that holds your data, a record of who signed in and what changed, kept for one year (clause 5.4).
Where your data may be
- Only in your accounts and with the providers in Annex A.
- Never on personal devices, in our inbox, in chat apps, in screenshots, in tickets, in a code repository or in test files.
- In an AI tool only if Annex A names it and it runs under business terms that say the data is not used to train models.
Protecting it
- Encrypted in transit (HTTPS) wherever it moves.
- On any account of ours, stored encrypted at rest.
- In your accounts, encrypted at rest where the platform offers it; sensitive data always where the platform allows (clause 2.6).
- Backups: in your accounts, as your care plan or proposal says; restore history on our accounts ends within 30 days (clause 10.2).
How we work with it
- Build and test with made-up data wherever we can.
- Logs hold counts, ids and error codes, never what your customers wrote.
- Exports only when a task needs one: in an encrypted file, deleted the same day the task is done, and noted in our client register.
- Every table, inbox and store the build creates has a deletion rule agreed with you.
- These measures are reviewed whenever a build changes (clause 5.2).
People
- Everyone with access has signed a confidentiality undertaking and knows these rules first (clause 4).
When something goes wrong
- Our breach routine: stop it, keep the evidence, record the times, tell you within 48 hours (clause 8), and log it in our breach log.