Buildplan · by Austin Lowther
What I keep and why
Plain language version of Buildplan's data handling. If anything here is unclear or you want your session deleted, email hello@buildplan.austin.lowther.me.
Never sold. Never shared.
Your conversation, your Build Brief, and your purchase email don't go to advertisers, brokers, marketing partners, or any third party. There is no analytics pixel from a data-resale company watching you type. The third parties involved in the chat path are processors acting on my instructions and don't republish your content:
- Anthropic and OpenAI — the AI providers. The main chat runs on Claude (Anthropic) by default; the background “audit lenses” that check the brief for sycophantic agreement may run on GPT-class models (OpenAI). Both providers' published API policies say API calls are not used to train their models.
- Supabase — stores the database (your messages, state snapshots, Build Brief, code, and grant row).
- Vercel — runs the app and edge network.
- Upstash — rate-limit counters (per-IP attempt tracking; no chat content).
Not used to train AI models.
I send conversation text to Anthropic's API (main chat) and OpenAI's API (background audit lenses). Both providers' published policies are that API calls are not used to train their models. I also don't pipe your sessions into any other training pipeline. Your idea isn't becoming tomorrow's autocomplete for someone else's startup.
Reviewed by Austin to improve Buildplan.
I keep your sessions in my Supabase database so I can:
- Reload your conversation if you come back later in the 90-day window.
- Read through completed sessions in my operator dashboard to find places where Buildplan misread the founder, asked the wrong question, or shipped a brief that didn't hold up.
- Tune the prompts, the lens system, and the pre-export audit (the structural checks that catch sycophantic agreement before the brief locks).
This is one human (me) reading sessions to make the product better — not a team, not a model training run, not a public dataset. If that's a deal-breaker for what you want to share, see “Ask for deletion” below.
What's actually stored
- The email you used at Stripe checkout (so I can reach you if a token issue comes up).
- Your invite code and when you redeemed it.
- Every message in your chat with Buildplan, in order, with timestamps.
- The structured Build Brief state the system extracted from your messages, snapshotted as it evolved.
- The final Build Brief markdown when you accept the export.
- Per-session token counts and dollar cost (so I know what each session actually costs to run).
How long it's kept
Indefinitely, unless you ask me to delete it. I don't auto-purge sessions because re-reading older ones is part of how Buildplan gets better. The data lives in the Supabase project I run; nobody else has credentials.
Ask for deletion
Reply to your purchase email, or write to hello@buildplan.austin.lowther.me with “deletion request” in the subject. Include the email you used at checkout. I'll delete your session, your messages, your state snapshots, your Build Brief, and your tester code from the database within 7 days, and confirm by email. No forms, no friction, no hoops.
Changes to this policy
If I change anything that broadens what I keep or who can see it, I'll email everyone who's ever bought a Buildplan before the change takes effect, and you can ask for deletion under the old policy at that point. The page you're reading right now is version-controlled at github.com/why-not-labs/buildplan; you can see every change ever made to it.