Start free →
🌐 Country / languageEnglish — grabtheslot.comDeutsch — grabtheslot.deMagyar — grabit.hu
Security & data protection

How we protect your customers’ data

GrabTheSlot holds your customers’ names, phone numbers and bookings. This page describes what actually protects that data today — measured facts, not promises.

Last updated: 19 October 2026

What protects your data today

Access & identity

  • Passwords of at least 10 characters, stored as bcrypt hashes — never in readable form.
  • Two-factor authentication (authenticator app) for any user; the owner can make it mandatory for their team. One-time recovery codes, and account lockout after repeated wrong codes.
  • “Sign out of all other devices” also revokes the two-factor trust of remembered devices.
  • Three roles (owner · staff · delegated), with layered permission checks on every action.
  • Two-factor authentication is mandatory for platform administrators. Support access to your account is only possible in a time-limited (8-hour), logged way, and stays visible in the interface throughout.

Separated accounts (tenant isolation)

  • Every database operation runs on the server and is filtered by your business’s identifier — another business’s data cannot be reached from your account.
  • The public keys used in the browser cannot read the data tables: row-level access rules and revoked database privileges protect them.
  • Before every release an automated check runs that fails the release if a database change would open new access.
  • Before every release an automated check walks every server endpoint and fails the release if any of them lacks a permission check; intentionally public endpoints (such as the booking page) are on a reviewed list with a stated reason.

Data & location

  • The database and the application server run in the EU, in Germany (Hetzner, Nuremberg), operated by us — no external database provider has access to the data.
  • The database, uploaded files and backups are kept on encrypted (AES-256) storage.
  • All traffic is TLS-encrypted (HSTS enabled).
  • Payment-provider keys and two-factor secrets are additionally encrypted at application level with AES-256-GCM.
  • We store no card data: card payments are handled by Paddle, and booking deposits by your own Barion account.

Backup & recovery

  • Continuous database backup: changes can be restored to the minute; on top of that, a full daily backup and a database copy every 6 hours.
  • Backups are copied within minutes to another provider’s EU-jurisdiction storage — so a server or account outage does not take the backup with it. There they are locked and kept for 89 days: they cannot be deleted or overwritten even from our server.
  • Backups are encrypted before upload (age); the decryption keys are kept separately from the storage.
  • A monthly automated test restore verifies that the backup can actually be restored.
  • If a release fails the post-deployment check, the system automatically rolls back to the previous working version.

Operations & updates

  • Firewall, automatic banning after repeated failed logins, key-only server access.
  • Automatic operating-system security updates and a weekly automated security check that alerts on deviations.
  • Weekly automated vulnerability checks of software dependencies; the release tooling is pinned to fixed, verified versions.
  • A newly published dependency version can only enter the system after waiting at least one day, and automated update proposals wait several days — compromised releases are usually caught within that time.
  • Type checks and automated tests run before every release — no release if they fail.
  • Critical server-side errors send an automatic alert to the operator.

Data protection (GDPR)

  • The data processing agreement (DPA) is part of the service, not a paid extra.
  • We name every sub-processor (see below) and announce any new sub-processor 30 days in advance.
  • You can export your data in a machine-readable format; deleting the account ends in anonymisation after a 30-day grace period.
  • Technical logs are deleted automatically after their retention period.

When something goes wrong: incident notice

If we become aware of a security incident affecting your data, we notify you by email within 24 hours at the latest with the information available, and keep you updated. That is early enough for you — as the controller — to notify your supervisory authority within the 72 hours required by the GDPR.

Sub-processors

These providers process data on our behalf. The list is the same as in the data processing agreement — it is generated from a single source.

Sub-processorPurposeData locationTransfer basis
Hetzner Online GmbHServer infrastructure: the application, our self-operated database and authentication, and encrypted storage of uploaded files (logos, images); a separate server runs our self-hosted, cookie-free visit statisticsEU (Germany, Nuremberg — application, database, file storage; Germany, Falkenstein — statistics)EEA
Cloudflare, Inc.Provider-independent, encrypted backup (continuous and daily copies of the entire database and uploaded files, for disaster recovery; the provider cannot decrypt the content) and DNS serviceEU-jurisdiction storage (R2); US-based providerEU-U.S. Data Privacy Framework (DPF)
GitHub, Inc.Automated release pipeline (build, tests, deployment) and running database schema changes over an encrypted channel; it stores no personal dataUSEU-U.S. Data Privacy Framework (DPF)
Resend Inc.Sending transactional emails (confirmations, reminders, cancellations, account notices)USEU-U.S. Data Privacy Framework (DPF)
Twilio Inc.Delivering SMS and WhatsApp reminders (phone number + reminder text)
(only if the Controller enables the SMS or WhatsApp reminder add-on)
USEU-U.S. Data Privacy Framework (DPF) + Binding Corporate Rules (BCR)
Zoho Corporation B.V.Support email mailbox (receiving the messages you send us)EU (the provider’s EU data centre)EEA

NIS2

The NIS2 Directive is not expected to apply directly to GrabTheSlot. If your organisation is subject to NIS2, we support your supply-chain security obligations: 24-hour incident notice, named sub-processors, and cooperation in audits. We do not claim NIS2 certification or compliance.

Vulnerability disclosure

If you have found a security issue, please report it to us directly — not publicly. [email protected]

What we commit to

  • We acknowledge your report within 2 business days.
  • We keep you informed about the fix.
  • We take no legal action over good-faith research that follows the rules below.
  • If you wish, we credit you after the fix.

What we ask

  • Do not access, modify or delete other users’ data.
  • Do not run automated scans that load the service, and do not attempt denial of service.
  • Give us reasonable time to fix the issue before disclosing anything publicly.

Related documents

Security contact

Security reports, vendor questionnaires or questions about the DPA:

[email protected]