Data Processing Addendum
Effective date
October 1, 2026
Contents
Proponent Labs Private Limited. Registered office: 2304, Pinewood, Runwal Greens, MGLR, Bhandup West, Mumbai 400078, Maharashtra, India (CIN: U62011MH2026PTC473867).
Incorporated by reference into the Cloud Services Agreement.
This Data Processing Addendum (“DPA”) forms part of the Cloud Services Agreement & Order Form governing Customer’s use of the Proponent Service (the “Agreement”) between the customer identified there (“Customer”) and Proponent Labs Private Limited, registered office at 2304, Pinewood, Runwal Greens, MGLR, Bhandup West, Mumbai 400078, Maharashtra, India (“Proponent”). It sets out the terms for Proponent’s Processing of Personal Data on Customer’s behalf. Capitalized terms not defined here have the meaning given in the Agreement.
In the event of a conflict between this DPA and the Agreement on data protection matters, this DPA controls. Where Customer accepts the Agreement through a countersigned Order Form, this DPA applies as modified by that Order Form only to the extent the Order Form expressly and specifically so provides.
1. Definitions
- “Data Protection Laws”: India’s Digital Personal Data Protection Act, 2023 (“DPDP Act”) and rules thereunder, the Information Technology Act, 2000 and the rules thereunder (to the extent in force), and, where applicable to a given Customer or Data Principal, the GDPR, UK GDPR, Swiss FADP, CCPA/CPRA, and other U.S. state privacy laws.
- “Personal Data,” “Processing,” and “Data Principal” take the meanings given under the DPDP Act; where GDPR or CCPA apply, “Controller/Processor/Data Subject” or “Business/Service Provider/Consumer” take the meanings given under those laws.
- “Customer Personal Data”: Personal Data within Customer Data that Proponent Processes on Customer’s behalf, including within Conversation Data and CRM Data.
- “Subprocessor”: a third party Proponent engages to Process Customer Personal Data to provide the Service.
- “Personal Data Breach”: a breach of security leading to unauthorized Processing, disclosure, alteration, destruction, or loss of access to Customer Personal Data.
- “Other Parties to the Call” means any individual who participates in a conversation captured or processed by the Service, other than Customer’s own Authorized Users, for example, a prospect, customer, or other external participant on a sales call.
2. Roles of the Parties
Customer is the Data Fiduciary (or Controller/Business); Proponent is the Data Processor (or Processor/Service Provider), Processing Customer Personal Data only on Customer’s behalf and not for its own independent purposes, except as Data Protection Laws require.
This DPA applies only to Customer Personal Data as defined above. It does not cover Proponent’s processing of Customer’s own account, billing, and support-communication data (for example, the name, email, and billing details of the individuals who administer Customer’s account), which Proponent processes as Data Fiduciary in its own right, for its own business purposes, and which is instead governed by the Proponent Privacy Policy.
3. Scope & Instructions
Proponent will Process Customer Personal Data only (a) to provide, secure, and maintain the Service for Customer (and, solely using aggregated data that does not identify Customer, its Authorized Users or any Data Principal, to improve the Service), (b) as documented in the Agreement and Annex 1, and (c) per Customer’s other documented instructions, unless otherwise required by law applicable to Proponent, in which case Proponent will inform Customer first, unless legally prohibited from doing so. Proponent will promptly inform Customer if, in its opinion, an instruction infringes Data Protection Laws.
4. Customer-Directed Integrations & AI Use
4.1 Customer-directed integrations
Where Customer or its Authorized Users connect a third-party tool to the Service, including a CRM, recorder, dialer, or an AI assistant through an AI Assistant Integration, any transmission of Customer Personal Data to that tool is made on Customer’s documented instructions under Section 3(c). The provider of that tool Processes such data under Customer’s own agreement with it, is not a Subprocessor, and its Processing is outside Proponent’s obligations under this DPA. For AI Assistant Integrations, Customer is responsible for using a plan with the relevant provider that excludes training on inputs, and may disable the integration at any time.
4.2 No model training
Proponent will not use Customer Data (including Customer Personal Data, Conversation Data, CRM Data and any outputs or derivatives thereof) to train, fine-tune or otherwise improve any artificial intelligence or machine-learning model, whether its own or a third party’s, other than configurations used solely to provide the Service to Customer, and will contractually prohibit each Subprocessor from using Customer Data to train or improve its models, and will use only Subprocessor plans or API tiers that exclude such use. This restriction applies only to Customer Data and any outputs or derivatives of it, and does not limit Proponent’s ability to develop, train, or improve its models using data obtained independently of Customer, including publicly available information or data from other customers in compliance with Proponent’s agreements with them, provided that no Customer Data is used for such purposes.
5. Consent & Notice Under the DPDP Act
Where Customer is itself obtaining consent from Data Principals (e.g. sales reps, call participants) under the DPDP Act, Customer is responsible for ensuring that consent is free, specific, informed, unconditional, and unambiguous, and that the required notice under Section 5 of the DPDP Act is given. Proponent provides reasonable supporting functionality but does not assume Customer’s obligations as Data Fiduciary.
6. Consent for Conversation Recording
Customer is solely responsible for establishing a lawful basis and obtaining any consents required by applicable law, including the DPDP Act, the Information Technology Act, 2000, and, where Other Parties to the Call are located elsewhere, laws requiring consent of all parties to a call, before any conversation is recorded, transcribed, or Processed through the Service, and for giving any required notice to both Customer’s Authorized Users and any Other Parties to the Call. This does not limit Customer’s indemnification obligations under the Agreement.
7. Prohibited Data
Customer will not submit, and will ensure the Service is not used to process, any of the following unless the parties have first entered into a separate written agreement specifically addressing that data category: (a) health-related information that would constitute sensitive personal data or information under the Information Technology Act, 2000 and related Rules, or mental-health records subject to the confidentiality protections of the Mental Healthcare Act, 2017; (b) personal data of a child or a person with a disability who has a lawful guardian, in a manner that would trigger the consent and processing restrictions under Section 9 of the DPDP Act; (c) bank account, credit card, debit card, or other payment instrument details, or other payment system data subject to the Reserve Bank of India’s data-localisation requirements; or (d) data subject to an equivalent sensitive or specially regulated data classification under any other Data Protection Law applicable to Customer or its Data Principals. Proponent has not designed the Service’s security or contractual safeguards around these data categories, and Customer’s submission of such data in breach of this Section is at Customer’s own risk and subject to the indemnification obligations in the Agreement.
This Section does not apply to information incidentally disclosed by a participant in the ordinary course of a conversation, which Customer will take reasonable steps to minimise.
8. CCPA Terms (where applicable)
Where the CCPA/CPRA applies to Customer Personal Data, Proponent acts as Customer’s ‘service provider’ under that law: Proponent will not sell or share Customer Personal Data; will use it only for the purposes set out in Section 3; will not combine it with personal data from other sources except as the CCPA/CPRA permits; will notify Customer if it can no longer meet its obligations under that law; and will impose the same restrictions on any Subprocessor. Customer may verify compliance with this Section through the audit rights in Section 14.
9. Security Measures
Proponent implements reasonable security safeguards under Section 8(5) of the DPDP Act and appropriate technical/organizational measures generally (Annex 2), including encryption in transit and at rest, access controls, and monitoring proportionate to risk. Where Customer selects self-hosting, responsibilities are as agreed in writing between the parties, and this Section applies only to components Proponent continues to operate. Proponent will not materially diminish the measures in Annex 2 during the term of the Agreement, and will provide a completed security questionnaire on reasonable request.
10. Personnel
Proponent ensures personnel authorized to Process Customer Personal Data are bound by confidentiality and receive appropriate training.
11. Subprocessors
Customer authorizes the Subprocessors listed at Annex 3 and generally authorizes future Subprocessors, provided Proponent: (a) gives at least 10 business days’ notice before a new Subprocessor begins Processing; (b) imposes data-protection obligations no less protective than those in this DPA on it; and (c) remains liable for its performance. Customer may object on reasonable data-protection grounds within the notice period, and Proponent will not permit the new Subprocessor to Process Customer Personal Data while an objection is pending; if unresolved after 30 days, Customer may terminate the affected Service on written notice, and Proponent will refund, within thirty (30) days, all prepaid fees for unused Credits. Integrations selected by Customer under Section 4 are not Subprocessors.
12. Assistance with Data Principal Requests
Proponent will reasonably assist Customer in responding to individuals exercising rights under Data Protection Laws (access, correction, erasure, and the DPDP Act’s grievance-redressal framework). If Proponent receives such a request directly, it will forward the request to Customer and refer the individual to Customer rather than directly responding, unless legally required to respond.
13. Personal Data Breach Notification
Proponent will notify Customer without undue delay, and in no event later than seventy two (72) hours after becoming aware of a Personal Data Breach affecting Customer Personal Data, describing (to the extent known) its nature, affected categories/volume of data, and remediation steps, and will reasonably cooperate with Customer’s own notification obligations, including to the Data Protection Board of India where required. Notification is not an acknowledgment of fault.
14. Audits
On reasonable notice, no more than once per 12 months (except after a Personal Data Breach or regulatory requirement), Proponent will provide information reasonably necessary to demonstrate compliance. Where such information is not reasonably sufficient to demonstrate compliance, or where required by a regulator, Proponent will permit Customer or an independent, confidentiality-bound auditor appointed by Customer (not being a competitor of Proponent) to conduct a limited-scope audit at Customer’s expense, on 30 days’ notice.
15. Cross-Border Data Transfers
Proponent may Process Customer Personal Data outside India, consistent with the DPDP Act’s transfer framework (permitted except to countries the Central Government specifically restricts).
Where Customer Personal Data is transferred outside India to a jurisdiction whose data protection law imposes its own requirements on such a transfer (including the EU, UK, or Switzerland), the parties will, before that transfer takes place, agree and incorporate the additional safeguards required under that jurisdiction’s law (for example, Standard Contractual Clauses, a UK International Data Transfer Addendum, or another lawful transfer mechanism) by way of a country-specific addendum to this DPA.
16. Deletion & Return
On termination, Proponent makes Customer Personal Data available for export for 30 days, then deletes it from active systems within 30 days, except where law requires continued (isolated, protected) retention. On request, the Proponent will certify such deletion in writing.
17. Liability & Governing Law
Liability under this DPA is subject to the limitation of liability in the Agreement.
This DPA is governed by the laws of India. Disputes will be referred to arbitration administered by the Mumbai Centre for International Arbitration (MCIA) under the Arbitration and Conciliation Act, 1996 & its Rules, before a sole arbitrator appointed in accordance with those Rules. The seat of arbitration shall be Mumbai, India; the language shall be English. The courts at Mumbai shall have exclusive jurisdiction to grant interim relief in aid of arbitration.
18. Term
This DPA remains in effect for as long as Proponent Processes Customer Personal Data under the Agreement. Sections 13, 16 and 17 survive termination of the Agreement.
Annex 1: Details of Processing
| Field | Detail |
|---|---|
| Subject matter | Provision of the Proponent customer-intelligence Service. |
| Duration | Term of the Agreement, plus the deletion window in Section 16. |
| Nature & purpose | Capture, transcription, analysis and scoring of business conversations (including sales and employee-engagement conversations), and synchronisation with Customer’s CRM; delivery of insights, including via AI Assistant Integrations where enabled. |
| Categories of Data Principals | Customer’s Authorized Users, employees and contractors; and prospects, customers, candidates, employees of Customer’s clients, and other individuals who participate in conversations Customer submits. |
| Categories of Personal Data | Names, contact details, voice recordings and transcripts, business-conversation content (which may incidentally include sensitive personal data if disclosed on a call; Customer should avoid directing sensitive data to the Service where not necessary). |
| Processing operations | Collection, storage, transcription, analysis, scoring, transmission to Customer’s CRM, and transmission, at Customer’s direction, to integrations Customer connects, including AI Assistant Integrations (see Section 4). |
Subject matter
- Detail
- Provision of the Proponent customer-intelligence Service.
Duration
- Detail
- Term of the Agreement, plus the deletion window in Section 16.
Nature & purpose
- Detail
- Capture, transcription, analysis and scoring of business conversations (including sales and employee-engagement conversations), and synchronisation with Customer’s CRM; delivery of insights, including via AI Assistant Integrations where enabled.
Categories of Data Principals
- Detail
- Customer’s Authorized Users, employees and contractors; and prospects, customers, candidates, employees of Customer’s clients, and other individuals who participate in conversations Customer submits.
Categories of Personal Data
- Detail
- Names, contact details, voice recordings and transcripts, business-conversation content (which may incidentally include sensitive personal data if disclosed on a call; Customer should avoid directing sensitive data to the Service where not necessary).
Processing operations
- Detail
- Collection, storage, transcription, analysis, scoring, transmission to Customer’s CRM, and transmission, at Customer’s direction, to integrations Customer connects, including AI Assistant Integrations (see Section 4).
Annex 2: Technical & Organizational Security Measures
- Encryption of Customer Personal Data in transit (TLS) and at rest
- Role-based access controls; least-privilege access to production systems
- Logging and monitoring of access to production systems
- Vendor/subprocessor security review before onboarding
- Incident response process per Section 13
- Self-hosting available for customers requiring full data residency and infrastructure control
Annex 3: Subprocessors
The current List of Subprocessors is as below:
Infrastructure subprocessors
| Subprocessor | Purpose | Customer data processed | Location |
|---|---|---|---|
| Supabase, Inc. | Primary database and user sign-in (hosted on AWS) | All Service data: user accounts, meeting and call records, transcripts, AI outputs, synced CRM records | India (Mumbai, AWS ap-south-1) |
| Amazon Web Services, Inc. | Encrypted file storage | Call audio, meeting transcripts, uploaded files | USA (N. Virginia, us-east-1) |
| DigitalOcean, LLC | Application servers: API, background jobs, AI processing pipeline | All Service data, in transit and while being processed | India (Bengaluru, BLR1) |
| Redis Ltd. | In-memory cache | Cached CRM contact, company and deal records | USA (N. Virginia, AWS us-east-1) |
| Vercel Inc. | Hosting of the Proponent web application | Data displayed in the application | India (Mumbai, bom1), with global edge network |
Supabase, Inc.
- Purpose
- Primary database and user sign-in (hosted on AWS)
- Customer data processed
- All Service data: user accounts, meeting and call records, transcripts, AI outputs, synced CRM records
- Location
- India (Mumbai, AWS ap-south-1)
Amazon Web Services, Inc.
- Purpose
- Encrypted file storage
- Customer data processed
- Call audio, meeting transcripts, uploaded files
- Location
- USA (N. Virginia, us-east-1)
DigitalOcean, LLC
- Purpose
- Application servers: API, background jobs, AI processing pipeline
- Customer data processed
- All Service data, in transit and while being processed
- Location
- India (Bengaluru, BLR1)
Redis Ltd.
- Purpose
- In-memory cache
- Customer data processed
- Cached CRM contact, company and deal records
- Location
- USA (N. Virginia, AWS us-east-1)
Vercel Inc.
- Purpose
- Hosting of the Proponent web application
- Customer data processed
- Data displayed in the application
- Location
- India (Mumbai, bom1), with global edge network
Service subprocessors
| Subprocessor | Purpose | Customer data processed | Location |
|---|---|---|---|
| Google LLC | Gemini API: AI analysis of conversations, transcription of call audio, text embeddings | Transcripts, call audio, participant names, related CRM context. Proponent uses Google’s paid Gemini Developer API under the Gemini API Additional Terms of Service (paid services). Under those terms, Google does not use prompts or responses to train or improve its models. Google may retain prompts and responses for up to 55 days solely for abuse monitoring; audio sent for transcription is deleted once processed. The Gemini Developer API does not offer region pinning, so processing takes place in the USA and other countries where Google and its subprocessors operate, under Google’s data processing terms including the Standard Contractual Clauses. | USA and other countries where Google operates (Gemini Developer API; no region pinning) |
| Knock Labs, Inc. | Notification workflows (meeting summaries, alerts) | Recipient names and emails, meeting titles, AI summaries | USA |
| Functional Software, Inc. (Sentry) | Error monitoring, and session replay with all text and media masked | Error logs, request metadata | USA (US data region) |
| PostHog, Inc. | Product usage analytics | Pseudonymous user identifiers, page views, in-app events | USA (US Cloud) |
| Stripe, Inc. | Subscription payments (only applicable where Customer is billed via card) | Billing contact name, email, payment details | USA |
| Razorpay Software Private Limited | Payment processing (only applicable where Customer is billed via card) | Billing contact name, email, payment details | India |
| Slack Technologies, LLC | Internal operational alerts to Proponent’s engineering team | Error and job-failure metadata | USA |
| OpenAI, L.L.C. | AI analysis of conversations | Transcripts, participant names, related CRM context | USA |
| Eleven Labs Inc. (ElevenLabs) | Transcription of call and meeting audio | Call and meeting audio, transcripts | USA |
| Recall.ai, Inc. | Meeting recorder bot and calendar sync | Meeting audio and video, transcripts, participant names and emails, calendar events | Japan (Tokyo) |
Google LLC
- Purpose
- Gemini API: AI analysis of conversations, transcription of call audio, text embeddings
- Customer data processed
- Transcripts, call audio, participant names, related CRM context. Proponent uses Google’s paid Gemini Developer API under the Gemini API Additional Terms of Service (paid services). Under those terms, Google does not use prompts or responses to train or improve its models. Google may retain prompts and responses for up to 55 days solely for abuse monitoring; audio sent for transcription is deleted once processed. The Gemini Developer API does not offer region pinning, so processing takes place in the USA and other countries where Google and its subprocessors operate, under Google’s data processing terms including the Standard Contractual Clauses.
- Location
- USA and other countries where Google operates (Gemini Developer API; no region pinning)
Knock Labs, Inc.
- Purpose
- Notification workflows (meeting summaries, alerts)
- Customer data processed
- Recipient names and emails, meeting titles, AI summaries
- Location
- USA
Functional Software, Inc. (Sentry)
- Purpose
- Error monitoring, and session replay with all text and media masked
- Customer data processed
- Error logs, request metadata
- Location
- USA (US data region)
PostHog, Inc.
- Purpose
- Product usage analytics
- Customer data processed
- Pseudonymous user identifiers, page views, in-app events
- Location
- USA (US Cloud)
Stripe, Inc.
- Purpose
- Subscription payments (only applicable where Customer is billed via card)
- Customer data processed
- Billing contact name, email, payment details
- Location
- USA
Razorpay Software Private Limited
- Purpose
- Payment processing (only applicable where Customer is billed via card)
- Customer data processed
- Billing contact name, email, payment details
- Location
- India
Slack Technologies, LLC
- Purpose
- Internal operational alerts to Proponent’s engineering team
- Customer data processed
- Error and job-failure metadata
- Location
- USA
OpenAI, L.L.C.
- Purpose
- AI analysis of conversations
- Customer data processed
- Transcripts, participant names, related CRM context
- Location
- USA
Eleven Labs Inc. (ElevenLabs)
- Purpose
- Transcription of call and meeting audio
- Customer data processed
- Call and meeting audio, transcripts
- Location
- USA
Recall.ai, Inc.
- Purpose
- Meeting recorder bot and calendar sync
- Customer data processed
- Meeting audio and video, transcripts, participant names and emails, calendar events
- Location
- Japan (Tokyo)