DevImprintRemove me, or ask what is held
Last updated 13 September 2026.
Two ways to do this, and they carry exactly the same weight. Email[email protected] with your username, or use the form below, which confirms it is you and records the request without anyone reading an inbox first.
You do not need a reason
If you want out, say so and you are out. We will not ask why, we will not reply with an argument for staying, and we will not send you anything afterwards. It is free, and there is no limit on asking.
Remove yourself
This asks you to publish a short public gist under your own GitHub account. That does two things at once: only you can publish under your account, and the sentence it contains is one you chose to write. You are not being asked to sign into anything here, or to grant this site any access to your account. You are leaving; being made to log in first would be a strange thing to require.
Publish this as a public gist
- Open gist.github.com, signed in as the account above.
- Name the file
devimprint-removal.txt. - Paste exactly this:
Create it as a public gist — a secret gist cannot be read, so it cannot be checked.
If you have no GitHub account here
Roughly half the identities on this site are not accounts at all. They come from commit history that yields only an address, and they are published as an opaque handle such as unresolved-a1b2c3d4e5f6, never as the address itself. If that is you, there is no account to publish a gist from — email[email protected] from the address that appears in the commits, and that is proof enough.
What else you can ask for
- Tell me what you hold
- Every field keyed to your account, where each came from, how long it is kept, and whether your name has ever gone to a company — and if it has, which company and on what date. This one discloses information, so it gets a closer look at who is asking than a removal does. Removing the wrong person is reversible; showing the wrong person someone's data is not.
- Something is wrong
- Usually misattribution: commits credited to you that are not yours, often through a shared or recycled commit address. Tell us which, and we will fix the mapping and say so publicly — a correction nobody sees is not a correction.
Proving it is you
The gist above is the whole check. If you would rather email, any one of these is enough: a message from the account itself, an email from an address shown on your public profile, or a short string we give you placed in a public gist or your profile bio.
Please do not send identity documents. We do not want them and will not accept them. Everything here is a public username attached to public commits, and demanding a passport to remove one would make the request itself the most sensitive thing in the exchange.
How long it takes
We answer within one month, usually much sooner. Removal from the public site takes effect at the next build, and we confirm once that build has shipped rather than when the change was made internally.
Your username then stays on a suppression list indefinitely, with the date and nothing else. That is the only way to be sure a later scan does not quietly put you back.
If we get it wrong
You can complain to a data protection supervisory authority — in the EU, the one where you live or work. Complaining does not require asking us first, though we would rather have the chance to fix it.