← Back to Dashboard

OpenBook legal

Terms of use

Customer and business-facing terms for using OpenBook booking links and dashboards.

Last updated 4 August 2026

These terms describe the conditions for using OpenBook. The booking or reservation contract, cancellation policy, deposit requirement, refund position, and service delivery are set by the business taking the booking.

OpenBook is not legal, medical, tax, financial, or professional advice. Businesses are responsible for their own service descriptions, prices, policies, tax settings, privacy notices, and legal compliance.

Customers should check the service, staff, location, date, time, price, amount due today, and booking policy before confirming.

Private manage links and customer portal links are bearer-style links. Do not share them publicly or with anyone who should not be able to view or manage the booking.

A booking may require payment, owner approval, quote review, or a later balance link depending on the business settings.

Business responsibilities

Businesses must keep service details, availability, staff permissions, deposits, tax labels, cancellation policies, privacy notices, cookie information, and email/calendar/payment settings accurate.

Businesses are responsible for responding to customer deletion, access, correction, refund, cancellation, reschedule, complaint, and dispute requests.

Businesses connecting professional messaging channels must have authority to use those assets, give required notices, respect provider consent and reply-window rules, and must not try to connect personal inboxes.

If outbound business webhooks are enabled, businesses must use safe HTTPS endpoints and avoid sending customer data to untrusted systems.

Platform limits

OpenBook may block abusive traffic, reject unsafe webhook URLs, disable demo providers in production, and require live provider configuration before launch.

If shared booking rate-limit storage is unavailable, OpenBook applies a bounded per-instance fallback and alerts the operator; production deployments must connect those degradation alerts before public launch.

Calendar sync, email delivery, payments, refunds, and webhooks depend on third-party providers and their availability.