You hold your guests' passports. We take that seriously.
Hospitality software handles identity documents, card payments and home addresses. Vyrobel treats data minimisation as an architectural decision rather than a policy page. ⚠️ Vyrobel has not launched yet. This page describes what is built and tested, and says plainly where something is not done.
Two-factor authentication
Available on operator, owner and platform-admin accounts, and mandatory for platform admins. ⚠️ It is opt-in per person: there is no way for an administrator to require it of a role, including roles that take payments or change payout details. Guest accounts have no 2FA. Recovery codes, trusted devices, and a real list of your active sessions — you can end all other sessions at once, after re-entering your password.
Roles that actually restrict
An owner sees their own units, never another owner’s — a row-level scope that fails closed rather than falling open, and an owner account cannot leave the owner portal. An accountant sees the ledger, not the guest list.
Audit trail on money
Refunds, payments, rate-plan changes and payout transitions are logged with who did what and when — a record you can hand to an owner or an auditor. ⚠️ Three things are not in it yet: per-unit rate overrides, owner payout preferences, and granting a role to a person.
Encryption and isolation
Sensitive fields are encrypted with the application key — guest email and phone, owner tax and bank details, identity documents, two-factor secrets. The application forces HTTPS and marks its cookies secure. Tenant isolation is structural: a global scope on every read, and a guard that refuses a write with no tenant context. ⚠️ Hosting is not chosen yet, so there is no data-residency commitment to give you — we would rather publish one before launch than imply it now.
Data minimisation
We collect what a stay requires and no more. Identity documents are encrypted and hard-deleted 30 days after checkout by a scheduled job — a fixed default applied everywhere, not a per-jurisdiction legal period.
Guest anonymisation
Erasure is real and thorough: personal details are cleared while the financial record survives, so your reports stay accurate. ⚠️ It runs on request — yours or the guest’s — not on a timer. There is no automatic retention sweep yet.
Your rights as a controller
You are the data controller for your guests; we're the processor. That means we act on your instruction, and we never use your guests’ data for anything but running your business. ⚠️ The paperwork that should come with that — the written contract governing how we handle your guests’ data, and the list of every company we rely on to run the service — is not written yet. We would rather tell you that than let you assume otherwise.
Corrections are self-service in every realm, and a guest can delete their own account from the guest portal. ⚠️ Owners and operators ask us to erase, and a guest cannot yet export their own data — two gaps we are closing.
Leaving is a feature
Export in open formats — CSV, PDF and XLSX — with no support request. Cancelling makes your workspace read-only at the end of the period you paid for. ⚠️ Deleting a whole account, and the schedule that would follow it, is not built: today you ask us and we do it by hand.
We'd rather you stayed because the product earns it.
Planning a security review?
Ask us what exists today. Right now the honest answer is: this page, and the engineers’ account of what is built. The formal documents a procurement team will ask for are not written, and we will tell you which are ready rather than send you one that is not.
An ordinary visit sets 2 cookies
— vyrobel-session and XSRF-TOKEN.
2 more appear only if you ask for them.
All 4 are strictly necessary, and there
are no analytics, no marketing and no third-party cookies at all —
nothing here tracks you across other sites.
So there is nothing on this notice to switch off today.
We record your answer anyway, because it binds us if that ever changes.
What each one is for
Every cookie this site sets
Cookie
What it does
How long
When it is set
vyrobel-session
Keeps your session — the sign-in that follows you between pages, and the basket of a booking in progress.
2 hours
On your first page view.
XSRF-TOKEN
Protects every form on the site from cross-site request forgery. Without it a form you submit here could be forged from another site.
2 hours
On your first page view.
vy_td
Remembers a device you chose to trust, so two-factor authentication does not ask again on it.
30 days
Only if you tick “trust this device” at a two-factor prompt. Never otherwise.
vy_cookie_choice
Remembers the answer you gave on this notice, so it is not shown again and so the answer can be honoured.