Skip to content
BookMyVenue

How BookMyVenue protects your data

Six tested promises about your bookings, records, access and money. No lock-in or exit fee.

Built-in safeguards

These rules apply across every screen and booking source. Automated tests check them.

No other business can see your bookings or your customers
Logged-in access keeps each business's bookings and customers separate.

Check: a test tries and fails to read another business's bookings.

Clinic records get extra protection
Clinical notes cannot be edited. Corrections link to the original. Access refusals are logged and retention rules apply.

Check: a BookMyVenue admin account must fail to open clinical notes.

Money movements can't be edited after the fact
Till payments and adjustments stay unchanged. Totals are calculated from those records.

Check: unapproved comps, discounts and refunds are refused.

Two bookings can't take the same slot
Only one simultaneous request can take a table or practitioner slot.

Check: eight concurrent requests produce one booking.

A message that didn't go out says so
Undelivered confirmations and reminders show as skipped with a reason.

Check: each failed message stores its reason.

Staff see their work, not your takings
Owner, manager, staff and read-only access is set per venue. Staff and read-only accounts cannot view money.

Check: accounts without money access receive a refusal.

Security and access you can account for

Audited operator access
BookMyVenue operators must give a reason before entering a venue console. The access and reason stay in the audit trail.
Sessions close behind staff
Login throttling, password-bound sessions and 90-day caps limit access. A new staff sign-in revokes older sessions.
Denied reads stay visible
Denied data reads are audited. Staff access fails closed when the system cannot identify the staff actor.
Verified nightly backups
The database is backed up and verified nightly. The backup sits on the same server, with no off-site copy. Audit logs, log redaction and a data-breach runbook support incident response.

Security documentation during procurement

Ask for written details on hosting, sub-processors, backups, retention, incidents, access, audit logs, export and deletion.

Time, API access and AI bookings

Booking, message and receipt times follow the venue's local time, including daylight-saving changes.

The public REST API covers venues, services, availability, bookings, tables, events and stays. It uses API keys, per-key limits and a published OpenAPI specification.

AI assistants can check availability and book through controlled agent keys. Each venue controls whether agent bookings are allowed.

Staff can set repeat weekly bookings for a client. Guests cannot create a series themselves.

Your data is yours, and you can take it with you

Export clients and reports to CSV any time. We can import a Fresha export. There is no lock-in, exit fee or sales commission, just one published monthly price.

BookMyVenue works out what you owe each person from the hours they clocked. Your team lodges payroll and moves the money.

Staff can set repeat weekly bookings. Guests book one visit at a time.

Everything BookMyVenue does is on the features page.

Trust & data questions

See it on your own bookings

Bring your services, staff and a few bookings.