Security & privacy
Last updated 2026-11-07.
Plain rules, not promises: this is what a bot can and can’t do in your business. By default, nothing is sent, paid, deleted or published without your OK.
Ask first
Deletions, external messages and merges wait for you, unless you turned that approval off for that bot, or granted that bot a standing rule for that action from an earlier approval. Paying always stays with a person: no plan, setting or toggle changes that.
Bots prepare, you pay
A bot never holds a card. It builds the cart in your own account or stops at the payment screen; you press Pay. ZeeDo never holds a card or moves money.
Your passwords stay yours
Bots use your credentials without ever reading them; three operations exist and none returns a secret to a model.
Watch, replay, take over
Watch any bot live, replay what it did, take over any time with your own mouse and keyboard.
If a bot is ever tricked
Prompt injection is unsolved industry-wide. ZeeDo is built so that a bot which is persuaded cannot do anything irreversible without a human.
Bots say they are bots
In the first message of every conversation and in every email signature. Forms are not stamped.
Recordings are masked at capture: password and card fields, payment frames and the fields the vault fills, and every input field while a person has taken over.
Customer data is stored and processed in the EU (France, Germany and Ireland), except two checks a model in the United States may make unless an organisation keeps them in the EU: reading the rules people set for a bot, and checking a button a bot is about to press.
- DPA with SCCs
- Published sub-processors
- Erasure within 72 hours
The binding list of our technical and organisational measures is Annex 2 of our Data Processing Addendum.
When a bot needs you to sign in to a website, you type the password on its screen yourself. The bot does not see your password, and ZeeDo does not record it.
With your own key, prompts go to the provider you chose under your contract. ZeeDo’s model uses only providers that keep no copy and do not train on your data; for EU organisations requests are processed in the EU, except the reading of the rules people set for a bot and the check of what a control a bot is about to press would do, which may be served from the United States.
We test our own security, as Annex 2 of our Data Processing Addendum describes under Testing.
Found a security problem? Our vulnerability disclosure policy says how to tell us.