Privacy preview

Privacy for the buyer flow.

This page describes the intended data posture for early access. It should be reviewed before public launch.

Data collected

The app may collect account email, name, checkout session IDs, Stripe customer IDs, license status, package access status, and early-access use-case notes.

Processors

The production stack is expected to use Clerk for authentication, Stripe for payments, Neon/Postgres for license records, Vercel for hosting, Resend for email, and PostHog or Plausible for analytics.

Purpose

Data is used to provide package access, support, billing, license records, private docs, and product feedback for the scheduler package.

Secrets

Do not send package tokens, Stripe secrets, or private keys through forms. Customer package credentials should be handled through account-gated setup instructions.

Contact

Privacy questions: hello@bravocalendar.com