Privacy
What this site collects, why, and what happens when you leave. Last updated 2026-08-15.
What this covers
This policy covers ledgerstack.dev: the marketing site and the live demo you can sign up for. It does not cover applications other people build with the LedgerStack code — each of those has its own operator, and this page speaks only for this one.
What we collect, and why
Account data. When you sign up: your email address, an optional display name, and a password handled by Supabase Auth — we store a hash, never the password. Sign in with Google and we receive your email and name from Google instead.
Ledger and usage data. The demo exists to show a credit ledger working, so it records exactly what a ledger records: credits granted, held, spent and released on your account, with timestamps. If you join an organization, entries against its wallet record that your account acted — that attribution is the feature.
Prompts. Text you submit to the demo run is processed to demonstrate the metered endpoint and is never stored — the runs table records cost and lifecycle, not content. Whether a prompt leaves the server depends on which provider the demo is configured with: the kit's default is a built-in stub that answers locally and sends nothing to any AI vendor; if a real provider is ever configured, prompts are sent to it to generate the response, under that provider's terms. Treat the demo as a demo either way.
Payments. The demo runs Stripe in test mode: no real charges, no real card data. If you buy the kit itself, payment is processed entirely by Polar (polar.sh), the checkout provider linked from the pricing page — card numbers never touch our servers.
What we do not collect. There are no analytics trackers, no advertising pixels, and no third-party scripts on this site. The only cookies are the session cookies that keep you signed in.
Who touches the data
Three infrastructure providers process data on our behalf: Supabase (authentication and the Postgres database), Vercel (hosting), and Stripe (test-mode billing on the demo). Emails the demo sends — confirmation links, sign-in links — go through Supabase's email service. Nobody else. We do not sell data, share it with advertisers, or use it for anything beyond running this site.
Retention, and the honest part about deletion
Most sites promise total erasure. This one is a financial ledger, so the honest answer has two halves. Your identity — email, name, profile — can be deleted on request. Ledger entries are append-only by design and are retained as the financial record; after erasure they carry an internal identifier that no longer maps to any person. This is the same retention-versus-erasure line the product documents for its buyers, applied to ourselves.
Demo accounts and their data may also be cleared as part of operating a public demo. Do not keep anything on the demo you care about.
Your rights
Email claygeo6@gmail.com to ask what we hold about you, to correct it, or to delete your account as described above. No forms, no dark patterns — one email.
Changes
If this policy changes, the date above changes with it, and the git history of the codebase — which buyers receive — is the audit trail.