Removal & Correction Policy

The short version

Any developer may request removal of their account from a comparable set, a case study, or any other published page on this site. We honour it promptly and we do not ask why. Email scottbphone12@gmail.com with the GitHub username and the page it appears on.

What you can ask for

• Removal — take my account off that page entirely.
• Correction — a figure attributed to me is wrong; fix it or take it down.
• Exclusion going forward — do not include my account in future comparable sets or published pages at all. We keep a standing exclusion list and we honour it.
• Access — tell me what you hold that relates to me.

How to ask

Email scottbphone12@gmail.com with:

• the GitHub username concerned;
• the page URL where it appears (or “everywhere”);
• whether you want removal, correction, or standing exclusion.

You do not need to explain yourself. If the request comes from an address or account we can reasonably associate with the username, that is enough; where we cannot, we may ask for a simple proof of control such as a gist or a profile-bio token — solely to stop a third party from removing someone else's data.

How fast

We aim to acknowledge within 3 business days and to complete removal within 7 business days. Removal means the content comes off the live site; we also request recrawl so search engines drop the cached copy, though the timing of that is up to the search engine and not something we control.

Our standing rules about naming other people

These apply whether or not anyone has complained:

• A named third party's valuation is never published without that person's consent. We do not publish a dollar figure, valuation range, or worth ranking for a named individual or organisation unless the subject has agreed to it. The case studies on this site cover accounts belonging to the site's own operator, published with consent.
• Comparable sets cite public factual metrics only. Contribution counts, star counts, repository counts, follower counts — figures GitHub already publishes publicly. No valuation, no worth ranking, and no authenticity, fraud, or integrity judgment is ever attached to a named third party.
• Findings about incentivized attention, fork behaviour, or automation are only ever published about a consenting subject — in practice, our own accounts. We do not publish that class of finding about someone who did not ask to be appraised.
• We do not publish private data. Only data GitHub and public package registries already make public.

Rights this reflects

This policy is written to give effect to the kinds of rights described in the EU and UK GDPR (access, rectification, erasure, objection, portability) and the California Consumer Privacy Act (know, delete, correct, opt out of sale — and we do not sell personal data at all). We honour these as a matter of policy, for everyone, regardless of where you live. We do not claim any specific compliance certification, accreditation, or third-party audit under those or any other regime, and nothing here should be read as such a claim.

If we get it wrong

If you asked for removal and the content is still up after 7 business days, email again and say so — it is an error on our side, not a decision. If you disagree with how we handled a request, tell us; we would rather fix it than argue about it.