Throng beta reservations
Privacy Policy
This policy explains how Throng handles information collected through the beta reservation flow, including the card setup step handled by Stripe.
Last updated: May 26, 2026
Information we collect
When you reserve a Throng beta spot, we collect the information you choose to provide in the reservation flow. This can include your name, email address, phone number, country, city or region, device preferences, intended use, referral source, feedback preferences, and the consent confirmations you check before continuing.
If you continue to Stripe, we may store Stripe identifiers connected to your reservation, such as a Stripe customer ID, Checkout Session ID, SetupIntent ID, payment method ID, and limited payment method metadata that Stripe makes available to us. We do not receive or store your full card number, CVC, or full bank account details.
How we use it
We use reservation information to manage the Throng beta list, understand demand, prioritize compatibility and shipping regions, communicate with you about beta availability, coordinate secure payment setup through Stripe, prevent abuse or fraud, troubleshoot the reservation flow, and comply with legal or operational obligations.
Saving a payment method does not mean you have completed a purchase. We currently use it to help confirm serious beta interest. We will contact you before requesting the beta payment and before finalizing any purchase terms.
Stripe and payment data
Stripe processes card setup and payment method storage for us. If you enter payment details, you provide them directly to Stripe through Stripe Checkout. Stripe handles sensitive card data under its own security and privacy practices.
We use Stripe-provided identifiers so we can match your saved payment method setup to your Throng reservation. We do not use those identifiers to charge you without the future confirmation described in the reservation flow.
Storage and service providers
Reservation records are stored in our Supabase-backed database. We may also use hosting, analytics, email, security, payment, and support providers to run the site and manage beta communications.
We share information with service providers only as needed for them to provide services to Throng, support the reservation process, protect the site, or meet legal requirements.
Retention
We keep reservation information for as long as reasonably needed to manage the beta program, maintain records of your consents, resolve disputes, comply with legal obligations, and operate or improve Throng.
If the beta program changes or ends, we may keep limited records where appropriate, such as proof of consent, security logs, or information needed for accounting, legal, or fraud-prevention reasons.
Security
We use reasonable administrative and technical safeguards for the reservation system, including relying on Stripe for sensitive payment data and Supabase for database storage. No internet service can guarantee perfect security.
Please avoid sending sensitive information that we do not ask for, such as full card numbers, passwords, government IDs, or private account credentials.
Your choices
You can choose not to complete a reservation, not to continue to Stripe, or not to provide optional information. You can also ask us to update, remove, or limit use of your reservation information, subject to reasonable verification and any records we need to keep for legal, security, or operational reasons.
For removal or privacy requests, contact us through the email address provided in your reservation communications.
Children
Throng beta reservations are not intended for children under 13. We do not knowingly collect reservation information from children under 13. If you believe a child under 13 provided information to us, contact us through the email address provided in your reservation communications.
Changes
We may update this Privacy Policy as the Throng beta program, site, payment flow, or service providers change. If changes are material to the reservation program, we will take reasonable steps to make the updated policy available before relying on the new terms.