Draft for legal review. Not yet in force, and not indexed by search engines.
LegalData processing agreement
Last updated 20 November 2026
How TalkDemo processes personal data on your behalf.
This data processing agreement (“DPA”) forms part of the terms of service between [TODO: contracting entity, e.g. PitchWitch Ventures LLC or the Indian operating company], [TODO: registered office address] (“TalkDemo”) and the company that uses TalkDemo to run demos of its product (the “Customer”). It applies whenever TalkDemo processes personal data on the Customer's behalf. It is written for India's Digital Personal Data Protection Act, 2023 and the Rules made under it (“DPDP Act”), the EU GDPR, and the UK GDPR with the Data Protection Act 2018.
The short version
- You decide why your prospects' data is processed. TalkDemo processes it only to run your demo agents, on your instructions.
- TalkDemo keeps it confidential and secure, uses only the listed sub-processors, and tells you before adding one.
- Demo credentials are sealed and never sent to the AI model, and customer data is never used to train AI models.
- TalkDemo helps you answer rights requests, tells you about a breach within 72 hours at the latest, and deletes your data when the service ends.
TalkDemo is pre-launch. Where this DPA describes a control, it is the control the product is designed and built to have; the security page marks which controls are planned. [TODO: legal review. Decide whether this DPA is accepted with the terms at sign-up, signed separately, or both, and attach the EU standard contractual clauses and the UK transfer agreement for customers that need them.]
01Roles
- The Customer is the data fiduciary under the DPDP Act and the controller under the GDPR and UK GDPR for the personal data of its prospects. It decides where its agents are offered, what they ask, whether calls are recorded, how long data is kept, which integrations receive it and who on its team sees it.
- TalkDemo is the Customer's data processor and processor for that data.
- TalkDemo is a data fiduciary and controller in its own right only for customer team accounts, billing, its staff, website visitors, enquiries and the waitlist, as its privacy policy explains.
The Customer is responsible for having a lawful basis for the processing, for its own privacy notice to prospects, and for the instructions it gives TalkDemo. TalkDemo shows the notice and records prospects' consents on the call page, but that does not move the Customer's duties to TalkDemo.
02Subject matter, duration, nature and purpose
Item Details Subject matter Providing the TalkDemo service to the Customer: AI demo agents reached through demo links and the website widget, the customer dashboard, and integrations the Customer connects Duration For as long as the Customer uses TalkDemo, then until the data is returned and deleted as set out below Nature Real-time speech recognition and speech generation, AI conversation, display of the Customer's demo tenant or slides, recording, transcription, summarising, lead scoring, storage, display to authorised users, sync to the Customer's CRM and calendar, recap messages the prospect agreed to, export and deletion Purpose Giving prospects a live demo of the Customer's product, answering their questions, qualifying them and booking meetings, plus the support, security and audit records needed to provide the service Not done Selling data, advertising, sharing prospects between customers, training AI models, voiceprints or emotion detection, using the prospect's camera, or recording the prospect's screen 03People and data covered
Categories of people:
- Prospects who start a demo with one of the Customer's agents.
- The Customer's own team members who use the dashboard or join a call to take over from the agent.
- People named in knowledge sources the Customer uploads, if any.
Categories of data:
- Voice audio during the call, and text the prospect types.
- Transcripts with timestamps, and summaries.
- Recordings of the call, with the prospect's consent where the Customer asks for it. The video is the agent's shared screen showing the Customer's demo tenant, not the prospect.
- Name, company and role.
- Email address and phone number, sealed with a keyed hash for de-duplication.
- Answers to qualification questions, lead scores and meeting bookings.
- A hash of the IP address (never the raw address) and the country.
- Consent events (recording, marketing email) with the notice version and time.
Sensitive data: the service is not designed for special category or sensitive personal data, and agents don't ask for it. The Customer must not configure qualification questions that ask for it.
04TalkDemo's obligations
- Process personal data only on the Customer's documented instructions, which are this DPA, the terms and the Customer's settings in the product. TalkDemo tells the Customer if it believes an instruction breaks data protection law.
- Make sure everyone at TalkDemo who can access the data is bound by confidentiality, and give staff access only when their role needs it.
- Open a Customer's workspace for support only when one of its Admins grants time-limited, read-only access, and record every page viewed.
- Keep each Customer's data separate from every other customer's, and never use one customer's data for another.
- Apply the security measures in the annex below.
- Help the Customer with data protection impact assessments and prior consultations, where they concern the service.
- Keep records of processing carried out for the Customer.
05Annex: security measures
TalkDemo is designed and built with the following measures, mapped to ISO/IEC 27001 Annex A and SOC 2 in an internal register. The security page lists every control and marks each as planned until it is in place and tested. Nothing here is audited or certified.
- Each customer's data separated in the database itself with composite tenant keys, so a bug in a screen can't link records across customers.
- Live product mode only against a demo tenant, with one isolated cloud browser per session that is destroyed when the call ends.
- A URL allowlist, blocked actions and an optional read-only mode, checked by the browser service before every action.
- Demo credentials sealed with AES-256-GCM and opened only by the browser service, never sent to the AI model, logged or returned by an API.
- Prospect contact details and integration tokens sealed at the column level; IP addresses stored only as hashes.
- Encryption in transit (TLS) everywhere and encryption at rest for the database and file storage; malware scanning of uploads.
- Two-factor sign-in required for TalkDemo staff, least-privilege staff roles, and support access only with the Customer's time-limited, read-only grant.
- An audit trail of every agent action, tool call and model step, linked to the recording, in a separate logs database without passwords, tokens or full contact details.
- Bot checks and rate limits on public forms, an allowed-origins check on the widget, and signature checks on webhooks.
- Encrypted backups, secrets kept outside the code, and a written incident response process.
TalkDemo may improve these measures over time but will not reduce the overall level of protection.
06Sub-processors
The Customer authorises the sub-processors listed below and on the sub-processors page. TalkDemo binds each one to data protection terms no less protective than this DPA and remains responsible for their work. Some are used only when the Customer turns on the feature that needs them.
Provider What it does Where Vercel Hosting for the website, dashboard and call page Global edge; functions in Mumbai (bom1) for India Managed PostgreSQL (AWS RDS or Supabase, Mumbai region) Database for account data and, separately, the logs India (ap-south-1) Amazon Web Services Private file storage, malware scanning and email India (ap-south-1) LiveKit Real-time calls: audio, screen share and recording Region pinned to the prospect (Mumbai for India) Sarvam AI Speech-to-text and text-to-speech for Indian languages, Hinglish and English (India) India Anthropic (Claude) The agent's conversation and reasoning, summaries and lead scoring United States; zero-retention settings where offered Browserbase Isolated cloud browsers for live product demos (agents in live product mode) Nearest available region; Singapore for Indian sessions (no India region yet). It renders your demo tenant, not prospect data Deepgram Speech-to-text for English (US, UK and Australia) and world languages (only for calls in those languages, never for Indian languages) United States ElevenLabs Text-to-speech for English (US, UK and Australia) and world languages (only for calls in those languages, never for Indian languages) United States Cartesia Backup text-to-speech for world languages (only for world-language calls, if ElevenLabs is unavailable) United States OpenAI Embeddings for knowledge search (text-embedding-3-small), and backup text-to-speech for world languages United States Cloudflare DNS and Turnstile bot checks on public forms Global network Razorpay Payments in rupees (UPI AutoPay, cards, GST invoices) (customers paying in rupees) India Stripe Card payments in US dollars, with receipts and invoices (customers paying in US dollars) United States cron-job.org Runs scheduled jobs and uptime checks Germany Sentry, PostHog and Langfuse Error tracking, product analytics and AI traces EU or US (set at launch) Before adding or replacing a sub-processor that will process the Customer's personal data, TalkDemo updates that page and emails the Customer's Admins [TODO: notice period, for example 30 days] in advance. If the Customer objects on reasonable data protection grounds, the parties will discuss it in good faith. If they can't agree, the Customer may end the affected service and receive a refund of fees prepaid for the period after it ends.
07AI processing
- The AI model receives the conversation, relevant passages from the Customer's knowledge sources and summaries of the screen, only for the demo in progress and the summary after it.
- Demo credentials are never sent to the model. Another customer's data is never included.
- AI providers are used under terms that don't train on submitted content, with zero-retention settings where offered. One customer's data is never used to improve the service for another.
- Knowledge sources, web pages and on-screen text are treated as untrusted input, never as instructions.
- The agent says it is an AI when asked, and is configured to say it will check with the Customer's team rather than guess when it isn't sure.
- Lead scores are suggestions for the Customer's team. No decision with a legal or similarly significant effect on a prospect is made solely by automated processing within TalkDemo.
08Data location and international transfers
For Customers in India, TalkDemo stores the database and files in India (AWS ap-south-1, Mumbai) and processes Indian-language speech with Sarvam in India. Some sub-processors process data in other countries, as listed, most importantly the AI model provider in the United States and, for calls in world languages, the speech providers in the United States. Under the DPDP Act, TalkDemo will not transfer data to a country the Central Government restricts. Where the GDPR or UK GDPR applies, transfers outside the EU, EEA or UK rely on the European Commission's standard contractual clauses and the UK International Data Transfer Agreement or Addendum, or another valid mechanism. [TODO: confirm the mechanism with each sub-processor and attach the clauses.]
09Rights requests
TalkDemo helps the Customer answer prospects who exercise their rights: access, correction, completion, updating and erasure, withdrawal of consent, grievance redressal and nomination under the DPDP Act, and access, rectification, erasure, restriction, portability and objection under the GDPR:
- The Customer can find a prospect's sessions and lead record in the dashboard, export them, correct details or delete them.
- Deleting a prospect removes their recordings, transcripts, contact details and answers, and the search entries made from them.
- If someone writes to TalkDemo directly about the Customer's data, TalkDemo passes the request to the Customer within [TODO: working days, for example 3] and helps it respond, unless the law requires otherwise.
10Personal data breaches
TalkDemo will notify the Customer without undue delay, and in any case within 72 hours of becoming aware of a personal data breach affecting the Customer's data. The notice will describe what happened, the data and people likely affected, the likely consequences and the steps taken, with updates as more is known. TalkDemo will help the Customer notify the Data Protection Board of India and affected data principals under the DPDP Act, its supervisory authority within 72 hours where the GDPR or UK GDPR applies, and others where the law requires. TalkDemo will not notify prospects or regulators on the Customer's behalf without its agreement, unless the law requires it.
11Retention, return and deletion
While the service runs, the Customer can shorten retention per agent, and these defaults apply:
Data Kept for Session recordings, transcripts and prospect details 90 days by default, shorter if you set it; recordings can be deleted sooner than transcripts; deleted by a daily job Demo credentials Until you remove them or close the account; sealed with AES-256-GCM, opened only by the browser service Knowledge sources (docs, website pages, decks) Until you delete the source or the agent Audit and security logs 1 year AI call logs (counts and costs, no text) 90 days A daily job deletes data when its period ends. When the service ends, the Customer can export its data within [TODO: period, for example 30 days]. After that, TalkDemo deletes the Customer's personal data, except what the law requires it to keep and de-identified consent proofs. Encrypted backups age out within [TODO: backup window, for example 35 days for daily backups], and data in them is never restored into the service except to recover from an incident.
12Audits
TalkDemo will make available the information the Customer reasonably needs to show compliance with this DPA, including its security documentation and, once it has them, audit reports. TalkDemo is not audited or certified today; its controls are mapped to SOC 2 and ISO/IEC 27001 in an internal register, and a SOC 2 Type I audit is planned when an enterprise customer needs it. Where that information isn't enough, the Customer may carry out an audit, itself or through an independent auditor bound by confidentiality, with [TODO: notice period, for example 30 days] notice, at most once a year unless a regulator requires it or after a breach, during business hours and without access to other customers' data. Each party bears its own costs.
13Contact
Data protection questions: [TODO: privacy contact email, e.g. privacy@talkdemo.com]. Anything else: hello@talkdemo.com. Grievance officer under the DPDP Act: [TODO: grievance officer name (DPDP Act, IT Rules)], [TODO: grievance officer email, e.g. grievance@talkdemo.com].