AILeadSpace

Privacy

What we keep

No password, no fingerprint, no address. A vote and a handle, and that is most of it.

01

There is no password to lose

Signing in goes through X, GitHub or LinkedIn, and the credential never touches this site. What comes back is a handle, a display name and an avatar — enough to know it is you next time, and nothing more.

02

A vote is stored against an identity, never an address

Signed in, a vote is stored against your account. Signed out, it is stored against a one-way hash of a random number your browser is holding. Neither row contains an IP address, and there is no column in this database that does.

03

The voting cookie is minted when you vote, not when you look

Read every board on the site and it sets nothing. The first time you cast a vote while signed out, sixteen random bytes get written to a first-party cookie so the same browser can't vote twice on the same listing. Sign in first and you never get one at all.

04

Nothing here fingerprints your browser

No canvas probe, no font list, no screen-size profile, no device graph. The anonymous identity is a random number we gave you, which means you can throw it away — clear the cookie and the site has no way to recognise you.

05

What is on a listing was already public

Names, handles, avatars, repos, follower counts, star counts: read from the same public sources anyone can open. A contact address only appears on a listing when the person published it themselves, in their own bio or on their own site. Nothing on a listing is inferred, and nothing is bought from a data broker.

06

Analytics runs on the live site and nowhere else

Page analytics go through Google Tag Manager, and the tag is only rendered by ailead.spaceitself — a preview build or a copy running on somebody’s laptop carries no analytics at all. It measures pages, not people.

07

Leave, and the account goes with you

Delete the account and the profile behind it is deleted in the same stroke. The votes stay on the boards with your name taken off them, and deliberately: a board that unwound every vote when somebody left would be a board anyone could rewrite by leaving.

What is stored

Four buckets, and a visitor who only reads the boards fills none of them.

Your account

A handle, a display name, an avatar link, and the day you joined. The address you signed in with stays in the sign-in system and is never shown on the site.

Your votes

Which listing, when, what the vote counted for, and one identity — your account, or the hash. Quarantined votes are kept rather than deleted, so a wrong call can be undone.

What you typed

A submission is the fields on the form: a name, a link, a line of copy, a contact address where the board asks for one. A claim also keeps the proof you gave, so the decision can be re-checked later.

Nothing else

No location, no device profile, no record of which pages you read, no profile assembled across other sites, and nothing sold to anyone.

The cookies

Three, at most, and two of them need you to do something first. A voting cookie appears the first time you vote while signed out and lasts a year. A session cookie appears when you sign in and goes when you sign out. Google’s analytics cookies come with the tag manager on the live site. Read the boards without voting or signing in and the site sets none of its own.

Who else touches it

Four companies, each doing one job. None of them is an advertising network, and none of them is paid in data.

Supabase

The database, and the sign-in that sits in front of it. Every row described on this page lives there.

Vercel

Serves the pages, and keeps the ordinary server logs any host keeps. Those are the one place a raw IP address exists, and they are not part of the site’s own data.

Google Tag Manager

Counts pages on the live site. It is the only third-party script on the page.

X, GitHub, LinkedIn

Whichever one you pick signs you in, and hands over a handle, a name and an avatar. Their own policies cover what happens on their side.

Measuring is one direction

The numbers behind a rank are collected on a schedule, from a server, against public APIs — the same call for everybody, made whether or not a single person is reading. Which pages you open is never reported to the platforms a listing was measured from.

Your own listing

Every listing is built from public numbers, and a listing about a person is the case that matters most here. The fastest way to change one is to claim it — proving it is yours puts the words, the links and the takedown in your hands. What you may do with a listing once it is yours is on the terms page.

Reaching a person

A question about any of this, a correction, or a listing you want taken down — DM @prateekkathal on X. That is also the route when a listing is yours but carries no channel you can prove.

Last changed 27 August 2026