Summary

• We never sell your data. We don't run ads. We don't share with brokers.
• We never see your password. It's hashed in your browser with argon2id before submission.
• We never see your card details. Stripe handles everything; we only get a token + receipt.
• You can export everything we have on you from your dashboard settings at any time.
• You can delete your account from the same place. It's gone within 30 days, including DB backups.

1. What we collect

Account data: email address (required), display name (optional), country / timezone derived from your browser headers, a password hash if you set one.

Order data: the services you bought, the plan terms, the order status, the Stripe Payment Intent ID. We do not store your card number, CVC, or full card name — Stripe does.

Support data: any messages you send us through tickets or chat, plus the resolution status. Retained for 24 months for fraud and dispute defense, then deleted.

Telemetry: anonymous page-load and error data via our own server logs. We do not use Google Analytics, Facebook Pixel, TikTok Pixel, Hotjar, or any third-party tracker on production marketing pages.

2. Why we collect it

• To deliver the seat you bought. Email is how we send your access details.
• To monitor seat health. If a seat breaks we need to know which order to replace.
• To prevent fraud. Repeated chargebacks, stolen cards, and abuse are matched against historical activity.
• To meet our legal obligations. Tax records, invoice copies, and dispute evidence have to be retained.

3. Where it lives

Our database is hosted with Neon (PostgreSQL) in the EU and US-East regions. Backups are encrypted at rest with AES-256-GCM. Master credentials for shared accounts are encrypted with a per-record envelope key that lives in a separate KMS — even a leaked DB dump would not yield usable credentials.

4. Who else sees it

Three categories of vendor only:

• Stripe — payments, refunds, chargeback handling. They see card data; we don't.
• Postmark — transactional email (order receipts, password resets, seat replacements). They see your email + the message body.
• Neon — the database. They see what's in it but can't decrypt seat credentials.

Stripe is a controller for the card data it sees, Postmark a processor, Neon a processor. We have a DPA with each.

5. Your rights

Whichever jurisdiction's law applies, you have at minimum these rights and we'll honor them within 30 days:

• Access. See everything we have on you. Export in JSON.
• Rectification. Correct any wrong details. Email address change requires a fresh verification.
• Deletion. Remove your account and all associated data, subject to legal retention (tax, anti-fraud).
• Portability. Take your data and leave. We'll never lock it in.
• Objection. Object to specific processing. We'll evaluate and respond in writing.

6. Cookies

We use one persistent cookie (seathub-session) for keeping you signed in. We use localStorage for your theme, currency, hero language, and one-time toast dismissals. We do not use any tracking cookies. See our cookie policy for the full list.

7. International transfers

If you're in the EEA/UK, your data may transfer to the US for processing (Stripe's primary infrastructure is US-based). Those transfers rely on Standard Contractual Clauses and Stripe's own DPF certification.

8. Children

SeatHub is not directed at children under 16. We don't knowingly collect data from them. If you're a parent and you believe we have data on your child, email privacy@seathub.app and we'll delete it.

9. Changes

If we make a meaningful change we will email every active customer at least 14 days before it takes effect. Cosmetic edits (spelling, formatting) we won't bother you about.

10. Contact

Email privacy@seathub.app. We reply within one business day. If you're in the EU and unhappy with our response, you can complain to your national supervisory authority.