Security
Your data, and why you can trust us with it.
We do not have a client list to show you yet. What we can show you is how this is built.
Every hotel in its own place
Every row says which company it belongs to, and no query runs without that filter. And an automatic check refuses to let code through that skips the rule.
Where it lives
On an OVHcloud server in Gravelines, France, inside the European Union. Cloudflare sits in front, filtering traffic and serving the site.
Who else touches it
Stripe for payments, Resend for email, Cloudflare for backups and photos, Aiosell if you take distribution and Apple for the contact mailboxes. All of them are in the privacy policy, named, with where they handle the data.
Backed up every night
A full dump every night, stored off the server, with thirty days of history. A backup only counts as a backup once someone has restored it, so it gets restored.
If you leave, you take it
Reports download as CSV from inside the programme, any time and without asking. Reservations, guest records, folios and invoices are handed over on request, in a standard format, within fifteen days and at no cost.
What we do not keep
The image of the identity document. No photo or copy of the document is uploaded or kept: only the details the law asks for.
The session closes itself
After a while unused, and you choose how long. A front desk is left alone more often than you would think.
How we check
Every change goes through more than two and a half thousand automated tests before it reaches you, and an accessibility audit that tolerates no failures at all. One of those checks exists for this alone: that no query leaves without saying which hotel it belongs to.
Anything left to ask?
If your advisers need a particular document, say so and we will give it to you before you sign anything.