Security and reliability
Your bookings, your guests' passports and your prices are trusted to Riverdesk. This is how they are protected.
Each company in its own space
Every row of data belongs to one cruise company, and the database itself refuses to show it to anyone else — not just the application. Automated tests try to cross that line on every table, every time.
Passports encrypted, kept only as long as needed
Passport numbers are encrypted before they are stored, never written to logs, events or messages to channels, and appear only in the passenger manifest. They are erased automatically 90 days after disembarkation.
Two-step sign-in and roles
Owners and finance staff sign in with a code from an authenticator app. Each person has a role, and every action is checked on the server, not only hidden on the screen.
Everything recorded
Every booking, change, payment and setting is written to an audit log with who did it and when — without personal data.
It cannot oversell
Each cabin is counted on every leg of the cruise in the same step as the booking, under locks, and a reconciliation check runs every night. If anything is ever wrong, sales stop on that departure and the office is told.
Prepared for bad days
Daily backups, a restore procedure that has been rehearsed, alerts when something goes wrong, and a nightly PDF of the next 14 days so the office can keep working even if the system is unreachable.
Data requests
An owner can export everything held about one guest, or erase it, in a few clicks — and the request itself is recorded.
Hosted in Europe
Riverdesk's database runs on Supabase in the EU (Ireland).