Secure by default
Connections to BookBreathe are protected using HTTPS, passwords are securely hashed, and protected areas require authentication.
✓ Trust built into the booking flow
Security at BookBreathe.
Your business runs on trust. BookBreathe is built with sensible security measures designed to protect your business, your customers and the information you manage.
Security principles
Sensible protection, without the drama.
BookBreathe is not a generic CRM. It protects the specific journey your business depends on: enquiries, conversations, quotes, payments, files and bookings.
Business data stays separate
Each business works inside its own space, so enquiries, customers, quotes, messages and bookings stay attached to the business they belong to.
Server-side access control
Permissions are enforced by the application on the server, not simply by hiding information in the browser.
Private customer files
Files uploaded through BookBreathe are stored privately and delivered through controlled application access rather than exposed as public files.
Secure payments with Stripe
Payments are processed using Stripe and Stripe Connect. BookBreathe does not store customers' full payment card details.
Monitoring and maintenance
Logging, monitoring, backups and regular software updates are part of how BookBreathe is operated and maintained.
Data boundaries
Your business data is your business.
BookBreathe serves many businesses from the same platform, but each business operates within its own protected workspace. Access checks are performed on the server so users can only retrieve information they are authorised to see.
Enquiries and customersConnected to the business that received them.
Messages, quotes and bookingsKept with the booking journey they belong to.
Team accessValidated against the businesses a user is allowed to use.
Payments
Payments handled by Stripe.
BookBreathe uses Stripe and Stripe Connect to process customer payments. Card information is entered into Stripe's payment infrastructure, while BookBreathe receives the information needed to manage the booking, such as payment status, amount and transaction identifiers.
- BookBreathe does not store full card numbers.
- Payment status is managed from Stripe payment events.
- Booking and payment details stay connected in BookBreathe.
Customer information
Useful details, handled carefully.
BookBreathe may contain customer contact details, enquiry notes, messages, quote and booking information, payment references and uploaded files. That information is protected through authentication, authorisation and private storage.
- Customer uploads are not treated as public files.
- Protected pages require the right access.
- Customer workspaces use secure access routes.
Ongoing work
Security is an ongoing process.
No software can honestly promise to be completely free of bugs or vulnerabilities. BookBreathe keeps the platform and its dependencies maintained, monitors for issues, and investigates security problems when they are identified.
Production access is restrictedAccess to production systems should be limited to people who need it to operate BookBreathe.
Software is kept currentFrameworks, packages and infrastructure are reviewed and updated over time.
Issues are taken seriouslySecurity concerns are investigated and addressed when discovered.
Responsible disclosure
Found a security issue?
If you believe you've discovered a security vulnerability in BookBreathe, please tell us privately at security@bookbreathe.com so we can investigate it.
Please avoid publicly disclosing a suspected vulnerability until we've had a reasonable opportunity to investigate.
Ready when you are
Run your bookings with confidence.
Give every enquiry, quote, payment and booking a calmer place to move through.