Data Processing Addendum
Effective from: 8th October 2026 Last updated: 8th October 2026
This Addendum forms part of the Terms of Service between Kevit Technologies Private Limited (“KTPL”, “Processor”) and the Customer (“you”, “Data Fiduciary”).
It is entered into by your acceptance of the Terms of Service. No signature is required and none will be provided. It satisfies the written-contract requirement of Section 8(2) of the Digital Personal Data Protection Act, 2023.
Where this Addendum conflicts with the Terms of Service on the subject of personal data, this Addendum prevails.
1. Definitions
Terms not defined here have the meaning given in the DPDP Act, 2023 and the DPDP Rules, 2025.
| Term | Meaning |
|---|---|
| Customer Data | Personal data about your End Users that we process on your behalf through Vezly. |
| End User | An individual who messages your WhatsApp or Instagram channel, or whose details you upload or import. |
| Data Principal | The individual to whom personal data relates. |
| Sub-processor | A third party we engage to process Customer Data on our behalf. |
| Personal Data Breach | Unauthorised processing, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to Customer Data, that compromises its confidentiality, integrity or availability. |
2. Roles
You are the Data Fiduciary. You determine the purpose and means of processing Customer Data. You are responsible for its lawfulness.
We are the Data Processor. We process Customer Data solely on your behalf and on your instructions.
Neither of us is a joint fiduciary with the other.
We are the Data Fiduciary in our own right for your account, billing and usage data. That is not Customer Data and this Addendum does not apply to it. It is governed by the Privacy Policy.
3. Scope of processing
3.1 Subject matter
Provision of the Vezly messaging and automation platform over WhatsApp and Instagram.
3.2 Duration
For the term of your account, plus the retention periods in section 9.
3.3 Nature and purpose
Receiving, storing, routing, transmitting, organising, segmenting, retrieving and deleting Customer Data as required to operate the service you have configured.
3.4 Categories of Data Principal
Individuals who message your channels; individuals whose contact details you upload or import; individuals who comment on or mention your Instagram account.
3.5 Categories of Customer Data
- Identifiers: phone number, WhatsApp ID, Instagram-scoped user ID, username, profile name, profile picture URL
- Message content: text, images, video, audio, documents, stickers, voice notes, location, shared contacts
- Instagram content: direct messages, comments, mentions, story replies, story mentions, reactions
- Interaction data: button and list responses, flow submissions
- Metadata: message IDs, timestamps, delivery and read status, conversation category, template IDs, referral data, error callbacks
- Customer-supplied data: uploaded or imported contact records and every field in them, tags, custom attributes, segment membership, agent notes
- Consent data: opt-in and opt-out records with timestamp, channel and source
- Generated data: conversation state, campaign records, assignment history, AI reply suggestions and summaries
3.6 Special categories
Vezly is not designed for sensitive personal or financial information. Do not configure flows that collect payment card details, bank account numbers, government identification numbers, passwords, OTPs, health information or biometric data. If you do so anyway, you do it at your own risk and the indemnity in section 13 applies.
4. Your instructions
We process Customer Data only on your documented instructions. Your instructions are:
- These Terms and this Addendum
- Your configuration of the account - flows, campaigns, integrations, retention settings, feature toggles
- Calls you make to our APIs
- Written instructions you give us through support, where we agree to act on them
We will not:
- Process Customer Data for our own purposes
- Sell, rent or disclose Customer Data to any third party except the Sub-processors in section 6
- Use Customer Data or End User message content for product analytics, marketing or profiling
- Use Customer Data to train, fine-tune or evaluate any machine learning model, ours or anyone else’s
We will tell you if we believe an instruction breaches the DPDP Act, and may decline to act on it.
Where we are compelled by law to process Customer Data beyond your instructions, we will tell you first unless prohibited from doing so.
5. Your obligations as Data Fiduciary
You warrant and undertake that:
- You have a valid lawful basis under the DPDP Act for all Customer Data you process through Vezly
- You have given each Data Principal a notice meeting Section 5 of the Act and Rule 3 of the Rules - itemised, standalone, in plain language, with working means to withdraw consent, exercise rights and complain to the Data Protection Board
- You hold, and can produce, evidence of opt-in for every recipient of a promotional or marketing message
- You will honour consent withdrawal and opt-out promptly, and will not continue messaging a Data Principal who has opted out
- You will not upload, import or message any contact for whom you cannot satisfy points 1 to 3
- You will respond to Data Principal rights requests yourself, as the Data Fiduciary
- You will publish your own contact point for data protection questions and grievances
- You comply with Section 9 of the Act in respect of any Data Principal under 18, and with the children’s restrictions in the Acceptable Use Policy
- You comply with Meta’s terms and policies, including the WhatsApp Business Messaging Policy
Vezly provides opt-in and opt-out capture and records. Those are tools. Using them is not the same as having a lawful basis. The obligation is yours.
6. Sub-processors
You give general authorisation for us to engage Sub-processors. The current list is published at /sub-processors and is incorporated here.
6.1 Current Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services India Private Limited | Hosting, storage, backup, CDN | India (ap-south-1) |
| Meta Platforms | WhatsApp and Instagram connectivity | Per Meta; WABA storage location controlled by your Business Manager |
| Zoho Corporation Private Limited | Support ticketing | India |
| Google LLC | AI reply suggestions and summaries | Outside India |
| OpenAI, L.L.C. | AI reply suggestions and summaries | Outside India |
| Anthropic PBC | AI reply suggestions and summaries | Outside India |
Cashfree Payments, Amazon SES and PostHog process your account data, not Customer Data, and are listed in the Privacy Policy rather than here.
6.2 AI provider routing
Google, OpenAI and Anthropic are each authorised for the AI features. We may route any given request to any of them, and may change the default, at our discretion and without notice to you. This is a term of your authorisation. If you do not accept it, disable the AI features in account settings - no Customer Data is then sent to any of them.
6.3 New Sub-processors
We will update the Sub-processor page. If you object, your remedy is to terminate the account before the change takes effect. No refund arises.
6.4 Our responsibility
We impose data protection obligations on each Sub-processor no less protective than those in this Addendum, and we remain responsible to you for their performance.
7. Cross-border transfers
Customer Data is stored in India (AWS ap-south-1).
Customer Data is transferred outside India in one circumstance only: when you use the AI reply suggestion or conversation summary features, message content is transmitted to Google, OpenAI or Anthropic for processing. These features are on by default and can be disabled account-wide at any time.
The DPDP Act permits such transfers except to territories restricted by Central Government notification. No applicable restriction is currently in force. If one is issued we will change our arrangements, which may mean disabling the affected feature.
Messages sent and received through WhatsApp and Instagram also traverse Meta’s infrastructure. Meta’s storage location for your WABA is a setting in your Meta Business Manager, which you control. We make no representation about where Meta stores data.
8. Security
We maintain the safeguards described in section 10 of the Privacy Policy, including encryption at rest and in transit, multi-factor authentication, just-in-time privileged access, least-privilege role assignment with quarterly review, centralised logging and alerting, annual independent penetration testing, and mandatory personnel training.
Personnel with access to Customer Data are bound by written confidentiality obligations that survive their engagement.
We may update our safeguards, provided the overall level of protection is not reduced.
9. Retention and deletion
| Category | Retention |
|---|---|
| Message content, media, contact records, campaign records | 3 months live, 3 months cold archive, permanent deletion at 6 months |
| Opt-in and opt-out records | Life of account plus 3 years |
| Platform audit logs | Indefinite |
| Backups | Daily ×2, monthly ×2 - up to 60 days residual after live deletion |
Cold archive (months 4 to 6) is not accessible in the application. Request retrieval through support; delivery takes up to 5 working days.
Running out of credit does not trigger deletion. Vezly is prepaid; if the wallet reaches zero, sending stops but the account remains open and Customer Data continues to age out on the schedule above.
On termination: access ends, you may request an export within 30 days, and all Customer Data is permanently deleted from live systems thereafter, subject to the 60-day backup residue.
Deletion on instruction. You may delete individual contacts, conversations or your whole dataset from the application at any time. Deletion is effective in live systems immediately and in backups within 60 days.
We will not retain Customer Data beyond these periods unless required by law.
10. Data Principal rights
Rights requests belong to you. Data Principals must exercise them against you, not against us.
Where we receive a request directly, we will not respond substantively. We will tell the individual to contact you, and where we can identify you from the request, we will forward it.
We assist you by providing, through the application: search and retrieval of an individual’s conversation history and contact record; export; deletion; and opt-out records. Where the application cannot serve a request, contact support@vezly.io and we will give reasonable assistance at no charge, provided the volume of requests is reasonable.
11. Personal Data Breach
We will notify you within 48 hours of becoming aware of a Personal Data Breach affecting your Customer Data, by email to your account owner and security contact.
The notification will include, so far as known at that time: the nature of the breach, the categories and approximate number of Data Principals and records affected, the likely consequences, the measures taken or proposed, and a contact point for further information. We will update you as the investigation progresses.
Your obligations are yours. As Data Fiduciary, notifying the Data Protection Board of India and affected Data Principals under Section 8(6) of the Act and Rule 7 of the Rules is your responsibility, on the timelines the Rules prescribe. Our notification is what enables you to do so. We will give reasonable assistance with your notification, including relevant logs.
We will not notify Data Principals on your behalf unless you instruct us to and we agree in writing.
12. Audit
You have no audit right. There is no right to inspect our systems, environments, facilities, personnel or records under this Addendum, at any spend level.
We hold ISO/IEC 27001 certification and a SOC 2 Type II attestation covering Security and Confidentiality.
Where your spend exceeds ₹1,00,000 per month, you may request our SOC 2 Type II report under NDA, and a written response to a reasonable security questionnaire within 30 days. Whether to provide either is our sole decision.
This section is the whole of your assurance entitlement.
13. Liability and indemnity
The limitation of liability in section 12 of the Terms of Service applies to this Addendum.
You will indemnify us against any claim, penalty, fine, order or cost, including reasonable legal costs, arising from:
- Your breach of section 5
- Any allegation that a message sent through your account lacked valid consent or was unsolicited
- Your processing of a child’s data without verifiable parental consent, or in breach of Section 9(3) of the Act
- Your collection of sensitive or financial data contrary to section 3.6
- Any Data Principal complaint or Data Protection Board proceeding arising from your processing
14. Term
This Addendum takes effect when you accept the Terms of Service and continues until all Customer Data has been deleted in accordance with section 9.
Sections 9, 10, 11, 12 and 13 survive termination.
15. Changes
We may update this Addendum. Material changes will be notified to account owners by email and posted here at least 30 days before taking effect.
16. Contact
Data protection: dpo@vezly.io Security incidents: security@vezly.io Grievance Officer: Dhruman Bhadeshiya - grievance@vezly.io