Trust and security
SunDibs tracks claims, furniture and usage, never identity. Here is exactly what that means, where the data lives, and who else touches it.
What we never do
- No cameras, no pressure pads, no occupancy sensors pointed at guests.
- No stored location. A guest's phone may be asked whether it is at the pool when confirming arrival; the answer is used once and never written down. Declining never blocks a guest.
- No advertising identifiers, no third-party cookies in the guest app.
- No selling or sharing of guest data. Ever.
How the platform is protected
- Every table carries row-level security scoped to a single venue or organisation. Staff at one property cannot read another property's data, by construction rather than by convention.
- The audit trail is append-only. Records of pins, arrivals, charges, deposits and settings changes cannot be edited or deleted, by us or by a property.
- Every marker gateway holds its own secret, rotatable from the dashboard. A compromised unit affects one pool, not a whole hotel group.
- Hotel system credentials and payment keys live in the server environment only. They are never sent to a browser and never appear in the dashboard.
- Guest verification is rate limited and answers uniformly, so nobody can use it to work out who is staying at a property.
Where the data lives
The database, file storage and backups run in the European Union. Guest contact details are optional, kept only for the length of a stay's reminders, and deleted on request from the guest app or by a property's manager.
Who else processes data
Last updated 14 February 2026.
- Cloudflare: hosting and edge delivery of the app, EU region. Receives the network requests needed to serve pages, and no stored guest record.
- Supabase: database, authentication and file storage, EU region. Holds the pin records, venue data and any optional guest contact detail.
- Stripe: payments, deposits and licence billing. Receives the payment detail and the amount, and no lounger or room information.
- Mews: only when a property connects its hotel system, for room charges and stay checks. Receives the stay reference and the charge.
- Twilio: text-message arrival reminders, only when a guest gives a number. Receives the phone number and the reminder text, and no room number, surname or location.
- Resend: email arrival reminders and account email. Receives the email address and the reminder text, and no room number, surname or location.
Reminders go to Resend and Twilio directly from our servers. No other party sits in that path. Ask us at privacy@sundibs.com for a data processing agreement covering any of the above.
Data processing agreement
Properties receive a data processing agreement covering the above as part of the contract. Ask us at privacy@sundibs.com and we will send the current version.
Reporting something
Security reports go to security@sundibs.com. We reply within two working days.
See also our privacy notice, our terms and our accessibility statement.