Privacy Policy

Effective Date: February 26, 2026

Contact: Booko App Inc., 325 Sharon Park Drive, Menlo Park, CA, Box 105 Unit D-5;support@bookoapp.com

Overview

Booko App Inc. ("Booko," "we," "us") provides dynamic-pricing and booking tools for service providers ("Providers"). This Policy explains what we collect, how we use it, who we share it with, and your choices. It applies to Providers and their end-customers ("Customers"). Where we process personal data on behalf of a Provider (e.g., booking data in Provider tools), we act as the Provider's processor. For our platform operations (security, billing, fraud, analytics), we act as an independent controller.

This Policy is US-centric and incorporates EU/UK concepts where relevant.

What We Collect

  • Provider account data: name, email, business profile (industry, services, phone, website, timezone, banner image), settings and policies.
  • Customer booking data: name, email, phone number, booked services, time, location if provided, pricing and payment status, SMS consent preferences; limited IP for security and fraud prevention.
  • Authentication: Google OAuth and email login links. We store the tokens necessary to operate accounts. We do not store passwords today. If we add password login later, we will store salted, hashed passwords only (never plaintext).
  • Payments: We do not store card numbers. Stripe processes payments for Providers via Stripe Connect. We store payment metadata (amounts, fees, status, Stripe IDs).
  • Calendar: If connected, we sync booking event details with the Provider's Google Calendar.
  • Files: Business banners and branding assets. These URLs may be public. Do not upload personal images without consent.
  • Diagnostics: Error/usage telemetry and sampled replay via Sentry to improve reliability. We minimize data and sample carefully. In EU/UK, replay/marketing pixels require consent.
  • Optional CRM: If enabled by a Provider, basic customer contact data and notes. Providers are responsible for lawful collection and content (no medical records or sensitive categories).
  • Enterprise integration data: Class schedules, booking counts, capacity, instructor names, and occupancy data ingested from Customer's connected booking and scheduling platforms on behalf of enterprise customers.
  • Member data from enterprise booking systems: Member ID, email, name, and phone received from enterprise customers' booking platforms. This data is collected on behalf of the enterprise customer, not directly from members.
  • Incentive and credit data: Incentive assignments, redemption records, credit fulfillment status, and promotional codes generated or synced through the enterprise platform.
  • ML/forecasting data: Historical demand patterns, feature vectors, model training datasets, and predicted occupancy used to power demand forecasting and dynamic pricing recommendations.

Representative sources in code: NextAuth auth and email login links; Prisma models for User/Business/Booking/Payment/StripeAccount; Stripe Connect and webhooks; Google OAuth/Calendar; Google Cloud Storage; Sentry instrumentation; optional Supabase CRM.

How We Use Data

  • Provide and improve the service (bookings, dynamic pricing, payments, calendar sync, notifications).
  • Security, abuse, and fraud prevention (e.g., IP checks, rate limiting).
  • Customer support and operational communications.
  • Marketing with consent (email/SMS). Providers using Booko's bulk email/SMS must have valid consent and honor unsubscribe/STOP requests.
  • Aggregated/anonymized analytics and, where permitted, retention of de-identified operational data to evaluate corporate transactions (e.g., merger, acquisition, sale) without disclosing personal data in a manner that constitutes a "sale" under applicable laws without required notices/choices.
  • Train per-organization demand forecasting and pricing models for enterprise customers.
  • Generate automated incentive recommendations based on predicted demand and occupancy.
  • Calculate and fulfill credits and rewards through integrated booking systems.
  • Provide enterprise analytics and reporting dashboards.
  • Use aggregated and de-identified data for internal improvement of AI/ML capabilities.

Lawful Bases (EU/UK)

  • Contract: performing bookings, payments, platform features.
  • Legitimate interests: security, fraud prevention, debugging, service analytics, improving reliability and quality.
  • Consent: marketing communications; non-essential cookies/replay/marketing pixels.

AI/ML and Automated Decision-Making

For enterprise customers using our dynamic pricing and demand forecasting services:

  • Booko trains demand forecasting models using enterprise customer data to provide the services. Model training scope and data isolation are governed by the applicable services agreement.
  • Customer data is not used to train third-party AI/ML models.
  • Aggregated and de-identified data (from which individual organizations and their end users cannot reasonably be identified) may be used for internal platform improvement.
  • Enterprise customers retain final authority over pricing and incentive decisions. All automated recommendations can be reviewed, modified, or overridden through the enterprise dashboard.
  • Booko maintains audit logs of automated pricing decisions, manual overrides, and model versions used.

Sharing and Sub-Processors

We share data with service providers acting on our behalf, including Stripe (payments), Google (OAuth/Calendar), Google Cloud Storage (assets), Sentry (error monitoring - may incidentally capture data in error logs), PostHog (product analytics - may capture usage events), Google Cloud Platform / Cloud Run (application hosting, ML model execution), email providers (Resend/SMTP), optional Supabase (CRM and database hosting), and hosting providers. We use appropriate transfer safeguards (e.g., Standard Contractual Clauses and the UK Addendum) when required.

Specific sub-processors engaged depend on the services used. Enterprise customers may request a current list of sub-processors applicable to their engagement by contacting founders@bookoapp.com.

Cookies and Similar Technologies

Essential

Authentication and CSRF cookies; local/session storage for booking and OAuth state.

Non-essential

Sentry Replay and any future marketing pixels (e.g., Meta Pixel) are used only with consent in applicable regions and can be controlled via our consent tools where provided.

Retention

  • Active accounts: retained while your account remains active.
  • After closure: account/profile for ~24 months; bookings/payments for ~7 years (tax/audit); operational logs/replay for ~30–90 days; marketing lists until you opt out or after ~24 months of inactivity.
  • We may de-identify data for analytics. These periods may change with notice and as required by law.
  • Enterprise customer data: retained for the term of the services agreement.
  • Upon enterprise termination: all customer data deleted within 30 days per the applicable DPA/MSA.
  • ML model artifacts: superseded model versions retained for up to 12 months after replacement, then deleted.
  • Aggregated/de-identified data: may be retained indefinitely for platform improvement and benchmarking.

Security

  • TLS in transit and cloud encryption at rest for databases and storage.
  • No payment card numbers stored by Booko (Stripe tokenization).
  • Access controls and least-privilege for staff.
  • If we add password login, passwords will be salted and hashed.

International Transfers

Primary processing is in the United States. When data moves outside your region, we use appropriate safeguards (e.g., SCCs and UK Addendum) as applicable.

Children's Privacy

Booko is not directed to children under 13. Accounts must be created by adults. In the edge case where a minor appointment is scheduled (e.g., child haircut), the Provider is responsible for obtaining appropriate parental/guardian consent and complying with applicable laws. Contact us if you believe a child provided data without appropriate consent.

SMS Communications

When you make a booking, we may ask for your consent to receive text message (SMS) confirmations and updates about your appointment. SMS consent is collected via a checkbox during the booking process and is stored per booking. You can opt-out of SMS communications at any time by:

  • Unchecking the SMS consent checkbox when making a booking
  • Replying "STOP" to any SMS message you receive
  • Contacting us at support@bookoapp.com

Standard message and data rates may apply. We use Twilio to send SMS messages. Your phone number and SMS consent are stored securely and only used to send booking-related communications.

Your Rights and Choices

  • Access, correction, deletion, and portability (subject to verification and legal limits).
  • Unsubscribe from marketing emails; SMS opt-out via STOP or by unchecking the consent checkbox during booking.
  • Manage non-essential cookies/tracking in supported regions via our consent tools.
  • Submit requests to support@bookoapp.com. We may verify identity and aim to respond within ~30–45 days.

State Addenda

We provide additional rights and disclosures for residents of CA/VA/CO/CT/UT and others as laws require (e.g., access, delete, correct, limit use of sensitive data, opt-out of sale/share/targeted advertising where applicable).

Changes and Contact

We may update this Policy; we'll post a "last updated" date and, for material changes, provide notice. Contact: support@bookoapp.com

This policy is general information and not legal advice.