Privacy Policy

Effective Date: November 14, 2026

1. Information We Collect

DepositBooking collects only the information necessary to operate deposit-protected appointment scheduling for independent service providers and their clients:

  • Provider Account Data: When a service provider signs in with Google OAuth, we store their display name, email address, public booking slug, timezone, service definitions, weekly opening hours, and self-configured payment instructions (payment link, handle, or QR code image).
  • Google OAuth Credentials: We store the provider's Google OAuth refresh token in an isolated, server-only database table (provider_secrets) accessible strictly by backend server processes.
  • Client Booking Data: When a client reserves an appointment slot, we collect their name, email address, optional phone number, and any optional payment proof screenshot uploaded to confirm their deposit. Payment proof screenshots are stored in a private storage bucket accessible only via short-lived signed URLs.

2. How We Use Google User Data

DepositBooking requests two Google Calendar scopes to automate availability and appointment confirmation:

  • Google Calendar Free/Busy (https://www.googleapis.com/auth/calendar.freebusy): Used for real-time, read-only lookup of busy time intervals on the provider's primary calendar so clients only see genuinely available slots. We do not read, store, or display private event titles, attendees, or descriptions from existing calendar events.
  • Google Calendar Events (https://www.googleapis.com/auth/calendar.events): Used solely to insert a new appointment event onto the provider's primary calendar when the provider explicitly clicks Confirm on a client's deposit booking.

3. Google API Services User Data Policy (Limited Use Disclosure)

DepositBooking's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, Google user data obtained through Google OAuth is never sold to third parties, never used for serving or targeting advertising, and never used to train generalized artificial intelligence or machine learning (AI/ML) models.

4. Direct Client Deposits & Third-Party Services

DepositBooking does not collect or process client deposit payments. Clients pay deposits directly to the provider's external payment account (such as Venmo, PayPal, CashApp, Stripe Payment Link, PayNow, or DuitNow). We do not collect or store client credit card numbers or bank account credentials.

To operate the software service, we rely on the following trusted infrastructure providers solely to store data or deliver transactional functionality:

  • Supabase: Database hosting, authentication, and private file storage for payment proof screenshots and QR codes.
  • Resend: Delivery of transactional booking notifications and calendar .ics confirmations.
  • Dodo Payments: Merchant of Record for provider software subscriptions ($9/month Pro plan after the 5-booking free tier).

5. Data Retention & Revoking Access

Providers may revoke DepositBooking's access to their Google account at any time from their Google Account Permissions page. Upon revocation, DepositBooking can no longer read your calendar availability or insert calendar events.

We retain booking records and uploaded screenshots only as long as needed to support active scheduling history and account operation. To request full deletion of your provider profile, bookings, and stored tokens, please reach out through our support contact listed on your billing receipt or provider dashboard.