Terms

Booking requests

• You must provide accurate booking information and use an email address you are authorized to access.
• The displayed quote is calculated from the selected studio, schedule, duration, guest count, add-ons, and any applicable promo code or customer pricing rule.
• Submitting a booking request creates a pending booking and redirects you to Stripe Checkout when the request passes availability and validation checks.
• A pending booking is not confirmed until payment completion is processed and the booking status is confirmed.
• The application can reject a request when the slot is unavailable, the quote is invalid, automated traffic is detected, or a live calendar check cannot be completed.

Payment

• Stripe processes payment through its hosted checkout service in United States dollars.
• The application records the payment and checkout references, amounts, status, and any refund-related status needed to operate and reconcile the booking.
• A checkout session can expire before payment is completed, after which the pending booking can be marked expired.

Booking policies

• The booking flow displays the currently configured cancellation and rescheduling rules before opening Stripe Checkout.
• You must select each displayed rule before continuing, and the application stores the accepted rule text with an acceptance timestamp.
• Cancellation, rescheduling, and refund outcomes depend on the configured rules, booking status, session timing, and payment state shown in the applicable flow.
• These Terms do not add a refund, cancellation, or rescheduling promise beyond the rules displayed for the booking.

Customer accounts and booking links

• Customer account access uses an emailed Supabase sign-in link and an authenticated session.
• Cancellation and rescheduling require an authenticated account whose normalized email address matches the booking email address.
• A public manage link is a restricted convenience link and does not authorize cancellation or rescheduling by itself.
• You are responsible for protecting access to your email account, authenticated session, and booking links.

Email and calendar activity

• The application can send transactional email for booking confirmation, cancellation, rescheduling, and customer account access.
• A confirmed booking can create a Google Calendar event containing the booking schedule and operational booking details and can invite the booking email address.
• Email and calendar actions are processed through third-party services and can fail or be delayed.

Acceptable use

• You may not attempt to access another customer's booking or account.
• You may not interfere with availability, payment, authentication, analytics, bot-protection, calendar, or other operational systems used by the service.
• You may not submit false, unlawful, or unauthorized booking information.

Third-party services

Questions