Trust center
Security, privacy and compliance in one place: how your demo tenant and your prospects' data are protected, and where each framework stands.
Last updated
What a security review asks first
TalkDemo is pre-launch, in private pilots. These controls are built with the product, and the security page marks each one Planned until it ships with its test.
- Data region
- India for Indian customersThe database and files are in AWS Mumbai and Indian-language speech runs on Sarvam in India. The AI model, and speech for world-language calls, run in the United States.
- Demo credentials
- Sealed, never shown to the AIThe demo login is encrypted and opened only by the browser service to fill your login form. It never appears in a prompt, a log or an API response.
- Guardrails
- Checked in codeEvery click and keystroke passes your URL allowlist and blocked actions before it runs, whatever the model asked for.
- Recording
- Only after notice and consentThe call page tells the prospect the call is with an AI agent and asks before recording starts. No camera, ever.
- Retention
- 90 days by defaultRecordings, transcripts and prospect details are deleted by a daily job, or sooner if you set a shorter period.
- Certification
- Not audited yetControls mapped to SOC 2 and ISO/IEC 27001, not audited yet. We show no badges and will say so here only when an audit is complete.
Security, privacy and compliance
Security
The agent runs only in your demo tenant, in one isolated cloud browser per call that is destroyed afterwards. The demo login is sealed and the model never sees it. Every browser action passes your guardrails in code. The database itself keeps each customer's data apart, and the audit trail lives in a separate logs database.
Privacy
Prospects never need an account and never turn on a camera. They are told the call is with an AI agent and asked before recording. Contact details are encrypted, IP addresses are kept only as a hash, and customer data is never used to train models.
Compliance
You are the data fiduciary under India's DPDP Act and the controller under the GDPR, and TalkDemo is your processor. The product supports your duties: notice and consent before recording, retention you control, access and deletion requests, and a public sub-processor list.
Aligned with the frameworks, not certified
TalkDemo holds no certifications. We keep one control register mapped to SOC 2, ISO/IEC 27001, India's DPDP Act and the GDPR, and this is where each one stands.
| Framework | Where we are |
|---|---|
| SOC 2 | Not audited. Controls are mapped to the Trust Services Criteria in an internal register and built with the product. |
| ISO/IEC 27001:2022 | Not certified. The same controls are mapped to Annex A. |
| India's DPDP Act 2023 | Designed for customers as data fiduciaries: notice and consent before recording, retention limits and data in India. |
| GDPR and UK GDPR | Designed for the processor role: recording consent, access and erasure tools, customer-set retention and a public sub-processor list. |
Next steps for each framework are on the security page.
Every trust and legal page
Trust
Legal
- Privacy policyDraftWhat we process and why
- Terms of serviceDraftThe agreement with your company
- CookiesEvery cookie and storage item we use
- Refund policyDraftCancelling and refunds
- Enterprise SLADraftUptime, service credits and support response targets
- Acceptable useWhat TalkDemo and its agents may not be used for
Questions, reviews and reports
Security questionnaires, procurement reviews and privacy questions: email hello@talkdemo.com.
Found a security problem? Email hello@talkdemo.com with “Security” in the subject. The rules for testing are on the security page, and our security.txt lists the same address.