privacy

— what loworbit stores about you —

• if you sign in (clerk)

  your email address. your name and avatar if you provided them via your sign-in method (google, github, etc). a session cookie scoped to .loworbit.ai so the same session works across the hub and every prototype subdomain. you can sign out at any time from the user menu.

• if you submit feedback

  the message body you typed, the page path you submitted from, optionally an email address you provided, and your clerk user id if you were signed in. screenshots only if you explicitly attached one.

• page views (posthog)

  page paths, anonymized session data, basic device info. no recordings. used for understanding which prototypes get traffic. set posthog opt-out via your browser's do-not-track and it will be respected.

• errors (sentry, when wired)

  stack traces and the page path that triggered the error. not the page contents. used to find bugs.

— what loworbit doesn't store —

• passwords

  clerk handles authentication. your password (if you have one) never touches loworbit's servers.

• payment info

  loworbit doesn't take payments. nothing here costs money.

• advertising / tracking

  no ad networks, no marketing pixels, no third-party tracking scripts. posthog is the only analytics tool.

• sensitive personal data

  loworbit isn't designed to receive medical, financial, government-regulated, or otherwise sensitive personal data. don't paste it into prototypes or feedback.

— where data lives —

each of those services has their own privacy policy. they are operating as data processors on behalf of loworbit; none of them receive a custom data feed from loworbit beyond what their normal product collects to function.

— per-prototype storage —

different prototypes do different things with what you give them. some save nothing. some store contributions to a shared corpus. some upload documents to anthropic for analysis and discard them after the session.

check the data: line under the try-it button on each prototype's /tools/[slug] page. if a prototype hasn't declared one yet, assume it stores at least your inputs and any signed-in identity.

— retention —

loworbit retains data indefinitely by default. retired prototypes' databases stay queryable for archival and writeup purposes; their github repos are archived (not deleted) when the prototype is taken down. feedback you submit is kept indefinitely so dks can revisit and act on patterns over time.

if you want any of that to not be true for your data, email and ask.

— how to ask for deletion —

email danielkinneyspears@gmail.com with the email address you used to sign in (or the path / timestamp of the feedback you want pulled). dks responds personally. expect a couple of days, not minutes.

for the supabase / clerk records, deletion is real deletion, not soft. for posthog and sentry, deletion runs through their respective tools and may take longer to propagate.

— changes to this page —

tracked in the open. this file lives at app/privacy/page.tsx in the hub repo. if you want to see what changed and when, read the git history. material changes will also show up in the public /log.