Skip to content

SECURITY

Your property details.
Within your borders.

Access is controlled by the PostgreSQL server and database. No one outside your organisation will see your guests, stays or billing.

Visualisation of a fictional hotel property

Database isolation

PostgreSQL's enforced RLS policy limits each query to an organisation and an property.

MFA and secure sessions

Administrator TOTP code, HttpOnly sessions, Origin and CSRF protection.

Roles and scope

Staff see only their assigned tasks; guests see only their own stays.

Audit log

Each change has an author, time, and request ID.

Idempotence

Repeated request, webhook or payment will not have double effect.

Backups and Restores

Database backups verified through restoration tests before every update.

Safe offline workflows

Offline queue compares versions and does not overwrite newer decisions.

Encrypted keys

Secrets of payment and mail operators are encrypted and never returned to the browser.

Consents and documents

Versioned terms and conditions, record of acceptance when booking and handling data requests.

HONEST

No invented
certificates.

We do not declare certifications that the system has not passed. The availability of WCAG 2.2 AA is a design goal, and legal and tax compliance is verified by the property operator with a lawyer, data protection officer and accountant.

  • DPIA and data retention checklist to be completed by the operator
  • Fiscalization and KSeF require separate acceptance testing
Visualization of a hotel apartment

Data questions
and safety?

Select the topic "Personal data and privacy" in the form - we will respond specifically.

Screenshots show the Polish version of the product. Choosing a website language does not change the language of the panels or apps.