Privacy Policy
How Guidestination collects, uses, shares, and safeguards personal data when you browse, book, and manage activities.
Guidestination ("we," "our," or "us") operates a marketplace that connects customers with independent activity providers. This Privacy Policy explains what personal data we collect, how we use and share it, how long we keep it, and the choices available to you.
We collect the data needed to run customer bookings and provider operations across Guidestination and Provider-Portal.
- Account and identity data, such as email, sign-in credentials, name, phone (if provided), profile image URL, and preferred language.
- Booking and service data, such as selected activity, schedule, participant count, contact details, and optional special requests.
- Provider operations data, such as business profile details, activity setup data, payout setup status, and support request records.
- Technical preference data, such as language/currency/country selections and limited referral attribution state.
We store and retrieve data using managed database and file storage systems with policy-based access controls and server-side safeguards.
- Application records (for example customers, bookings, provider profiles, and provisional booking metadata) are stored in Supabase PostgreSQL tables.
- Uploaded files (for example profile/media assets and provider documents) are stored in storage buckets with access policies and signed upload URLs for protected flows.
- Data access follows authenticated and service-role authorization patterns, including row-level security and provider-ownership checks on protected endpoints.
- Limited browser storage (localStorage/sessionStorage/cookies) is used for locale preferences, checkout continuity, and referral state.
- Payment card details are processed by Stripe Checkout; full card numbers are not stored in our application databases.
We use collected data only for platform operation, service delivery, and compliance needs.
- Authenticate accounts, maintain secure sessions, and support account recovery.
- Process bookings, send confirmations and updates, and enable customer/provider support communication.
- Run provider operations, including optional read-only external calendar synchronization.
- Support payouts, reconciliation, fraud prevention, audit, and legal compliance workflows.
- Measure and improve platform quality using limited de-identified analytics.
We do not sell personal data and we do not share personal data with advertisers or unrelated third parties for their own marketing.
When you make a booking, we share only the data needed for service delivery with the selected activity provider:
- Phone number
- Email address
- Additional booking instructions you provide
We use limited de-identified analytics (such as QR scans and page activity) to operate, improve, and measure platform performance, including internal ranking of activity providers and referral partners.
If you choose OAuth sign-in, we access only identity data required to authenticate your account and provide core account features.
- Data accessed: unique account ID, email address, basic profile details, profile photo URL, and locale/language
- Data use: authentication, account creation and sign-in, profile prefill, localization, and fraud/security protection
- Scope limits: this sign-in flow does not request access to calendar, inbox email, cloud storage, or contacts
- Advertising: this data is not used for advertising
If a provider chooses to connect an external calendar, we use OAuth to sync availability in read-only mode.
- Permission scope: read-only calendar access
- Data accessed: calendar event metadata (event ID, title/summary, status, start date/time, end date/time)
- Connection data stored: access token, refresh token, token expiry, and granted scope, only as needed to maintain authorized sync
- Usage limits: we sync availability only and do not create, edit, or delete events in the provider calendar
When you request account deletion, your booking-related personal data and uploaded media are permanently deleted, subject to limited retention requirements described below.
After deletion, we may retain minimal record-level identifiers where reasonably required for system integrity, fraud prevention, audit, dispute handling, or legal compliance.
For privacy questions or requests, contact:
Last Updated: February 24, 2026