Website information
Data processing agreement
How Zenffy processes your customers’ personal data for you, as your processor.
Zenffy Solutions Private Limited
Version 1.0. Last updated: 19 November 2026
1. About this agreement
1.1 This data processing agreement (“DPA”) is between Zenffy Solutions Private Limited (CIN: U62013KL2026PTC106027), Nedumpurath, College Road, Hostel Junction, Muvattupuzha, Ernakulam, Kerala 686661, India (“Zenffy”, “we” or “us”), and the business that uses Zenffy (“you”).
1.2 This DPA forms part of our terms of service, or of any other written agreement for Zenffy between you and us (together, the “Agreement”). It applies whenever we process Customer Personal Data for you, from the day you accept the Agreement. You don’t need to sign it. If you want a signed copy, email hello@zenffy.com and we will send you one.
1.3 On data protection, this DPA takes priority over the rest of the Agreement. Where the Standard Contractual Clauses apply, they take priority over this DPA.
2. Definitions
- “Applicable Data Protection Law” means every data protection and privacy law that applies to the processing of Customer Personal Data under the Agreement. Depending on where you and your customers are, that can include the EU General Data Protection Regulation (Regulation (EU) 2016/679, the “GDPR”); the UK GDPR and the UK Data Protection Act 2018; the Swiss Federal Act on Data Protection (the “FADP”); India’s Digital Personal Data Protection Act, 2023 and the rules made under it (the “DPDP Act”); and US state privacy laws such as the California Consumer Privacy Act (the “CCPA”).
- “Customer Personal Data” means personal data that we process for you, as your processor, to provide Zenffy. Annex I describes it.
- “Contact” means a person who talks to your agent, on your website or on WhatsApp.
- “Security Incident” means a breach of our security leading to the accidental or unlawful destruction, loss or alteration of Customer Personal Data, or its unauthorised disclosure or access.
- “Sub-processor” means a third party we engage to process Customer Personal Data.
- “Standard Contractual Clauses” or “Clauses” means the standard contractual clauses annexed to European Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
- “UK Addendum” means the International Data Transfer Addendum to the European Commission’s Standard Contractual Clauses, issued by the UK Information Commissioner (version B1.0, in force from 21 March 2022).
- “Controller”, “processor”, “data subject”, “personal data” and “processing” have the meanings given in the GDPR. Where the DPDP Act applies, “controller” includes a Data Fiduciary, “processor” includes a Data Processor, and “data subject” includes a Data Principal. Where the CCPA applies, “processor” includes a service provider.
3. Our roles
3.1 You are the controller of Customer Personal Data, and we are your processor.
3.2 If you use Zenffy on behalf of your own clients, you are their processor and we are your sub-processor. You confirm that your clients have authorised your instructions to us, including our use of the Sub-processors in Annex III.
3.3 We are the controller of the information we need to run your account and bill you, such as your teammates’ email addresses and your billing details. Our privacy notice at zenffy.com/privacy/ covers that information. This DPA doesn’t.
4. Your instructions
4.1 We process Customer Personal Data only on your documented instructions, unless a law that applies to us requires otherwise. If it does, we tell you before we process, unless that law forbids us to.
4.2 Your instructions are the Agreement, this DPA, and how you set up and use Zenffy. That includes your agent’s settings, knowledge and goal, the retention period you choose, the addresses that receive your leads, your webhook, your account’s storage region, and the tools you connect, such as Google Calendar and WhatsApp. Any other instruction must be in writing and agreed by both of us.
4.3 If we believe an instruction breaks Applicable Data Protection Law, we tell you promptly. We may hold off following it until you confirm or change it.
4.4 You are responsible for your instructions and for having a lawful basis for the processing. In particular, you:
- (a) give Contacts the information, and get any consents, that the law requires. Your website chat links your privacy notice, and an agent can’t go live without one;
- (b) don’t use Zenffy to collect passwords, card numbers or government identity numbers;
- (c) don’t set up your agent to collect special categories of personal data, such as health information, unless you have a lawful basis for it and have checked that the measures in Annex II are right for that data.
5. How we use Customer Personal Data
5.1 We use Customer Personal Data only to provide, secure and support Zenffy for you, as Annex I describes.
5.2 We don’t sell Customer Personal Data. We don’t use it to train AI models, and our AI model provider doesn’t use it to train its models. We don’t use it for advertising or marketing, ours or anyone else’s.
5.3 To bill you, enforce plan limits and run Zenffy, we keep counts that identify no one, such as conversations, messages and AI costs per day. To stop abuse, we also count messages per shortened IP address hash, and per WhatsApp number, for no more than two days.
6. Our people
6.1 Only Zenffy staff who need access to provide, support or secure Zenffy can access Customer Personal Data. They read a conversation only to support you, fix a problem or stop abuse.
6.2 Everyone with that access is bound to keep it confidential.
7. Security
7.1 We keep the technical and organisational measures in Annex II. They protect Customer Personal Data against Security Incidents, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks to Contacts.
7.2 We may update these measures as technology and threats change. We won’t lower the overall protection they give.
8. Sub-processors
8.1 You authorise us to use the Sub-processors listed in Annex III.
8.2 Before a new Sub-processor starts processing Customer Personal Data, we email the owner of your account at least 30 days ahead. Within those 30 days, you may object in writing on reasonable data protection grounds. If we can’t resolve your objection, you may end the affected part of Zenffy before the change takes effect. We then refund any fees you prepaid for the time after it ends.
8.3 If we must replace a Sub-processor urgently to keep Zenffy secure or running, we may give shorter notice. We then tell you as soon as we can, and your right to object still applies.
8.4 Each Sub-processor is bound by a written contract with data protection obligations that protect Customer Personal Data at least as well as this DPA does. We remain responsible to you for how our Sub-processors meet those obligations.
9. Services you connect
9.1 Some parts of Zenffy send Customer Personal Data to services you choose and control. Those services act for you, under your own terms with them. They are not our Sub-processors:
- (a) your Google Calendar, when you connect it. We use it to find free times and create bookings, and Google sends the invitations;
- (b) your webhook endpoint, which receives your leads and bookings, signed with your secret;
- (c) your Google Analytics, Google Tag Manager or Meta Pixel. Your website chat can send them events for a lead and a booking, and Google Analytics also an event for a chat start. These events carry only the goal and an anonymous conversation id, never a name, email address or phone number;
- (d) the email addresses you choose to receive your leads.
9.2 If your WhatsApp number is in your own WhatsApp Business Account, Meta processes your WhatsApp messages under your own terms with Meta. If your number is in Zenffy’s WhatsApp Business Account, Meta is our Sub-processor and is listed in Annex III.
10. Requests from Contacts
10.1 When you ask us by email at hello@zenffy.com, we find, export, correct or delete a Contact’s Customer Personal Data for you within 10 business days.
10.2 If a Contact sends a request to us, we pass it to you. We answer it ourselves only if you ask us to or the law requires it.
10.3 We also give you reasonable help with your other obligations under Applicable Data Protection Law, such as data protection impact assessments and consultations with a supervisory authority. Our help reflects the nature of the processing and the information available to us.
11. Security Incidents
11.1 We notify you without undue delay, and in any case within 48 hours, after we become aware of a Security Incident. We send the notice by email to the owner of your account.
11.2 The notice describes what we know at that point, and we add to it as we learn more:
- (a) what happened;
- (b) the categories, and approximate number, of Contacts and records affected;
- (c) the likely consequences;
- (d) what we have done, or propose to do, to deal with it and limit its harm;
- (e) who to contact for more information.
11.3 We take reasonable steps to contain the Security Incident and limit its harm. Notifying you is not an admission of fault.
11.4 Where the DPDP Act applies, we give you the information you need to inform the Data Protection Board of India and each affected Data Principal.
12. Where data is stored, and transfers
12.1 Storage. If your account uses EU storage, your agents, settings, knowledge, connection details and conversations are stored at rest in the European Union, in Cloudflare’s EU jurisdiction. Otherwise, Cloudflare chooses where your account’s data is stored, which can be in any country where Cloudflare stores data. Your account’s storage region is set when the account is created.
12.2 Processing outside the storage region. Even with EU storage, Customer Personal Data is processed outside the EU:
- (a) Cloudflare handles each request in the data centre that receives it;
- (b) our AI model provider, our email provider and Meta process each request where they run (Annex III);
- (c) our staff, who work in India, can access it to support you.
12.3 Transfers from the EEA. Where the GDPR applies to your transfer of Customer Personal Data to us, the Standard Contractual Clauses form part of this DPA, as follows:
- (a) Module Two (controller to processor) applies where you are a controller, and Module Three (processor to processor) applies where you are a processor;
- (b) you are the data exporter, and we are the data importer;
- (c) Clause 7 (docking clause) applies;
- (d) in Clause 9(a), Option 2 (general written authorisation) applies, with the notice period in section 8.2;
- (e) the optional wording in Clause 11(a) doesn’t apply;
- (f) in Clause 13, the competent supervisory authority is the one Clause 13(a) identifies, as Annex I.C sets out;
- (g) in Clause 17, Option 1 applies, and the Clauses are governed by the law of Ireland;
- (h) in Clause 18(b), the courts of Ireland have jurisdiction;
- (i) Annexes I, II and III of this DPA complete Annexes I, II and III of the Clauses;
- (j) audits under Clauses 8.9(c) and (d) take place as section 14 describes, and the certification of deletion in Clauses 8.5 and 16(d) is given on written request.
12.4 Transfers from the UK. Where the UK GDPR applies to your transfer of Customer Personal Data to us, the UK Addendum forms part of this DPA. Table 1 is completed with the parties’ details in Annex I. Table 2 is completed with the Modules and choices in section 12.3. Table 3 is completed with Annexes I, II and III. In Table 4, neither party may end the UK Addendum under its Section 19.
12.5 Transfers from Switzerland. Where the FADP applies to your transfer of Customer Personal Data to us, the Clauses apply as section 12.3 sets out, with these changes:
- (a) the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for transfers governed by the FADP;
- (b) “Member State” includes Switzerland, so that data subjects in Switzerland can enforce their rights there;
- (c) references to the GDPR include the FADP.
12.6 Our onward transfers. When we transfer Customer Personal Data to a Sub-processor outside the EEA, the UK or Switzerland, we rely on that Sub-processor’s Standard Contractual Clauses, with the UK Addendum and the Swiss changes where needed, or on another transfer mechanism that Applicable Data Protection Law recognises.
12.7 India. Where the DPDP Act applies, we transfer Customer Personal Data outside India only as the DPDP Act allows, including any restriction the Government of India notifies under its section 16.
12.8 Requests from public authorities. If a public authority asks us for Customer Personal Data, we refer it to you where we can. If the law requires us to disclose it, we tell you first, unless the law forbids that, and we disclose only what we must.
13. Deletion and return
13.1 During the Agreement. Conversations, with everything stored with them, are deleted automatically 30, 90 or 365 days after they start. You choose the period for each agent, and the default is 30 days. Deletion runs once a day, so a conversation is deleted within a day after its period ends. Inbound WhatsApp messages also wait in a queue for up to 8 days, so that none is answered twice.
13.2 When your account closes. We delete all Customer Personal Data in your account within 30 days after it closes. Before then, you can ask for a copy at hello@zenffy.com, and we send it in a common machine-readable format, such as JSON. On request, we confirm the deletion in writing.
13.3 Recovery copies. Deleted data can stay in Cloudflare’s automatic recovery copies for up to 30 more days, until those copies expire. We use them only to recover from an incident or an error. If we restore from them, we delete again any data that was due for deletion.
13.4 Longer retention required by law. We keep Customer Personal Data longer only where a law that applies to us requires it, for only as long as it requires, and we keep protecting it under this DPA.
13.5 What stays with you. Lead emails, briefs and webhook events you have received stay with you, under your own policies. Our email provider deletes its copies of those emails under the retention period in Annex III.
14. Information and audits
14.1 We give you the information you reasonably need to show that we meet this DPA. That includes written answers to a reasonable security questionnaire, once a year.
14.2 If that information isn’t enough to meet a requirement of Applicable Data Protection Law or of a supervisory authority, you may audit our compliance with this DPA once a year, yourself or through an independent auditor bound by confidentiality. You give us at least 30 days’ written notice, and you pay your own costs. Audits take place during business hours, follow our reasonable security rules, and never reach other customers’ data. You may audit more often after a Security Incident, or when a supervisory authority requires it.
15. US state privacy laws
15.1 Where the CCPA or a similar US state privacy law applies, we are your service provider or processor. We process Customer Personal Data only for the business purposes in Annex I.
15.2 We don’t sell or share Customer Personal Data, as those laws define “sell” and “share”. We don’t retain, use or disclose it outside our direct business relationship with you, or for any purpose other than those in the Agreement. We don’t combine it with personal information we receive from others, except as those laws allow.
15.3 We comply with those laws and give Customer Personal Data the level of privacy protection they require. If we can no longer meet them, we tell you. You may then take reasonable steps to stop and remedy any unauthorised use.
16. Liability, duration, changes and law
16.1 Each party’s liability under this DPA is subject to the limits in the Agreement. Nothing in this DPA limits a party’s liability to data subjects under the Standard Contractual Clauses, or any liability that the law doesn’t allow to be limited.
16.2 This DPA lasts as long as we process Customer Personal Data for you, including after the Agreement ends, until we have deleted it.
16.3 We may update this DPA to reflect changes in the law, in our Sub-processors (under section 8) or in Zenffy. We tell the owner of your account by email at least 30 days before a material change applies. We won’t make a change that lowers the protection of Customer Personal Data without your agreement.
16.4 This DPA is governed by the law that governs the Agreement, the laws of India, and the courts of Ernakulam, Kerala, have jurisdiction. The Standard Contractual Clauses are governed by the law in section 12.3, and the UK Addendum by the laws of England and Wales.
16.5 For questions about this DPA, email hello@zenffy.com.
Annex I. Description of the processing
A. The parties
- Data exporter: you, the business named in your Zenffy account. Contact: the owner of your account, at the email address on the account. Role: controller, or processor on behalf of your clients. Activities: using Zenffy to answer your Contacts on your website and on WhatsApp.
- Data importer: Zenffy Solutions Private Limited, at the address in section 1.1. Contact: hello@zenffy.com. Role: processor, or sub-processor. Activities: providing Zenffy.
- Signature and date: accepting the Agreement counts as signing this Annex, on the date you accept it.
B. The processing
- Data subjects:
- Contacts: people who talk to your agent, on your website or on WhatsApp;
- people named in your knowledge, settings or connected calendar, such as your staff;
- other people whose details a Contact shares.
- Personal data:
- the messages between Contacts and your agent;
- details a Contact gives, such as their name, email address, phone number, company and answers to your questions, and any call they book;
- on a website: the Contact’s time zone, browser language and approximate country, the page address and any campaign (utm) tags, and a shortened hash of their IP address. Page addresses are kept without their query string, except utm tags;
- on WhatsApp: the Contact’s number and profile name, message ids and delivery status;
- the lead brief the AI writes, which can draw on the public website of the Contact’s company;
- personal data in your website knowledge, agent settings and notes;
- free and busy times on your connected Google Calendar, and the events your agent creates there.
- Sensitive data: Zenffy isn’t designed to collect special categories of personal data. Contacts may still share them in messages, and some uses, such as a clinic’s front desk, can reveal health information. The measures in Annex II apply to all Customer Personal Data. The agent never asks for passwords, card numbers or government identity numbers, and if a Contact starts to share one, it asks them not to.
- Frequency: continuous, while you use Zenffy.
- Nature of the processing: storing data; writing replies and lead briefs with an AI model; finding free times and booking calls on your calendar; emailing leads, bookings and briefs to you; sending the signed webhooks you set up; receiving and sending WhatsApp messages; preventing abuse; deleting data automatically.
- Purpose: to provide Zenffy to you under the Agreement: answering your Contacts from your information, booking calls and sending you leads.
- Retention:
- conversations, with everything stored with them: 30, 90 or 365 days after they start, as you choose. The default is 30 days;
- the inbound WhatsApp queue: up to 8 days;
- daily counts keyed by an IP address hash or a WhatsApp number: two days;
- knowledge and settings: until you change them, or until 30 days after your account closes;
- recovery copies: up to 30 days after any of the above;
- the website chat’s copy in the Contact’s own browser: up to a day.
- Transfers to Sub-processors: as Annex III sets out, for the purposes listed there, and for the retention periods above unless Annex III says otherwise.
C. Competent supervisory authority
The supervisory authority identified under Clause 13(a) of the Clauses:
- if you are established in the EEA, the supervisory authority of the Member State where you are established;
- if you aren’t established in the EEA but have appointed a representative under Article 27 of the GDPR, the supervisory authority of the Member State where your representative is established;
- otherwise, the supervisory authority of the Member State where the Contacts concerned are.
For the UK, the Information Commissioner. For Switzerland, the Federal Data Protection and Information Commissioner.
Annex II. Technical and organisational measures
Encryption
- All connections to Zenffy, and between Zenffy and its Sub-processors, use TLS (HTTPS).
- Cloudflare encrypts all stored data at rest with AES-256.
- Zenffy also encrypts calendar and WhatsApp access tokens, webhook secrets and WhatsApp registration PINs with AES-256-GCM, using a key held as a Cloudflare secret.
Separation between businesses
- Each business account’s agents, settings, knowledge and conversations are kept in that account’s own Cloudflare Durable Object, separate from every other business.
Access control
- Zenffy’s internal admin interface requires a secret key, which it checks in constant time.
- Access to Zenffy’s accounts with Cloudflare and its other providers is limited to the staff who need it, and protected by multi-factor authentication.
- Links that connect a Google Calendar or a WhatsApp number are signed and expire after 7 days.
- Webhooks to you are signed with HMAC-SHA256, using your secret. Zenffy checks Meta’s signature on every WhatsApp webhook before reading it.
Data minimisation
- IP addresses are never stored. Zenffy stores only a shortened hash of each one.
- Page addresses are stored without their query string, except campaign (utm) tags.
- On WhatsApp, the agent reads only text and button taps. Zenffy never downloads voice notes, photos, videos, documents, locations or contacts.
- Analytics events carry only the goal and an anonymous conversation id.
- Zenffy’s logs carry ids, counts and error codes, never message text.
- Alerts to Zenffy staff say what failed for which business, never what a Contact wrote.
Retention
- Conversations are deleted automatically, as section 13 describes.
Abuse prevention
- Cloudflare Turnstile checks each new website chat.
- Rate limits apply per IP address, per WhatsApp number, per agent and per business, with a daily ceiling on each business’s AI costs.
AI safeguards
- The agent always says it is an AI, and never claims to be a person.
- It answers only from your information and about your business.
- It never asks for passwords, card numbers or government identity numbers.
- Nothing a Contact writes changes its rules.
- Under its commercial terms, our AI model provider doesn’t use Customer Personal Data to train its models.
Resilience
- Cloudflare keeps automatic point-in-time recovery copies of stored data for 30 days.
- Failed emails, webhooks and WhatsApp messages are retried automatically.
Development
- Changes to Zenffy are reviewed and pass automated tests before they are deployed.
People and incidents
- Staff access is limited, and bound by confidentiality, as section 6 describes.
- Security Incidents are handled and notified as section 11 describes.
Sub-processors
- Each Sub-processor is bound by data processing terms, as section 8.4 describes.
Annex III. Sub-processors
| Sub-processor | What it does | Customer Personal Data | Where |
|---|---|---|---|
| Cloudflare, Inc. | Hosts Zenffy, stores its data, and runs Turnstile against abuse on the website chat | All Customer Personal Data | Cloudflare’s global network. For accounts with EU storage, stored data stays in the EU |
| Anthropic | The AI model. It reads conversations and your information to write replies and lead briefs | Messages, Contact details, your knowledge and settings, lead brief inputs | United States |
| Postmark (ActiveCampaign, LLC) | Sends lead, booking and brief emails to you | The contents of those emails | United States. It keeps sent emails for 45 days |
| Meta Platforms | Carries WhatsApp messages, when your number is in Zenffy’s WhatsApp Business Account (section 9.2) | WhatsApp messages, numbers and profile names | Meta’s global infrastructure |
These aren’t Sub-processors:
- Google: your own Google Calendar, which you connect and control (section 9.1).
- Paddle and Razorpay: they handle billing for your account. That data is ours as controller, and no Customer Personal Data reaches them.
