Trust Center

Security with explicit boundaries, not generic badges.

Helios is designed around tenant isolation, scoped access, strong authentication, auditability and controlled integrations. The Trust Center explains what those principles mean in practice and what is verified for each deployment.

HELIOSTrust CenterArchitecture · Access · Audit · Privacy
Security principles

Six principles that define the security model.

Implementation details are reviewed for each environment and deployment scope.

01

Scoped access

Roles, properties and permissions restrict who can view or perform each function.

02

Authentication

2FA, session controls and additional checks are used for sensitive administrative surfaces and flows where applicable.

03

Auditability

Critical changes and operational actions can leave a trace so review and investigation remain possible.

04

Integration boundaries

Every PMS, Wi-Fi, printer or API integration is assessed before it becomes supported scope.

05

Data minimisation

Data and analytics should be limited to the purpose, permissions and consent model of the specific deployment.

06

Production safeguards

Deployments, health checks, backups and recovery procedures are treated as operational requirements rather than afterthoughts.

Production review

What we review before a property enters production.

01

Identity & roles

Which users exist, which scopes they need and which actions require stronger protection.

02

Tenant & property boundaries

How data and operations are separated by account, property and role.

03

Integrations

Credentials, endpoints, network dependencies, permissions and ownership for every external system.

04

Privacy & consent

Which data is necessary and which optional analytics or marketing signals require appropriate consent.

05

Operational fallback

What happens when a dependency or integration is unavailable and which fallback procedure has been agreed.

06

Backup & recovery

What is protected, how recoverability is checked and who owns the operational process.

Explicit boundaries

What we do not present as guaranteed without verification.

We do not use a certification or compliance badge unless a formal certification exists for the stated scope.

We do not treat a PMS, Wi-Fi stack or third-party system as compatible before technical assessment.

The Emergency layer supports predefined hotel procedures and does not replace official emergency plans or emergency services.

Smartwatch notification delivery depends on the paired device, operating system and notification settings. It is not presented as an independent smartwatch integration.

Helios is not presented as a fully offline system. Connectivity requirements and fallback flows are defined per deployment.

Privacy & data

Privacy and analytics with a first-party approach.

The public sales site and guest journeys should separate necessary functions from optional analytics or marketing processing. Final configuration depends on the use case, property and the controller's legal obligations.

Sales site privacy policy
Security review

Need a security review before a pilot or procurement process?

We can structure a technical discussion around roles, integrations, data flows, privacy requirements and deployment boundaries for your property.