Skip to content

Legal

Privacy Notice

Last updated July 17, 2026

This Privacy Notice explains how JPR Studios handles information through this website, the booking flow, and customer account features.

It describes the application behavior that is currently implemented and does not state a fixed data-retention period.

  • A booking request includes your name, email address, requested studio, date and time, duration, guest count, selected add-ons, and any promo code or booking notes you submit.
  • The application stores the booking rules shown at checkout and the time those rules were accepted.
  • Staff-managed customer records can also contain a phone number, company, referral source, social links, tags, notes, pricing rules, and promotion eligibility when that information is provided or added for operations.
  • Customer account access uses your email address and an authentication session provided by Supabase.

Payment is completed on a Stripe-hosted checkout page rather than in a card-entry form operated by this application.

The application sends Stripe your email address, booking amount, session description, and booking-related metadata needed to connect the payment to the booking.

The application stores booking amounts, status, payment and checkout references, refund status, and related operational timestamps.

  • The booking flow can record attribution values supplied in utm_source, utm_medium, utm_campaign, utm_content, utm_term, and ref URL parameters.
  • Vercel Analytics is used for page-view and application-event analytics, with tokenized booking, confirmation, and customer-booking URLs excluded by the application.
  • Google Analytics and Google Ads page or conversion events can be enabled through the deployment configuration, with the same sensitive booking URLs excluded by the application.
  • Vercel BotID checks booking-creation requests for automated traffic.
  • Application and provider logs can contain routes, timestamps, booking references, delivery references, calendar event references, recipient addresses, and error details used to operate and troubleshoot the service.
  • Information is used to calculate a quote, check availability, create and manage a booking, connect a payment, and provide customer account access.
  • Information is used to send booking messages, create or update calendar events, process cancellation or rescheduling actions, and support operational review.
  • Analytics and attribution data are used to understand site use and booking-flow activity.
  • Security signals and operational logs are used to protect the booking flow, diagnose failures, and reconcile booking, payment, email, and calendar activity.
  • Supabase provides customer authentication and session handling.
  • Stripe provides hosted payment checkout and payment processing.
  • Resend receives recipient and booking-message content to deliver transactional email.
  • Google Calendar receives the customer name and email, session schedule, guest count, selected add-ons, and submitted booking notes when a booking event is created or updated.
  • Vercel hosts the application and provides analytics and bot-protection services used by the site.
  • Google can receive analytics or advertising events when the corresponding deployment settings are enabled.

Booking, customer, payment-status, policy-acceptance, calendar, email-job, and operational records remain in their respective systems unless they are removed through an administrative or approved provider process.

The application does not currently implement an automatic deletion schedule for booking or customer records.

Questions or requests about information associated with your email address can be sent to team@justpushrecord.com.

Customer cancellation and rescheduling require a Supabase customer session whose normalized email address matches the booking email address.

Public manage links show a restricted booking summary and do not authorize cancellation or rescheduling by themselves.