Security. What Henk can and cannot do.
The most honest protection for an AI desk is how little it is allowed to do. Henk talks to your visitors and nothing else. Below is exactly how it is set up, including what we do not have.
The best protection is what he is not allowed to do.
Most worries about AI on a website are about what such a system might do. With a desk the answer is short: nothing. Henk has no buttons to press.
He cannot change anything
Henk has no access to your systems. He cannot place an order, change an invoice, open an account or delete anything. He talks. That is all he does.
He keeps no conversations
What a visitor asks Henk is not stored by us anywhere. The conversation goes to the language model to produce an answer and after that it is gone. Only what someone fills in a form themselves is kept.
He makes no commitments
Henk quotes no amounts, promises no delivery dates and closes nothing. What a desk costs depends on the situation, and that is for a human to say. When in doubt he hands over.
He only runs on your site
The desk only accepts requests from the domain it was built for. Anyone trying to put it on their own website gets nothing.
How it is locked down.
- The key sits on the server, never in the browser
- Only your own domain may call the desk
- A limit per visitor, so nobody can hammer the desk
- Conversations are capped: at most twenty messages, 4000 characters each
- Only the intended requests get through, the rest is refused
- Security headers against piggybacking and outside snooping
Where the data travels.
Four parties, nobody else. No ad networks, no trackers, nothing sold on.
| Party | What for |
|---|---|
| Netlify | The website and the desk run here. |
| Anthropic | Produces the answer Henk gives. Their terms state that they do not use customer content to train their models. |
| Supabase | Stores only what someone fills in a form themselves: name, email address, phone number and their question. |
| Resend | Sends us the notification when an enquiry comes in. |
What we are straight about.
A security page that only reassures is itself a reason for concern. These are the things you should know before you say yes.
People try to talk Henk out of his role
That is called prompt injection and it genuinely happens. Henk has instructions to stay in role, and that works in the vast majority of cases. It is not guaranteed. What protects you is not the instruction but the fact that he can carry nothing out.
A language model can get something wrong
That is why Henk quotes no amounts, makes no commitments and hands over to a human when in doubt. That is a choice in his instructions, not something we patched afterwards.
Because we store nothing, we cannot look back either
The upside of not storing conversations is that nothing can leak. The downside comes with it: if a visitor says Henk promised something, we have no recording to check that against. If you do want that, raise it during the baseline scan and we will look at how to arrange it.
We have no ISO certification
We are a small company just getting started. If your procurement asks for a certification, a penetration test report or a data processing agreement, say so right away. Then we discuss what is needed instead of talking around it.
Do you have a questionnaire? Send it over.
Many companies have a standard list of supplier questions, or a data processing agreement that needs signing. Send it over. We will fill it in honestly, including where the answer is no.