Scoped access
Roles, properties and permissions restrict who can view or perform each function.
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.
Implementation details are reviewed for each environment and deployment scope.
Roles, properties and permissions restrict who can view or perform each function.
2FA, session controls and additional checks are used for sensitive administrative surfaces and flows where applicable.
Critical changes and operational actions can leave a trace so review and investigation remain possible.
Every PMS, Wi-Fi, printer or API integration is assessed before it becomes supported scope.
Data and analytics should be limited to the purpose, permissions and consent model of the specific deployment.
Deployments, health checks, backups and recovery procedures are treated as operational requirements rather than afterthoughts.
Which users exist, which scopes they need and which actions require stronger protection.
How data and operations are separated by account, property and role.
Credentials, endpoints, network dependencies, permissions and ownership for every external system.
Which data is necessary and which optional analytics or marketing signals require appropriate consent.
What happens when a dependency or integration is unavailable and which fallback procedure has been agreed.
What is protected, how recoverability is checked and who owns the operational process.
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.
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 policyWe can structure a technical discussion around roles, integrations, data flows, privacy requirements and deployment boundaries for your property.