privacy policy

we store your account email (via our sign-in provider, Clerk), the usage logs you choose to upload, and your subscription state (via Stripe). the analysis itself is plain arithmetic that runs on our servers — your logs are never sent to any AI model, advertising network, or data broker. there is no third-party analytics or tracking code in the app.

token·flow is built by ogbuilds, a uk-based studio. this policy is written under uk data-protection law (uk gdpr).

account data. sign-in is handled by Clerk, our authentication provider. Clerk holds your email address and sign-in credentials; our database references your account only by an opaque user id.

the usage logs you upload. when you upload a usage CSV, we parse and store its rows — provider, model, token counts, costs, timestamps, and any prompt excerpts or extra fields present in the file — so your dashboard, trends, and recommendations can be computed and shown to you. upload only data you are permitted to share; if your logs contain prompt text you'd rather not store, strip those columns first — the analysis works without them.

billing data. payments are processed by Stripe. we store your Stripe customer id, plan, and subscription status — never your card details, which go directly to Stripe.

operational data. we use request ip addresses transiently to rate-limit uploads and protect the service. we run no third-party analytics, no advertising trackers, and no session recording.

token·flow's analysis is deterministic arithmetic — grouping, deduplication, and cost math over the rows you uploaded. no model calls are made with your data. your logs are not used to train anything, are not shared with or sold to anyone, and are only ever shown back to you.

we rely on a small set of infrastructure providers, each processing only what their role requires: Clerk (authentication), Stripe (payments), Neon (database hosting), and Vercel (application hosting, which like any web host processes standard request metadata such as ip addresses to serve and protect the site).

we process your account, uploaded logs, and billing data to perform our contract with you (providing the service you signed up for), and operational data such as rate-limiting on the basis of our legitimate interest in keeping the service secure and available.

your data is kept while your account is active. you can erase it yourself at any time from settings → delete account: that permanently removes your uploaded logs, recommendations, and billing records from token·flow, and cancels any active subscription. because sign-in is a single ogbuilds account shared across our other products, deleting your token·flow data does not delete that ogbuilds login itself — sign out afterwards, or contact us via the studio link below if you want the login removed too. we keep a minimal, non-identifying audit record of the deletion (an opaque user id, a timestamp, and how many records were removed) to evidence that the erasure took place.

under uk gdpr you can access, correct, export, and delete the personal data we hold about you, and object to or restrict its processing. reach out via ogbuilds and we’ll respond. you also have the right to complain to the ico.

our providers (Clerk, Stripe, Neon, Vercel) are us-based and may process data outside the uk/eea under appropriate safeguards, such as the uk addendum to the eu standard contractual clauses.

the only cookies set are the session cookies our authentication provider needs to keep you signed in. there are no advertising or tracking cookies.

token·flow is a developer tool and is not directed at children under 13. we do not knowingly collect data from children.

traffic is encrypted in transit over https, data at rest is encrypted by our database and hosting providers, and uploads are rate-limited and size-capped.

if this policy changes, we’ll update the date above and, for material changes, note it on this page.

questions? reach out via ogbuilds, the studio behind token·flow.