Card payments
When online payment is switched on for a property, card payments are taken on Stripe-hosted Checkout pages. Card numbers are entered on Stripe's systems and never pass through or rest on HotelMesh servers; HotelMesh has no place to store them and keeps only the payment amount, status and Stripe's reference. Stripe webhooks are verified by signature before any payment is recorded. Online payment is being switched on; payments taken at the desk are recorded against the reservation.
Encryption
All traffic between browsers, HotelMesh and its providers uses HTTPS (TLS). The database and file storage are hosted on Supabase, which encrypts data at rest.
Tenant isolation
Every record is tied to its organisation or property, directly or through its parent record, and PostgreSQL row-level security is enabled on every table, restricting each query to the caller's own organisation. Privileged operations run inside database functions that enforce the same checks, and authorisation is applied on the server for every request; what the interface shows is never treated as permission.
Access control
Staff sign in with Supabase Auth. Each staff member has a role with explicit permissions, and property-level permissions limit which properties they can see. Important operational and financial actions are written to an audit log that records who did what and when. Financial records are corrected with adjustments rather than destructive edits.
Secrets and integrations
Service credentials, payment keys and channel-connectivity tokens are held as server-side environment variables and are never sent to the browser. Connections to messaging providers store only a reference to the credential, not the secret itself. Inbound webhooks from payment and channel providers are checked for authenticity before they are processed.
Reliability
Reservation, inventory and payment operations are transactional and idempotent: a retried payment request is recorded once, and HotelMesh never sells its last room twice through the desk or the booking engine.
Backups
The database is hosted on Supabase, which takes automated backups of hosted projects. Backup frequency and retention depend on the Supabase plan in use.
What we are still verifying
The following are not yet confirmed and are not claimed above:
- The exact backup schedule, retention period and whether point-in-time recovery is enabled on the production project.
- A documented restore test.
- Independent security certification (for example SOC 2 or ISO 27001). HotelMesh does not currently hold one.
- A formal vulnerability disclosure programme and penetration test report.
Reporting a security issue
If you believe you have found a security issue in HotelMesh, write to hello@hotelmesh.io. Please include enough detail to reproduce the issue, and allow time for a fix before sharing it publicly.