# How TalkDemo protects your demo tenant

> The safeguards around live product demos, from sealed credentials and isolated browsers to guardrails checked before every click and a full action log.

Source: https://talkdemo.com/help/privacy-and-security/how-talkdemo-protects-your-demo-tenant · Updated 2026-11-20

## Key takeaways

- TalkDemo only ever drives a dedicated demo tenant, never your production account.
- Credentials are sealed with AES-256-GCM, filled into the login form by TalkDemo's platform and never sent to the AI.
- Every session gets its own isolated cloud browser, destroyed when the session ends.
- Every action is checked against your guardrails before it runs and logged on the session's actions timeline.

Letting an AI click around your product is a fair worry. TalkDemo is built so that the worst a session can do is limited to a demo tenant full of sample data, and every action can be traced.

**Who can do this:** Everyone can read this. Admins manage credentials and guardrails.

## Layer 1: a dedicated demo tenant

Live product mode connects only to a demo tenant you create for demos. Never connect production. Give the demo user the least access a demo needs, and fill the tenant with sample data. See [Connect your demo tenant](/help/product-and-flows/connect-your-demo-tenant).

## Layer 2: credentials the AI never sees

1. An Admin enters the demo username and password once.
2. They are sealed with AES-256-GCM straight away and never shown again, to anyone.
3. At the start of a session, TalkDemo's platform opens them and types them into the login form, before the AI agent gets the browser.
4. The AI only knows it is "logged in as the demo user". Credentials never appear in prompts, logs, API responses or the dashboard.

## Layer 3: one isolated browser per session

Each session gets a fresh cloud browser. No cookies or data carry over between prospects. The browser is destroyed when the session ends, and, if you set one, the reset method restores your demo data.

## Layer 4: guardrails before every action

TalkDemo checks every click, keystroke and page change in code before it happens:

- https pages on your tenant's host and your allowlist only.
- Delete, billing, settings, payment, export, invite and similar actions blocked by default.
- Password and file inputs never touched.
- Optional read-only mode.
- Email addresses and phone numbers never typed in.

The AI cannot see or change these rules. See [Guardrails](/help/agents/guardrails).

## Layer 5: a full record

Every action, tool call and refusal is logged on the session's actions timeline, with its time. Refused actions show which rule stopped them. Changes your team makes, such as a saved demo login or a new guardrail, go to **Settings → Activity log**. See [Review sessions](/help/sessions-and-leads/review-sessions).

## Also in place

- Encryption in transit (TLS) and at rest.
- Each workspace's data separated in the database, so one workspace cannot reach another's.
- Customer data is never used to train AI models.

## What is not in place yet

TalkDemo has not completed a SOC 2 or ISO 27001 audit. Our controls are mapped to both, and we plan an audit when the first enterprise customer needs it.

**Privacy:** the AI receives the transcript, your knowledge passages and a summary of the screen, never credentials. See [Workspace region and data residency](/help/team-and-settings/workspace-region-and-data-residency).

## Frequently asked questions

### Can a prospect take control of the browser?
No. Prospects watch and talk; the agent drives.

### Can I see which actions were refused?
Yes. They appear in each session's actions timeline.
