Privacy by Design: Your Staff See What They Need. Nothing More.
We're built different. Because the housekeeper doesn't need your guest's credit card number to clean a room.
Most platforms show everything to everyone who logs in.
When a housekeeper opens their tablet, a server checks an order, or a maintenance contractor glances at a screen, what do they see? In most hospitality and operations software, the answer is too much: guest emails, phone numbers, payment details, booking totals. Data that has nothing to do with getting the job done. Calisto is built differently.
Built Into the Architecture
Això no és un interruptor de permisos ni una casella de verificació a la configuració. El model de dades mateix separa els expedients comercials dels operatius. Els expedients del personal operatiu no contenen dades financeres, perquè mai hi van ser col·locades.
Global Privacy Laws Are Tightening
GDPR in Europe, CCPA in California, LGPD in Brazil, PDPA across Asia: regulators worldwide are raising the bar on who can access personal data and why. The safest data is data that simply isn't in the wrong place to begin with.
Menys Mans, Menys Riscos
Every person who can see a guest's phone number is a potential data exposure point. Not because your staff are untrustworthy, but because limiting access is simply better practice. Calisto enforces this automatically.
Two records. One transaction. Each built for a different audience.
Every booking in Calisto creates two distinct records: the Booking and the Reservation. They're linked, but they serve entirely different purposes and reach entirely different people.
The Commercial Record
The full financial and identity picture, visible only to the people who need it: admins, finance, revenue managers, and owner statements.
- · Confirmation code, guest name, email, phone
- · Detalls del pagament, valor total, saldo a pagar
- · Booking source (direct, OTA, corporate, proposal)
- · Històric financer i enllaçament de foli
Who sees this: Admins · Finance · Revenue managers · Owner reports
The Operational Record
The fulfillment-focused view: everything the team needs to deliver the service. Nothing they don't.
- · Asset assignment, dates, and status
- · Nom del primer nom de l'invitat (per a personalització)
- · Petició especials, notes, nombre d'ocupants
- · Check-in/out status, cleaning tasks, key management
Who sees this: Front desk · Housekeeping · Servers · Field staff · Kiosks
Regla pràctica: Si la persona que executa el servei no necessita les dades per fer el seu treball, pertany a la Reserva, no a la Reserva.
What this looks like across your team
El mateix principi s'aplica a cada sector. Diferents indústries, mateixa arquitectura.
Hotels & Short-Term Rentals
Un netejador obre la seva llista de tasques i veu "Habitació 214, King, neteja de sortida, 2 convidats." No veu l'email, el número de telèfon del convidat ni el que ha pagat per nit. La habitació es neteja. Les dades romanen protegides.
Resultat: Eficiència operativa sense exposició de dades
Restaurants i Hostaleria
A server sees "Table 6, 2 adults, 1 child, nut allergy noted." They can personalize the experience. They can't see the billing account, the corporate booking reference, or the guest's contact information.
Result: Personalized service, contained information
Benestar i spas clínics
A therapist sees the appointment, treatment type, and client preferences. Billing, insurance details, and contact information are handled separately by admin staff, not visible at the treatment level.
Result: Clinical professionalism with proper data boundaries
Golf Clubs & Experience Operators
Un iniciador o guia veu "8:12am, John S., 4 jugadors, cistella demanada". El número de membre, el saldo del compte i els detalls de contacte romanen on pertoca: al registre financer, no a la fulla del camp.
Result: Smooth operations without unnecessary access
A permission toggle is not the same as architectural separation
La majoria de plataformes gestionen això amb controls d'accés: amagar camps determinats per a certs rols. Sona similar. No ho és.
Field-Level Permissions
The data is still in the record. It's just hidden in the UI. A misconfigured role, a shared login, or a developer query can expose it. The risk doesn't disappear; it's just masked.
One Big Record
When a single record holds everything (identity, payment, operational notes), the blast radius of any access mistake is the entire record. There's no clean boundary between what's sensitive and what's not.
Calisto Architecture
Booking and Reservation are separate data structures. Operational records don't contain financial fields, because they were never designed to. You can't expose what isn't there.