What we store and why.
Plain english, no legalese — we only collect the minimum needed to build an operating view and deliver the notifications you ask for.
What we collect
- Public GitHub repository data— issues, pull requests, commits, reviews, workflow runs. Fetched via GitHub's public API using the same access any unauthenticated visitor would have.
- An email address, only if you opt in to “notify me when my operating view is ready.” We store it on the sync run you subscribed to and delete our copy when we send the email or when you ask us to.
- Sync & analysis metadata — the status of each run, what phases completed, how long they took. No content of your private repos is ever fetched or stored — we never authenticate as you against private resources.
- IP addresses, transiently, in an in-memory rate-limit counter. Not persisted to a database and not associated with your identity.
- A session cookie if you sign in. It stores a signed workspace token so we can look up your account on each request. No third-party ad or analytics cookies today.
Who we share it with
- GitHub— we read from the public API. They see our service's IP, nothing about you.
- Resend— delivers the “notify me when ready” email if you opt in. They receive only the address you gave us plus the email body.
- Render — hosts the app, API, and Postgres database. Subject to their infrastructure security terms.
- Nobody else. No ad networks, no analytics aggregators, no data brokers.
How long we keep it
Public-repo analytics are kept as long as the repo is indexed here; deleting a repo (via the intake UI or an emailed request) wipes every associated row, including any captured notification email. Rate-limit counters live for one window (an hour at most) and then expire.
How to delete your data
If you captured an email for a notification and changed your mind, or you want your repo removed from the public gallery, email chasewnorton@gmail.comand we'll delete the associated rows. We don't have a self-serve delete surface today; that's on the roadmap.
Changes
If we collect something new or change how we use existing data, we'll update this page before the change takes effect. This is a research prototype — expect the policy to get more specific, not less.