What is and is not recorded
current as of the deploy you are reading, and a change to this list ships with the site| Item | State | Why |
|---|---|---|
| Page views | recorded | Which page was opened, the referrer, and coarse device and browser information. This is how the board knows which verdicts people come here for, which is what decides which tools get added next. |
| Interaction events | recorded | Clicks on links and controls, captured automatically and attached to the page they happened on. Text typed into a field is masked before it leaves the browser, and the only field on this site filters a table that is already in the page. |
| Session recordings | recorded | Analytics here includes session replay: a reconstruction of how a page was used, meaning clicks, scrolls, pointer movement, and which pages were opened in what order. Everything typed into a field is masked in the browser before it is sent, so text you enter is never captured. It exists so that a flow which breaks for someone can be watched back and fixed rather than guessed at. Recordings are processed by PostHog and deleted after 30 days. |
| Errors | recorded | When a page throws, the stack trace is sent so it can be fixed. Nothing about you is attached to it. |
| An account | none | There is nothing to sign up for. No email address is ever requested and no login exists. |
| Payments | none | The board and the JSON API are free. There is no payment processor and no card ever touches this site. |
| A profile about you | none | Analytics runs in identified-only mode and nothing on this site ever identifies you, so no person record is created. Events are grouped by page, not by visitor. |
| Sale or sharing of data | none | Nothing collected here is sold, brokered, or handed to an advertising network. There are no third-party ad or tracking scripts on any page. |
Four of the eight rows are an absence, and each is a thing this site chose not to build rather than a thing it has not got round to.
How it is served and switched off
Analytics are served from this domain rather than from a tracking host, so the requests are first-party. The processor is PostHog, on their EU and US cloud, acting on our instructions. Nothing is passed to anyone else.
If you would rather not be counted, any content blocker or the browser’s own Do Not Track setting will stop it, and nothing on the site breaks when it does. Every page is rendered on the server before any script runs. To have anything already recorded removed, write to hello@thecompound.tech.
What the verdicts hold
The verdicts themselves are computed from public GitHub API data about public repositories. No personal data about any maintainer is stored: the board keeps repository-level facts, meaning commit dates, release tags, counts and licences, and the owner name that forms part of the repository path.
The method page writes out how a verdict is reached, and the security page says what this site stores and who processes it.