Leisbase runs in data centres in the European Union, keeps every venue in its own database and gives you the tools to answer any guest’s data request yourself. This page says exactly how, without badges we don’t have.
The application, databases and encrypted backups run in Hetzner data centres in the EU; files such as chat attachments and exports are stored in Cloudflare R2 under EU jurisdiction. Cloudflare protects the platform in front, with bunny.net as a fallback route if a region has problems.
Each workspace has its own database, and its files are kept apart from other workspaces. Roles and permissions decide who sees what, down to single locations; exporting or erasing guest data, cancelling payments and monitoring functions need separate permissions.
Passwords of at least 12 characters, checked against known leaked passwords and stored only as bcrypt hashes. Two-factor authentication and passkeys, a notice for every new sign-in, an optional country restriction and a list of sessions you can end. Shared devices at the desk lock with a PIN.
Every connection runs over TLS. Keys and passwords of connected services, time tracker screenshots and documents are stored encrypted, and every backup is encrypted with AES-256.
Guests enter card details in the payment fields of Stripe, PayPal, Revolut or your other provider. Full card numbers are never processed on Leisbase servers, and the money goes straight to your own payment account.
Databases are backed up every hour and in full every night; files are backed up too. Nightly backups are kept as 14 daily, 8 weekly and 12 monthly copies in separate storage, and we monitor that every backup is fresh.
DDoS protection and a web application firewall stop attacks before they reach the servers, bot protection guards the sign-up, files sent to the chatbot or shared in the team chat are scanned for malware, and errors are monitored without sending personal data.
Export everything about one guest in a click, or erase them with a 14-day safety delay and an entry in the privacy log. Marketing consent is stored with its proof, and website statistics work without cookies or stored IP addresses.
Under the commercial terms of our AI providers, your data is not used to train their models. Claude or ChatGPT connected to your workspace only read until you switch on changes for the workspace, the connection and the role – and they can never delete anything.
Our Data Processing Agreement is public and part of every contract. It turns the measures on this page into obligations.
Read the Data Processing Agreement →You do. For your guests’ data you are the controller and we process it only on your instructions under the DPA. We never use it for our own purposes, never sell it and never combine it across venues.
Yes, at any time. The panel exports guests, bookings, orders and files. After the contract ends you still have a 30-day grace period to export before the workspace is deleted.
No. Card details go directly into the payment fields of your payment provider; our servers never receive full card numbers.
In data centres of Hetzner Online GmbH in the EU, with files in Cloudflare R2 under EU jurisdiction. Some services, such as sending emails or AI functions, are provided by sub-processors partly outside the EU; the DPA lists each one with its transfer basis.
Yes. Screenshots, activity tracking, location checks for the time clock and call recording are off until you switch them on, and in Austria they need a works agreement or your employees’ consent. The DPA explains your obligations.
Yes. Send it to support@leisbase.com and we answer it, together with the DPA and the list of sub-processors.
Please write to support@leisbase.com with a description and the steps to reproduce it. Do not access, change or delete other people’s data while testing. We confirm receipt, fix confirmed issues and tell you when they are fixed.