The GDPR and TalkDemo
Last updated 20 November 2026
How TalkDemo supports your GDPR duties when you sell in Europe.
The General Data Protection Regulation (“GDPR”) applies when a customer in the EU or EEA uses TalkDemo, or when a customer elsewhere runs demos for prospects there. The UK GDPR, with the Data Protection Act 2018, applies in the same way for the UK. The two match closely, so the article numbers on this page apply to both unless a line says otherwise. This page explains how TalkDemo is designed to support a customer's obligations. It is general information, not legal advice.
TalkDemo is pre-launch. The controls below describe how the product is designed and built against a control register. None of it is audited or certified, and there is no GDPR certificate to hold. The security page marks each control as planned until it ships.
In short
- You are the controller for your prospects' data. TalkDemo is your processor, under the data processing agreement.
- Prospects are told they are talking to an AI and asked before the call is recorded.
- Transfers outside the EU, EEA and UK are covered by standard contractual clauses and the UK transfer agreement.
- TalkDemo tells you about a breach within 72 hours at the latest, so you can meet your own deadline.
01Controller and processor
- Customers are controllers for prospect data. They decide to use TalkDemo, where agents appear, what they ask, whether calls are recorded, which integrations receive the data and how long it is kept.
- TalkDemo is a processor for that data, acting only on the customer's documented instructions under the data processing agreement (Art. 28). It does not use prospect data for its own purposes, sell it, or use it to train AI models.
- TalkDemo is a controller only for customer team accounts, billing, website visitors, enquiries and the waitlist, as described in the privacy policy.
02Lawful basis for each purpose
Purpose Lawful basis Running a demo the prospect asked for: the conversation, showing the product, answering questions and qualifying Usually the customer's legitimate interests in responding to a prospect who asked for a demo (Art. 6(1)(f)), or steps taken at the prospect's request before a contract (Art. 6(1)(b)). Set by the customer. Recording the call The prospect's consent (Art. 6(1)(a)), asked on the call page before recording starts, or the customer's legitimate interests where it has documented them. TalkDemo asks for consent by default. Marketing email from the customer The prospect's separate consent (Art. 6(1)(a)), and any e-privacy rules that apply to the customer. Customer team accounts and providing the service to the customer Contract with the customer (Art. 6(1)(b)). TalkDemo is controller here. Security, abuse prevention and audit trails Legitimate interest in keeping the service and the data in it safe (Art. 6(1)(f)). Billing records and tax Contract (Art. 6(1)(b)) and legal obligation (Art. 6(1)(c)). TalkDemo is controller here. Replying to enquiries, pilot requests and the waitlist Steps taken at your request before a contract (Art. 6(1)(b)), or consent for the waitlist (Art. 6(1)(a)). TalkDemo is controller here. The customer, as controller, chooses and documents its own lawful basis. A customer relying on legitimate interests should record its balancing test. Where consent is the basis, TalkDemo's consent records (purpose, notice version and time for each grant and withdrawal) help the customer show that consent was given (Art. 7).
03Notices to prospects
- Before the call starts, the call page tells the prospect they are talking to an AI agent, which company it is for and whether the call will be recorded.
- The call page links to the customer's privacy notice, where the customer gives the information Art. 13 requires, and to TalkDemo's processor notice.
- The notice version a prospect saw is recorded with their consent choices.
- The agent says it is an AI whenever a prospect asks.
04Data minimisation
- The prospect's camera is never used and their screen is never recorded. The shared screen is the agent's browser showing the customer's demo tenant.
- Email addresses and phone numbers are sealed (encrypted, with a keyed hash for de-duplication). IP addresses are stored only as a hash, with the country.
- The AI model receives only what the conversation needs, never demo credentials, with zero-retention settings where the provider offers them.
- There are no voiceprints and no emotion detection.
- Customers are told not to ask for special category data in qualification questions, and agents don't ask for it.
05Data subject rights
Right How TalkDemo is designed to support it Access and portability (Art. 15, 20) The customer finds the prospect's sessions and lead record in the dashboard and exports them, including the transcript and answers. Rectification (Art. 16) The customer corrects the prospect's details or answers in the lead record. Changes are recorded in the audit trail. Erasure (Art. 17) The customer deletes the prospect. Recordings, transcripts, contact details, answers and the search entries made from them are removed. The de-identified consent proof remains. Withdrawing consent (Art. 7(3)) Recording and marketing email are separate consents. Withdrawing one stops that processing and starts deletion of what it covered. Objection and restriction (Art. 18, 21) Requests go to the customer, which can stop follow-up and restrict or delete the record. TalkDemo helps it act on them. Automated decisions (Art. 22) The agent suggests a lead score for the customer's sales team. No decision with a legal or similarly significant effect is made solely by automated processing within TalkDemo. The customer answers each request within the one-month limit. Requests that reach TalkDemo directly are passed to the customer, and TalkDemo helps it respond. Prospects can also complain to their supervisory authority: in the UK, the Information Commissioner's Office (ICO).
06Retention
Recordings, transcripts and prospect details are kept for 90 days by default (Art. 5(1)(e)). The customer can set a shorter period per agent, and a daily job deletes data when its period ends. The defaults are:
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 07International transfers
Calls are routed to the region nearest the prospect. Data for Indian customers is stored in India. Some providers process data outside the EU, EEA and UK, including these in the United States:
- Anthropic (Claude): the agent's conversation and reasoning, summaries and lead scoring.
- Deepgram: speech-to-text for English (US, UK and Australia) and world languages.
- ElevenLabs: text-to-speech for English (US, UK and Australia) and world languages.
- Cartesia: backup text-to-speech for world languages.
- OpenAI: embeddings for knowledge search (text-embedding-3-small), and backup text-to-speech for world languages.
- Stripe: card payments in US dollars, with receipts and invoices.
The full list is on the sub-processors page. Personal data of people in the EU or EEA that leaves those areas will be covered by the European Commission's standard contractual clauses, and UK data by the UK International Data Transfer Agreement or Addendum, set out in the data processing agreement.
08Security of processing
TalkDemo's measures under Art. 32 include separating each customer's data in the database itself, demos only against demo tenants in one isolated browser per session, sealed demo credentials and contact details, encryption in transit and at rest, two-factor sign-in and least-privilege roles for staff, and an audit trail of every agent action in a separate database. See the security page for each control and its status.
09Breach notification
TalkDemo will inform the customer without undue delay, and within 72 hours at the latest, after becoming aware of a breach affecting its data (Art. 33(2)), with the details the customer needs to notify its supervisory authority within 72 hours of becoming aware itself (the ICO in the UK) and, where required, the prospects affected. TalkDemo notifies directly for data it controls.
10Records, impact assessments and representatives
Records of processing (Art. 30) are being prepared alongside the data processing agreement. TalkDemo uses only the providers on the sub-processors page and tells customers before adding one.
Some customers will want a data protection impact assessment (Art. 35) before putting an AI agent in front of prospects. TalkDemo can provide what goes into one: the data flows, the sub-processor list, what the agent and the AI model do and don't do, and the security controls.
EU and UK representatives (Art. 27): [TODO: name the EU and UK representatives if required once customers there sign up]. Company: [TODO: contracting entity, e.g. PitchWitch Ventures LLC or the Indian operating company]. Questions: [TODO: privacy contact email, e.g. privacy@talkdemo.com] or hello@talkdemo.com.