Guardrails
Show the product without being able to change it.
A demo agent should be able to show your product and be unable to change it. DemoPage opens only pages you approved, refuses payments, invites, API keys, and account changes in every mode, blocks write requests at the network layer, masks secrets on screen, and sends questions it can't answer from your pages to your team.
Last reviewed 2026-10-26. Written from what the product does today.
What happens when something goes wrong
Each row is a situation a demo agent meets, what DemoPage does, and where the behavior is documented.
| If this happens | DemoPage does this | Documented in |
|---|---|---|
| A visitor asks for a discount | Not promised. The question goes to your team. | The never-list: no discount is promised |
| A visitor asks for a price you haven't published, or the roadmap | Not guessed. The question goes to your team. | Answers come only from pages you approved |
| A question hides an instruction, such as "ignore your rules" | Treated as untrusted text. It never becomes navigation or a tool call, and your team gets it as a follow-up. | Security page, visitors section |
| A click on Pay, upgrade, or change plan | Refused in every mode. | Security page, what it can't click |
| A page sends a delete or update request, or a GraphQL mutation | The request fails at the network guard, and payment processors' pages never load. | Security page, what it can't click |
| A sign-up, trial, or booking page | Kept out of the demo browser, outside sign-in. | Security page, what it can't click |
| An API key or token appears on screen | Blanked before any page script runs, and kept out of narration, recordings, and what the AI model sees. | Security page, secrets on screen |
| A password or card field | Shown as dots, even if the page switches it to plain text. | Security page, secrets on screen |
| A link to a page you didn't approve | Not opened. Only https pages on the approved list load. | Security page, the demo browser |
| The visitor's own login | Never used. A demo signs in only with a sandbox login you provide. | The never-list |
The never-list
In any demo, in any mode, DemoPage never does these eight things.
- Pay for anything
- Sign anyone up
- Change your CRM
- Make a phone call
- Send an email
- Use a visitor's own login
- Open a page you didn't pick
- Promise a discount
Where the guardrails stop
A guardrail is a promise about what the demo browser will do. It is not a certification, and some things aren't available yet:
- Single sign-on (SSO) and audit export
- A private-network runner that reaches apps behind your firewall
- Data residency outside the United States
Keep these out of sandboxes, logins, and the pages you approve:
- Protected health information
- Payment card data
- Government ID numbers
Seven questions to ask any vendor of a demo agent
- Does the agent run in your visitor's browser, or on the vendor's machines? Where it runs decides what a visitor can reach.
- Which pages can it open, and who decides? An approved list is safer than a crawl.
- Which actions are blocked in code, and which are only discouraged in a prompt?
- What happens to a question it can't answer from your pages? A guess is worse than a handoff.
- How are secrets on screen handled, and do they reach the model and the recording?
- How is a sandbox login stored, and how long does a saved sign-in last?
- What can it not do yet? A vendor that lists nothing is hiding something.
When not to use DemoPage for this
- A review that needs a named certification. The security page lists what isn't available yet, and no certification is claimed here.
- Pages that contain protected health information, payment card data, or government ID numbers. The terms don't allow them in sandboxes or approved pages.
Questions
What teams ask.
Can the demo agent submit a form or pay for something?
No. Payments, plan changes, invites, API keys, sign-ups, and account deletion are refused in every mode, and the network guard fails write requests as a second layer.
What happens to a question the agent can't answer?
It isn't guessed. Prices you haven't published, discounts, and the roadmap go to your team as a follow-up, and the visitor is told a person will reply.
Does the agent see my visitor's passwords or cards?
Password, card, and ID fields are shown as dots and card numbers in text are cut to the last four digits. Masked text stays out of the narration, the recording, and what the AI model sees.
Is this the same as the security page?
The security page is the full reference. This page answers one question, what the agent can't do, and links to the detail.