Trust & security

The postureyour auditor expects.

HotelOS handles guest PII, payment tokens, payroll signals and the general ledger. Treat us like a finance system, because we are one.

This page is the single source of truth for our security posture, data architecture and compliance status. It says what is in place today and what is not. Procurement teams get the same answers.

Certifications & frameworks

Where we stand
on the paperwork that matters.

Certification 01

SOC 2

Not certified

HotelOS does not hold a SOC 2 report today. When an audit is under way we will say so here, with dates, and not before.

Certification 02

PCI DSS

No card data stored

HotelOS does not store card numbers or security codes. Card payments run through your payment provider; HotelOS records that a payment was made, not the card.

Certification 03

GDPR · APPI · PDPA

Standard Article 28 DPA

Our DPA and sub-processor list are published under Legal, with standard contractual clauses for transfers outside the EU. Data Protection Officer at [email protected].

Certification 04

ISO 27001

Not certified

HotelOS is not ISO 27001 certified and has not set a target date.

Data architecture

How we hold
your operating data.

Hosting & residency

Your HotelOS database is stored in the EU, in Frankfurt. Some uploaded files and attachments are currently stored in Asia-Pacific. Named sub-processors, including some in the US, process customer data under standard contractual clauses. Pages and APIs are served from a global edge network.

Encryption

Data is encrypted at rest (AES-256) by our database and storage providers, and in transit with TLS. Credentials for the systems you connect, such as mail and accounting tokens, are kept in an encrypted secrets vault. Customer-managed keys are not offered.

Identity & access

Sign in with email and password or a work account, with multi-factor authentication and passkeys, and one sign-in across every HotelOS app. Access is role-based and scoped to your organisation and property. Enterprise single sign-on (SAML) and SCIM provisioning are not offered yet.

Audit trail

Administrative and approval actions are written to an audit log whose entries are hash-chained, so an altered or missing entry can be detected. Owners can export it from Command.

Backup & resilience

Our database provider takes automated daily backups. We have not published recovery-time or data-loss targets, and will not until we have measured them in production.

Sub-processors

Our sub-processor list at /legal/subprocessors names every company that may handle personal data, including each AI model provider and where it processes data. We give 30 days' notice before adding a sub-processor.

Operating policies

How we behave
when something goes wrong.

Penetration testing

No independent penetration test has been completed yet. When one is, the date and a summary of findings will appear here.

Vulnerability disclosure

Report suspected vulnerabilities to [email protected]. We welcome good-faith research reported to us privately.

Bug bounty

There is no bug-bounty programme today.

Breach notification

Commitment to notify within 72 hours of a confirmed material incident, with a written remediation plan inside 14 days. Codified in every customer DPA.

Service status

status.hotelos.ai runs live health checks against every product, refreshed every minute. It shows current status only; during an incident we contact affected customers directly.

Sub-processor changes

We announce additions to the sub-processor list 30 days before they take effect, so you can review them and object.

Procurement is welcome

Hand us your security questionnaire.

Send us your questionnaire: CAIQ, SIG-Lite or your own. We answer from what is in place today, including the gaps, and agree a timeline with you.