The registration details, filled in before they knock

How it works

Registration is set per booking, not once for the whole property. When you create or edit a stay, you switch it on for that guest.

The guest opens the link you already sent them. Near the top of their guide there is a clearly marked request to complete their registration. They tap it, fill the form on their phone, and submit. That is the whole thing — there is still no account, no password, and nothing to install.

You see the submissions on the booking in your app, and you can download them as a CSV file whenever you want.

The form asks the right questions

Most forms of this kind are written for one country and then translated. The result is a foreign guest being asked for a document series that their passport does not have, and getting stuck.

This one adapts to who is filling it in:

A Romanian ID card asks for the series and the CNP, and checks the CNP is thirteen digits before it will accept the form.

A foreign passport or residence permit does not ask for either, because they do not exist on those documents.

Everyone is asked for the things that always apply: full name, date of birth, place of birth, nationality, document type and number, and home address.

Or the guest can just photograph the document

Some guests would rather not type any of it, particularly on a phone, late. They can choose to photograph their document instead. They still give their name — with several guests on one booking you need to know which photo is whose — and the photograph goes straight into private storage.

You then read the details off the photo yourself, at a sensible hour, rather than standing in the doorway with someone’s passport and a pen.

What happens to the data

This is identity information, so it is treated as such rather than stored like a guide section.

It is encrypted. The document number, the CNP and the home address are encrypted before they are written to the database.

Photographs are private. They go into a private storage bucket that is never publicly readable, and they are shown to you through short-lived links that expire.

It deletes itself. Every submission carries a deletion date, worked out from check-out plus a retention period you choose. The default is thirty days. You can set anything from one day to a year. When the date passes, the record and its photographs are deleted without you doing anything.

It never leaves the system for convenience. Identity details are not sent away to be translated, are not fed into any analytics, and are not used to train anything.

What it does not do

This is worth being blunt about, because other tools in this space are sold on it.

It does not submit anything to SIT, or to any other public authority. It does not obtain or manage a SITUR code. It does not calculate, collect or pay tourist tax. It does not check whether a document is genuine, or confirm that the person is who they say they are. It does not issue invoices to your guests.

What it does is collect the details accurately, before arrival, keep them properly, hand them back to you in a file you can use, and then delete them on schedule. Your legal and tax obligations stay yours, and you should take your own advice on them.

What this costs

Guest registration is part of Pro, at €5 a month. That covers the adapting form, document photographs, encryption, automatic deletion and the CSV export, on every property on your account.