Going live
How your account is protected
What the widget ID can and cannot do, in full.
Three layers, none relying on secrecy
| Protection | How it works |
|---|---|
| Domain locking | Every request is checked against your approved domains before anything is returned. A request from any other website is refused. This, not secrecy, is the security boundary. |
| One-way hashing | We never store the widget ID itself, only a SHA-256 hash, which cannot be reversed. Even with full database access the value cannot be read back out. |
| Server-side credentials | Credentials for booking and e-commerce systems are held on our servers and never sent to a browser. Those calls are made from our infrastructure. |
What the widget ID cannot do
If someone copied your widget ID out of your page source, they could not:
- Read or change anything in our database
- Reach any other customer's account or content
- See your conversation history or your visitors' messages
- Change your assistant's content, settings or approved domains
- Authenticate to your booking or e-commerce system, or alter an order
The only thing it permits is asking your assistant a question, exactly what any visitor can already do by clicking the launcher.
Approved domains
Your approved list should name every domain that runs your assistant, staging sites included. We maintain that list for you. A www. prefix is handled automatically, so example.com also covers www.example.com.
Reply to the email your installation guide came with and we will add any others the same day, or join a short call and we will walk your developer through the change.