Built with privacy first.
Resort Buggy protects your property's data and your guests' data with encryption in transit and at rest, role-based access, per-property data isolation, EU hosting, and encrypted nightly off-box backups.
Last updated: 2026-08-27
How we protect your data
Encryption in transit and at rest
All traffic is encrypted in transit. The production database is encrypted at rest, and nightly off-site backups are encrypted before they leave the server. Database access is restricted to the application.
Access controls
Authenticated access with strict role separation — guests, drivers, and admins each see only what their role allows. Guest access codes end automatically at checkout, after a set number of hours, or after one ride, and can be revoked instantly.
Multi-tenant isolation
Every query is scoped to your property. Your guests, drivers, rides and maps are never visible to another property.
Backup & recovery
Nightly database backups are copied off-box and kept for 30 days, so your operational history survives hardware failure or loss of the server. Backups are restore-tested.
Privacy
We collect the minimum needed to dispatch a buggy — and nothing more.
What we collect
- Guest name and room/villa identifier (provided by your property)
- Access codes for guests, drivers, and admins
- Pickup and dropoff selections, ride history
- GPS location while the app is actively in use
- The location at the moment a ride is called, on codes the resort marks Require location, checked against the property outline plus the resort’s allowed distance
- A push notification token, only if the user opts in
- Where a property checks its vehicles: a driver’s answers, photographs and odometer readings, under their name
- Where a property switches on Hold phone numbers: a telephone number for each staff member, and for a guest while she is in house — read by that property’s administrators, and a guest’s number erased at checkout
What we don't
- No payment or billing data from guests — rides are complimentary
- No guest or staff phone number is shown to a driver or to another guest
- No tracking across other apps or websites, no ad networks
- No analytics in the guest app — on the marketing site, analytics load only if you opt in
- Push notification payloads carry only ride status — never guest personal data
Where data lives
Your property's operational data — guests, rides, drivers, maps, messages — is hosted and processed on Hetzner Cloud in the European Union. A short list of named services outside the EU handles narrow supporting functions such as transactional email and map tiles; each is listed with its purpose and location in our DPA, and every transfer runs under Standard Contractual Clauses.
Export & deletion
An administrator downloads your property's whole data set from Settings › Your data, any time, as one archive. For deletion, email [email protected]. Details in our Privacy Policy.
Compliance & certifications
Here is exactly where we stand today.
Today
- GDPR-aligned practices: minimal collection, EU hosting, self-service export, deletion on request
- Encryption in transit and at rest, role-based access, per-property data isolation
- Access codes are never stored in plain text
- Nightly off-box backups, encrypted before they leave the server, 30-day retention, restore-tested
- Data Processing Agreement (DPA) with a public sub-processors list and downloadable PDF
What we don't have
- SOC 2 — we hold no SOC 2 report and no audit is under way.
- ISO 27001 — no certification.
If a certification is a hard requirement for your property, tell us early and we'll scope it with you.
Incident response
If you report a security concern, we acknowledge it within 24 hours.
If a breach affecting your data is confirmed, we notify you within 72 hours with what happened, what data was involved, and what we're doing about it.
Security contact: [email protected]
Responsible disclosure
Found a vulnerability? We want to hear about it. Email [email protected] with steps to reproduce, and we'll respond within 24 hours.
Safe harbor: we will not pursue legal action against researchers who test in good faith, avoid privacy violations and service disruption, and give us reasonable time to fix the issue before public disclosure.
Service status
Live service status is public at status.resortbuggy.com.
Have a security question?
Security questionnaires, procurement reviews, or anything we didn't cover here — we answer them personally.