Security and data
What is true today, and what is not.
Bookesto is pre-launch. This page states what is implemented, what is not started, and what has to happen before each item changes. There are no badges on this page.
Implemented and verified in the build
Distinct ALTER TABLE … FORCE ROW LEVEL SECURITY statements in packages/db/prisma/migrations · counted 2026-08-17
Not started, and we are not going to imply otherwise
| Item | Status | What changes it |
|---|---|---|
| SOC 2 Type I or II | Not started | Begins after the first 100 paying merchants |
| ISO 27001 | Not started | Not planned before SOC 2 |
| EU data-protection compliance claim | Not claimable | Requires an Article 27 representative, a DPA with standard contractual clauses, and EU-region hosting. All three pending. EU signups are gated until then |
| PCI DSS | Not applicable to us | Stripe is assessed; we are not the entity being assessed. Card data does not touch our servers |
| Uptime SLA | No operating history | There is no production deployment. An SLA without history is a fabrication |
| Public status page | Not published | Ships when production is real, and will show real incidents |
| Penetration test | Not commissioned | Before private beta |
If you need a completed security questionnaire, a signed DPA or a pen-test report before you can buy, we do not have them yet. Saying so now is cheaper for both of us than saying so after a procurement review.
Who else touches the data
| Subprocessor | Purpose | Data | Region |
|---|---|---|---|
| Hetzner Online GmbH | Hosting and backups | All application data | Germany or Finland, stated per deployment |
| Stripe | Payment processing | Payment metadata. Card data never reaches Bookesto | Ireland / United States, per Stripe's terms |
| 360dialog GmbH | WhatsApp Business API access | Message content and phone numbers for WhatsApp only | Germany |
| Meta Platforms Ireland | WhatsApp message delivery | Message content and phone numbers for WhatsApp only | Ireland |
This list is complete as of . Adding a subprocessor requires prior notice, and we will publish the change on the changelog before it takes effect.
The subprocessor page, with the change-notification commitmentYour data, your exit
These are commitments about the service, not a description of a running one. There is no deployment and there are no accounts yet, so nothing below has been exercised by a customer.
Why we only use the official API
Unofficial WhatsApp gateways get business numbers permanently banned. Bookesto connects only through Meta's official Cloud API, through 360dialog, and there is no mode in which it does anything else — including in testing. This is a merchant-protection decision as much as a compliance one.
Found a problem
Email security@bookesto.com. Include enough detail to reproduce it. We will confirm receipt within two business days and tell you what we are doing about it. There is no bounty programme yet and we are not going to pretend there is.
Security questions
- Where is the data hosted?
- Hetzner, in Germany or Finland, with the region stated per deployment. EU-region hosting for EU tenants is part of the data-protection pack that is not yet complete.
- Can I get a DPA?
- Not yet. It is drafted for counsel review and it is on the roadmap. When it is signable, this page will link to it.
- Who is the legal entity?
- AL MANNAN GENERAL TRADING FZE-LLC, Sharjah, United Arab Emirates.
- Do you train models on my data?
- No. There is no customer-facing model runtime at all today, and if one is ever approved, training on customer data will not be part of it.
Status of this page checked