DevImprint.

Privacy

Last updated 26 October 2026.

DevImprint measures AI-assisted commits in public repositories and ranks developers by them. That means it holds information about people who never signed up for it, and most of you are reading this because you found yourself on a list you did not ask to be on. This page is written on that assumption.

The short version: everything measured is already public, the ranking is built from commit history, and a small amount of extra information — roughly what country you are in, and the social links you published on your own profile — is held privately so that hiring conversations can be aimed sensibly. That extra information isnever published on this site. Nothing is ever sold. You can be removed at any time, without giving a reason, by writing to privacy@devimprint.com. If you opt in yourself — to be introduced to a hiring company, or to hear when profiles launch — that is the one part of DevImprint built on your consent rather than on public data, and its own section belowsays exactly what is held and how to undo it.

Who is responsible

The controller is Ronald Gardner, contactable atRonald@DevImprint.com. For requests about your own data, write toprivacy@devimprint.com.

The controller's postal address and the contact details for representatives in the EU and the UK will be added here after they are appointed.

Where the information comes from

Not from you. That is the most important thing on this page, and it is why this notice exists at all: data protection law requires that when information about someone is collected from somewhere other than the person themselves, they are told about it. There are two sources, and both are public.

  1. Public repository history. Commits, the tool signatures they carry, when they were made, the repositories they landed in, and the timezone offset git records alongside every commit date.
  2. Your public profile on the hosting provider. Your account name and avatar, and — where you filled them in — your location, company, bio, website, and the social accounts you added to your profile.

We do not read private repositories. We do not use your commit email address as a way to contact you. We do not request the profile scope that would give us your email address, so we do not have it. We do not scrape LinkedIn or any other site: a LinkedIn link is only held when you published it yourself in your hosting profile's own social accounts feature. The one exception to “not from you” is the opt-in list, where the information comes from you because you asked for something — it has its own section below.

If you opt in

Everything above is about information you never gave us. The opt-in list is the one exception, and it works the other way around: it starts with you, it holds only what you gave it, and this section is its notice. The lawful basis here is consent — Article 6(1)(a) — not the legitimate interests described above, and consent is only worth asking for if taking it back is as easy as giving it, so withdrawing is described below.

The opt-in page offers two separate choices, each its own box, neither pre-ticked, and at least one must be chosen. “Introduce me”: when a company hiring for AI-assisted engineering asks for people who are demonstrably doing that work, we may show it your public DevImprint record — your rank, your 30-day and lifetime AI-assisted commit counts, your tool mix and your top public repositories, all of which anyone can already see on this site — and pass on your email address, and nothing else. “Tell me when profiles launch”: you get one email when claimable profiles launch, and that is all that choice is for.

Here is everything the list holds, and all of it comes from you:

Just as important is what the list does not hold: no IP address, no browser details, and no tracking identifier of any kind. It is kept in its own database, separate from the pipeline data described above. And the rule that keeps the two apart, stated plainly: addresses that appear in public commit history are never used to contact anyone, and are never added to this list. The list contains only addresses people typed in and then confirmed. Until you confirm through the emailed link, nothing joins the list at all — a submission nobody confirms is deleted after seven days.

The form is protected by Cloudflare Turnstile, a check that tells people and bots apart. It does not present a visual puzzle, and we never receive or store your IP address or browser details from it. Cloudflare's own Turnstile privacy notice says that Turnstile processes only the data strictly necessary for that security function, and that it does not access, store or transmit user communications, form entries or other page inputs. The technical signals it does process — Cloudflare names the client IP address, a TLS fingerprint and the browser user-agent — are used solely to detect and block bots: Cloudflare states they are not used to identify, profile or target anyone, and that it does not have the ability to directly identify an individual from them.

Before any introduction happens, we check that you actually control the GitHub username you gave — submitting the form does not prove that, and the opt-in page says so. If an introduction has happened, you can ask us which company saw your record and when, and we will tell you.

How long the list keeps things. An entry nobody confirms: deleted after seven days. An entry that only asked for the launch email: deleted once that one email has gone. An “introduce me” entry: re-confirmed with you, or deleted, every twelve months. A confirmed entry: kept until you withdraw it.Withdrawing is the link in your confirmation email, or a note toprivacy@devimprint.com. Withdrawal deletes the entry immediately and keeps no record — not even the kind of removal record described above, because there is nothing left to keep you out of. It changes nothing about your place in the public ranking; that stays covered by Your rights below.

What is published, and what is not

This distinction is the centre of how DevImprint is built.

InformationOn the public site?
Account name, avatar, profile linkYes
The hosting provider's numeric account ID, for verified GitHub accountsYes, in the downloadable data — so a profile claim can be matched to the account you sign in with
Commit counts, rank, tools detected, activity dates, repository namesYes
Commit email addressNo — replaced with an opaque handle before publication
Country, world region, US stateNo
Commit timezone offsetNo
LinkedIn and other social linksNo
Company, bio, websiteNo

Location is only ever held at the level of a country. We do not hold your city, your address, or coordinates, and we do not send anything to a geocoding service. We do not infer your nationality, your residency, or your right to work anywhere, from your timezone or from anything else.

Why it is held

The lawful basis is legitimate interests. The interest is straightforward: hiring for AI-assisted engineering is currently done with take-home tests and interviews, and we think what someone has actually shipped in public is better evidence. The ranking cannot be built on consent, because a ranking that only contains people who agreed to be in it is not a ranking.

The location and social links exist for one purpose: to build a shortlist a company can act on, and to have a way to ask you whether you want to be introduced. Nobody is ever introduced to a company without agreeing to it first.

We assessed that balance in writing before collecting any of it, and we were candid with ourselves that it is a close call rather than an obvious one. The assembly of ninety thousand people into one ranked, filterable table is a bigger thing than any single fact in it, and no developer anticipated it when they pushed a commit. It holds because the extra information is never published, never sold, stops at country level, and because objecting ends it immediately. If you think we got that balance wrong in your case, you do not have to argue the point — see below.

Who else sees it

Nobody buys it. The data is not sold, licensed, rented or brokered, and there is no paid API serving it.

A company hiring for a role may be shown a shortlist that names you — but only after you have been asked and have said yes. If that has happened, you can ask us which company and when, and we will tell you.

The opt-in list adds one further recipient, described in its own section: for people who chose “introduce me”, the hiring company also receives the public record and the email address. Everything on that list is processed by Cloudflare — it hosts the site, holds the list's database, runs the bot check and delivers the confirmation email — on our instructions and for no other purpose.

Infrastructure providers process data on our behalf in the ordinary way: the cluster host, the object store holding pipeline artifacts, the CDN serving this site, and the mail provider handlingprivacy@devimprint.com. They act on our instructions and for no other purpose. Processing takes place outside the EU and the UK.

How long

Ranking data is kept while the repositories it came from remain public and in scope. Profile information — location, company, social links — is refreshed or deleted every twelve months; if we have not re-confirmed a field against your public profile within a year, we should not still be holding it.

If you ask to be removed, we keep a single record of your account name and the date, indefinitely, and nothing else. That record exists so that a later scan cannot quietly put you back.

The opt-in list is the exception to the record above: withdrawing from it deletes the entry outright and keeps no record at all. Its full retention rules are in If you opt in.

Your rights

You can ask for a copy of everything held about you, have it corrected, have it erased, restrict how it is used, or object to it entirely. There is no charge, and we answer within one month.

You do not have to give a reason for an objection, and we will not ask for one or try to change your mind. An objection is treated exactly like an erasure request.

We will not ask you for identity documents. Proving you control the account is enough — a message from the account, an email from an address shown on your public profile, or a verification string you put in a public gist.

How to make a request →

Removal takes effect on the next build and covers the leaderboard, your profile page, the downloadable document and the social card; the profile URL then returns a permanent “gone” response. The private information is deleted at the same time. Aggregate totals keep the commits with no identity attached to them.

If you are unhappy with how we handle a request, you can complain to a data protection supervisory authority — in the EU, the authority where you live or work.

Decisions made about you automatically

The ranking is computed automatically, but no decision with a legal or similarly significant effect is made about you by a machine. A shortlist is assembled by a person, and an introduction only happens if you agree to it.

Rank is a count of detectable AI-assisted commits and nothing more. It cannot see private work, or work where tool attribution was turned off, and it says nothing about your ability. The methodology pageis explicit about what the number cannot see.

Cookies and analytics

This site sets no tracking cookies, runs no advertising, and does not fingerprint visitors. Analytics, where used, are cookieless and aggregate. The opt-in form's bot check (Cloudflare Turnstile) loads from Cloudflare's own challenges origin and exists for spam protection only.

Changes

If what we hold or why changes materially, this page is updated and the date at the top changes with it. The interesting changes are the ones that add a category of information, and those will be described rather than folded silently into the text.

26 October 2026. A category of information was added: the opt-in list. People can now ask to be introduced to hiring companies, or to hear when claimable profiles launch, and this page has gained its first section about information collected from the person rather than from public history — If you opt in.