Privacy

FlowWatch stores the minimum we need to run checks and bill for them.

What we store

• Your email address, from the magic-link sign-in.
• A marketing contact row: email, signup time, source, plan, and UTM parameters. It is not readable with the anon or user API keys.
• App URLs, verification tokens, and flow selectors.
• Test-account credentials, encrypted with libsodium before they are written. They are not logged.
• Run status, step results, timings, masked leak findings, and a screenshot path. Password fields are blurred before a screenshot is taken.
• Stripe customer and subscription ids. Card numbers for your FlowWatch subscription stay with Stripe.

What we do with it

We use the data to run checks, show your dashboard, email failure and recovery alerts, and export marketing contacts as CSV for an admin you designate. Signup emails are synced to ActiveCampaign for product email.

Shareable reports

A free-check report link shows step results and masked findings. It does not include credentials or screenshots. Anyone with the link can view that report.

Subprocessors

Supabase (auth, database, screenshot storage), Vercel (app hosting), Fly (the check worker, when you deploy it), Stripe (subscriptions), Resend (alert email), and ActiveCampaign (product email).

Contact

Privacy questions and abuse reports go to abuse@flowwatch.org.