Yes. The Free plan is a zero-subscription option for one independent professional. Current limits, included capabilities and any transaction fees come from the live plan configuration on the plans page.

Subscription prices, plan limits, platform transaction fees and available add-ons are published from the live billing configuration on the plans page. Payment-provider processing fees are separate and depend on the connected account, country, method and contract.

No binding on our standard monthly plans. Choose up to 6 months free. Each free month is followed by one paid commitment month. The exact timeline, earliest cancellation date and minimum committed base cost are shown before checkout; enterprise arrangements can have separately agreed terms.

Yes. Provider processing fees are charged under the connected payment account and are separate from any Booking Bible subscription or platform transaction fee. Exact rates vary by provider, market, payment method and merchant contract.

AI availability depends on the active plan, enabled module, role permissions and platform rollout controls. The admin AI surface is Studio Manager; write-capable tools are permission-gated, audited and designed with reversal metadata or an explicit irreversible marker.

Contact billing@bookingbible.com with your organization and requirements. Any eligibility or commercial offer is confirmed in writing rather than promised as a blanket public discount.

Use the live comparison on the plans page for current limits and included modules. Enterprise is the route for requirements such as multi-organization operations, franchise controls, negotiated integrations or a separately scoped commercial arrangement.

Booking Bible has file-import paths for common source systems, but coverage depends on the fields present in your actual exports. Start with the matching migration page, then validate a representative file before confirming scope.

Timing is confirmed after reviewing source access, data volume and quality, payment-method portability, reconciliation work and the cutover model. A public estimate is not a substitute for reviewing the real account.

That depends on identity and payment-provider constraints. Profiles and supported history can be mapped, while password setup, consent refresh or payment-method re-entry may be required. The migration plan states these client actions before cutover.

Yes. Contact migrate@bookingbible.com for a source assessment. The level of assistance, responsibilities, timing and any cost are confirmed after the source and data set have been reviewed.

We identify the gap, decide whether an approved API or manual mapping is feasible, and agree what must remain as an archive or be rebuilt. Booking Bible does not promise scraping access or completeness where the source does not provide it.

A parallel or read-only reference period can be included when the source contract and operating workflow allow it. The correct duration and system of record must be agreed for each data type to avoid duplicate bookings or charges.

The primary database, authentication and storage data plane is configured for EU residency. Some optional services—such as video delivery, AI inference and consent-gated analytics—can involve documented cross-border processing covered through the relevant contractual safeguards. See the Data Processing Agreement and sub-processor list.

Yes. The current platform DPA is published at /dpa and its acceptance is versioned. Venue-specific controller responsibilities and any negotiated terms should be reviewed during onboarding.

Booking Bible includes data-subject request workflows for access, correction, export, objection and deletion. Requests still require identity verification and may retain records where a legal exception or financial-retention duty applies.

Yes. The current public list is at /legal/sub-processors, with purpose and processing context. Contractual notice and objection mechanics are governed by the DPA.

Consent grants and withdrawals are recorded with version and evidence fields. Marketing and analytics flows consult the relevant consent and suppression gates; a venue remains responsible for choosing the lawful basis and wording appropriate to its processing.

Booking Bible maintains an incident-response and breach-assessment process. The 72-hour GDPR deadline applies to a controller notifying the supervisory authority when the legal threshold is met; affected venues receive the information needed to meet their own duties.

Stripe Connect is the complete production payment rail today. Other provider-aware code paths are not live venue offerings and are not presented as supported processors until their implementation, approval and rollout are complete.

MobilePay can be presented through eligible Stripe accounts and checkout contexts. Availability depends on the connected account, country, currency, device and Stripe configuration; normal provider and any applicable platform fees still apply.

Booking Bible supports recurring passes and course installment plans. Available collection methods and payment methods depend on the product configuration, connected provider and rollout controls.

Refunds use the canonical payment record and the payment intent’s stored account context, then reverse the relevant platform fee and financial records where applicable. Final timing and availability still depend on the live provider and the underlying charge state.

Yes. Stripe Connect onboarding and account-aware charge routing are implemented. The exact charge model, payout timing, payment methods and fee treatment depend on the venue account and platform configuration.

The point-of-sale workflow can record approved offline tender types, including cash, against venue sales. Card-present capabilities require compatible Stripe Terminal hardware, account eligibility and market support.

Yes. The current platform exposes 478 REST route handlers with OpenAPI documentation, 28 embeddable widget surfaces and a read-only MCP endpoint. Access is venue-scoped and depends on plan, permissions and granted API scopes.

The catalog currently contains 458 active event keys. Outbound deliveries are HMAC-SHA256 signed, include stable delivery metadata and retry non-success responses according to the delivery policy. Consumers should verify signatures and deduplicate.

Booking Bible provides scoped REST APIs and signed webhooks for approved custom workflows. That developer foundation does not imply an off-the-shelf connector to every automation service; a provider-specific connection must be scoped and accepted before it is presented as available.

Compatible calendar clients can subscribe to eligible read-only iCalendar feeds. Feed contents and viewer access depend on the schedule and booking workflow; this should not be read as a universal two-way calendar sync.

Booking Bible includes consent-gated campaign tools plus export, API and webhook surfaces. It does not advertise a generally available native CRM or email-platform connector today; any custom connection requires a separately confirmed scope.

Accountant-oriented exports are the generally available path today. Booking Bible does not advertise a generally available native accounting connector or two-way accounting sync; provider-specific pilots must be confirmed separately.

No. Booking Bible maintains security and compliance controls and readiness evidence, but it does not claim a completed SOC 2 Type II examination. Ask for the current evidence package and known gaps during due diligence.

TOTP-based MFA is available. The privileged-account enforcement path is currently staged and should not be represented as universally mandatory; the current control posture and rollout status can be shared during security review.

Booking Bible maintains documented database, storage and external-system recovery procedures with backup verification and restore drills. Current recovery objectives depend on provider features such as PITR and are not presented as guaranteed until their production configuration has been verified.

There is a coordinated disclosure process, not a public paid-bounty promise. Send security reports to security@bookingbible.com and consult /.well-known/security.txt for the current contact and policy.

Tenant-scoped data paths combine Postgres Row Level Security, organization identifiers, role and permission checks, and scoped API keys. Security tests and audits verify positive and negative tenant-boundary cases; no control is described as eliminating all risk by itself.

The application uses a per-request nonce Content Security Policy, strict source directives, output sanitization and secure response headers. CSP rollout and monitoring are configuration-controlled so production enforcement can be verified without overstating every environment.

The published service-level page states the current acknowledgement targets by severity and business-hours policy. A target is not the same as a measured uptime or guaranteed resolution time.

General support is available through support@bookingbible.com and the in-product reporting paths. Any phone, dedicated-channel or on-call arrangement must be included in the applicable order form or support agreement.

The public service-level objectives and severity targets are at /sla. They are operating targets; a contractually binding service credit or dedicated support commitment exists only where stated in an executed agreement.

Use the in-product report path when available or the public form at /support. Include the affected venue, time, route, expected result and safe reproduction steps; never send passwords, secret keys or full payment details.

The public incident ledger is at /status. It shows declared active incidents and history but does not invent uptime percentages when an authoritative external monitor is not connected.

Send operational incidents to support@bookingbible.com; send suspected vulnerabilities or data exposure to security@bookingbible.com. State the impact and time window clearly without including secrets or sensitive personal data.

Booking Bible currently publishes 9 supported solution paths across yoga, fitness, dance, martial arts, spas, salons, clinics, event venues and franchises. Each page explains the relevant workflows and availability caveats.

A venue has a primary business type and can enable compatible modules and workflows. Multi-brand and multi-location structures are supported on eligible plans, but adjacent vertical behavior should be validated rather than assumed from a label alone.

Spa configurations can use appointments, rooms, resources, staff availability, services, products, packages and client records. Sensitive health or contraindication data requires an appropriate lawful basis, restricted access and the relevant enabled workflow.

Salon configurations can use appointment scheduling, staff and resource calendars, client profiles, products, point of sale, packages and retention reporting. Exact station, formula, patch-test and media workflows depend on enabled modules and configuration.

Event-venue configurations can combine room and resource availability, private events, clients, deposits, products, documents and operational schedules. Booking Bible does not replace legal capacity, fire-safety or venue-compliance controls.

The platform includes group and franchise concepts, venue-level overrides, cross-venue controls and reporting foundations. Availability and commercial scope depend on the enterprise plan, enabled modules and the intended ownership model.

Start with the nearest supported operating model and describe the differences during discovery. We only publish a new vertical when its terminology, booking rules and required workflows are actually supported; adjacent businesses are assessed case by case.