IT, Data & Security

An independent audit against the AICPA's Trust Services Criteria — security, availability, processing integrity, confidentiality, and privacy. It's third-party proof that Juyo handles your data the way we say we do.

The globally recognized standard for information security management, in its latest 2022 revision. Certification means our approach to protecting your data has been independently verified against current best practice.

The EU's benchmark for data protection and privacy. Juyo is built to meet it, so your data — and your guests' data — is governed, protected, and handled with the rigor the regulation demands.

Your data stays in the EU, hosted on German infrastructure (Hetzner) and AWS EU regions — so where your data lives is never something you have to chase down for a security review or a group-level data policy. For Enterprise customers, in-region housing is possible.

The underlying infrastructure is independently certified: Hetzner is ISO 27001 certified and AWS holds both ISO 27001 and SOC compliance, so the foundation Juyo runs on is held to the same standards as the platform itself.

We target 99.98% uptime, with DDoS protection handled at the cloud-provider level, so the platform stays available and resilient even under attack.

All data is encrypted in transit using TLS 1.2+/1.3, and encrypted at rest across both databases and object storage. Protected whether it's moving or stored.

We deliberately hold as little sensitive data as possible: no payment card data ever touches the platform, guest personal details are excluded or masked, and reservation data is limited to operational attributes. The data-minimization approach behind how we meet GDPR.

You can request erasure of your data at any time, and system logs are retained under a defined 6–12 month policy, long enough for security and troubleshooting, no longer than needed.

Identity is managed through AWS Cognito with short-lived JWT sessions, and Juyo never stores your passwords. Authentication is handled by a dedicated, managed identity provider.

Role-based access control governs exactly who can see and do what across the platform, so access always maps to a person's actual role.

Permissions are enforced right down to the property, department, and data-model level: Property A users can't see Property B by default, and people only ever see the data relevant to their work.

Kassandra AI runs on an isolated analytics database — never your live production systems — so the AI layer can never reach or interfere with the data running your operation.

No AI-connected system is ever publicly exposed, closing off the most common route of attack against AI-enabled platforms.

Your data is never used to train our models or any third party's — a guarantee written into your Data Processing Agreement, not just a policy statement but a contractual commitment.

Development follows OWASP secure-coding practices, so protection against common vulnerabilities is built in from the start rather than patched later.

Every change runs through version control and security review before it ships, so nothing reaches production unchecked.

If an incident does occur, we follow a clear five-step response process: contain, assess, notify, run a full root-cause analysis, and remediate so it doesn't recur.