Encrypted transfer
Data moves between browser and service over HTTPS/TLS.
Back to all features
The host workspace is separated from the public guest form.
Security and privacy
Guest documents are not marketing data
Public check-in is separated from the host account, data transfer is encrypted and sensitive access is used only for required operations.
This page describes verifiable technical principles. It does not replace contractual or privacy documentation.
Specific safeguards
Fewer security slogans, more clear answers about what happens to data.
UbyPort credentials
Credentials are encrypted at rest and decrypted server-side only for the operation that needs them.
Public guest link
Guests cannot access the host account or other reservations.
Legal information
Binding processing terms and contacts belong in the privacy documentation.
Separate access and explicit rules
Security relies on concrete technical and operational controls.
Public and signed-in areas
Public check-in is separate from the authenticated app.
Sensitive server operations
Access is used server-side only for an operation the host starts or configures.
Binding documentation
Details are in the Privacy Policy and Terms of Service.
Frequently asked questions
For security documentation needed in your own review, send us a specific request.
Can a guest see other reservations?
No. Public check-in is separated from the signed-in application.
How is UbyPort access handled?
Access is used server-side for an operation started or configured by the accommodation provider. Detailed documentation is available on request.
Where can I find the legal information?
In the Privacy Policy and Terms of Service. The security page supplements those documents; it does not replace them.
Need documents for your own review?
Tell us what you are assessing. We will answer specifically.
Try for free