Cambrino
Security

Guest data is the most personal data you hold

Who slept where, company billing details, payment references, allergies. Here is what the system does about that, and what it does not do yet.

One hotel cannot see another

Every reservation, guest and invoice carries the hotel it belongs to, and every query is filtered by it at the database layer rather than by each screen remembering to.

Least privilege, per hotel

Roles are held per hotel, so the same account can manage one property and only clean at another. Two-factor is enforced, not offered, on administrator accounts.

An activity log on the record itself

Bookings, rooms, guests, invoices, companies and accounts each keep a log of who changed what and when, readable next to the record rather than in a separate tool.

Card details never reach us

Payments run through the provider's own hosted checkout. Card numbers are never sent to, processed by or stored on our servers.

European by default

The company, the team and the hosting are in Europe. Ask us for the current hosting details in writing and we will put them in the agreement.

You are the controller

Your guests' data is yours. We process it on your instruction, under a data processing agreement, and you can have all of it back at any time.

What is not in place yet

There is no external penetration-test report, no formal certification, and no automated retention or one-click erasure — deletion requests are carried out by hand today. We would rather you knew that than read a list of adjectives. If you need any of it contractually, ask, and we will tell you where we genuinely stand.

info@cambrino.com