For clients 2 min read

How we protect your personal data

Encryption, secure payments via Stripe, and access control - how we protect your data.

Updated 19.02.2026

You book studios, share your details, leave reviews - and you want to be sure that information is safe. Here is what we do to make that happen.

Encryption and secure connections

All communication with Booquela uses an encrypted HTTPS connection. This means no one can intercept data sent between your browser and our servers.

Your password is never stored in plain text - we only save an encrypted version. Even our technical team cannot see your password.

Payments - Stripe, not Booquela

Your card details never reach our servers. Payments are handled by Stripe - a certified payment processor compliant with the PCI DSS standard. When you enter your card number, you do so in Stripe's secure form, not ours.

Who can see your data

  • You - you have full access to your profile, booking history, and messages
  • The studio - sees only the information needed to fulfill a booking: your name and email address
  • Booquela team - accesses data only for technical support or dispute resolution

No one else - no other client, no platform visitor - can see your personal data.

Where we store data

Data is stored on servers within the European Union. We perform regular backups, and database access is restricted and monitored.

GDPR - your rights

Booquela complies with GDPR. You have the right to access, correct, delete, and transfer your data. You can learn more in the article about your GDPR rights.

What if you suspect a data breach?

If you suspect your data may have been compromised:

  1. Change your password immediately
  2. Check the activity on your account
  3. Email us at [email protected] - we will treat the matter as a priority

Enable two-factor authentication (2FA) in your account settings. It is an extra layer of protection that means even knowing your password is not enough to log in.

Was this article helpful?

What could we improve?

Thanks! Your feedback will help us improve this article.

This website uses cookies to provide the best quality of service. Privacy policy