Ospikey is launching: automatic sending to SES.Hospedajes is being tested with the Spanish Ministry of the Interior and will be switched on soon.
Servers in the EU · Privacy by design · Encrypted data
Your guests' data, protected by design
An ID document is high-risk data. We protect it by design, not as an afterthought.
-
Servers in the EU Hetzner, Germany
-
Sensitive data encrypted Documents, signatures and SES credentials
-
Photos deleted after 30 days After departure, automatically
-
Two-step verification With an app or an email code
Four pillars
How we protect data
Every document, signature and piece of personal data goes through measures designed for high-risk data.
-
Servers in the EU
Servers and providers in the European Union
The service runs on Hetzner servers in Germany: database, files and backups. Automatic emails are sent with Brevo, in France. We do not transfer data outside the European Economic Area.
- Database, files and backups in Germany (Hetzner)
- Automatic emails with Brevo, in France
- Data processing agreement (Art. 28 GDPR) with every provider
-
Encryption
Sensitive data encrypted
Identity data, signatures, document photos and SES.Hospedajes credentials are stored encrypted with libsodium. Each type of data has its own key, kept outside the database.
- HTTPS-only connections, with HSTS
- Passwords stored with Argon2id
- No personal data in technical logs
-
Minimal data
Only the data needed, deleted automatically
We collect the data required by Royal Decree 933/2021. Document photos are optional: they are only requested if you turn the feature on, and they are deleted 30 days after departure.
- Guest data deleted 3 years after departure, as the law requires
- Photos stripped of metadata, GPS location included
- Document reading on the phone: the camera image never reaches our servers
-
Access
Two-step verification and permissions
Each team member has their own user, with a password and two-step verification: authenticator app, email code or backup codes. Anyone who hasn't turned on the app yet gets an email code for sensitive actions.
- Roles and properties: everyone sees only what you assign them
- Viewing a document or changing SES credentials asks for the code again
- Passwords checked against those already leaked
Behind the scenes
Customer separation and sending to the authorities
Today we send to SES.Hospedajes (Spain). This is how it works inside.
-
Each customer sees only their own data
PostgreSQLSeparation is built into the code and into the database itself (PostgreSQL Row Level Security), and automated tests check it.
- Row Level Security: the database itself filters each customer's rows
- Automated tests: check that one customer cannot see another's data
- Permissions per property: within your team, too, each person only sees the properties you assign
Separation in the code and in the database -
Sending to SES.Hospedajes
Real Decreto 933/2021Landlord code, web service user and password are stored encrypted: the password is never shown again and changing them requires two-step verification. If the Ministry's service does not respond, the sending is retried later.
- Encrypted credentials: landlord code, web service user and password
- Retries: after 1, 2, 5, 10 and 30 minutes, then hourly, without duplicates
- Receipt saved: batch and communication code stay with the booking
Spain · all plans -
Activity log
Audit logEvery sensitive action, such as opening a document photo or changing SES credentials, is kept in the audit log: who, what, when and from which IP. The log cannot be modified and contains no personal data.
- Who, what, when: user, action, date and IP address of every sensitive action
- Cannot be changed: the database rejects changes and deletions in the log
- No personal data: guests' data never ends up in the log
Each row linked to the previous one
Coming soon Portugal (SIBA) Italy (Alloggiati Web)
Our model
Your guests are your guests. We do not sell their data.
Ospikey lives on hosts' subscriptions. We do not use guest data for our own purposes, we do no profiling and we never pass it on to anyone for commercial purposes.
-
No advertising to guests
The check-in app has no banners, offers or promotional emails.
-
No data sharing
We share traveller data only with SES.Hospedajes, on your behalf, and with the providers that help us run the service.
-
No cookies on the website
The public website uses no cookies, analytics or advertising tools, and loads no third-party resources.
Clear roles
Who does what
Under the GDPR, you are the controller of your guests' data and Ospikey is the processor that handles it on your behalf.
-
Processor (Art. 28)
What Ospikey does
Processes your guests' data only on your instructions: the Terms of use and the settings you choose in the panel.
- Security: Protects the data with the measures on this page
- Deletion: Deletes photos and data when they are due
- Breaches: Notifies you without delay if there is a data breach
- Guests' requests: Helps you answer guests' requests
-
Controller
What is up to you
By law, you are the one who registers travellers: Ospikey helps, but the obligation remains yours.
- Personal users: Give each team member their own user: an account is not shared
- SES credentials: Do not share SES.Hospedajes credentials in chats or spreadsheets
- Sending results: Check the result of each sending in the panel
- Guests' requests: Answer guests' requests about their data; we help you
Frequently asked questions
Questions about security and GDPR
Retention, roles, encryption: answers to the most common questions.
Does Ospikey sign a data processing agreement?
Yes. The data processing agreement (Art. 28 GDPR) is section 20 of the Terms of use, which you accept when you sign up: there is nothing extra to sign.
What happens if SES.Hospedajes does not respond?
The sending stays in the queue and is retried later automatically. In the panel you see the status of each report and, if some data is wrong, which field to fix.
Are document photos kept forever?
No. They are optional, only requested if you turn the feature on, and deleted automatically 30 days after departure. Meanwhile they are encrypted and every time someone opens one it is logged.
Who on my team can see guest data?
Only people with the right permission, and only for the properties you assign them. Viewing documents also asks for the two-step verification code again.
Is reading the document with the camera safe?
Yes. Reading happens on the phone itself: the camera image is not sent to our servers. Only the fields are filled in, and the guest checks them before sending.
A guest asks to delete their data: what do I do?
The request is yours to handle, as the controller. Remember that Spanish law requires traveller data to be kept for 3 years: in the panel you can view and correct it, and we help you with the rest.
First year free for everyone who signs up by December 1, 2026.
Your guests' check-in, in safe hands
You can start in a few minutes. Have a question about security? Write to us.
- Servers in Germany (Hetzner)
- Second code for sensitive actions
- Document photos deleted after 30 days