Privacy
The short version
korrents is a public site. Everything you post is public by default and intended to be read by anyone. We collect the minimum needed to sign you in and attribute your posts to you. We do not sell your data, we do not run ads, and we do not share your data with third parties for their own use.
What we collect
- From Google, when you sign in: your Google account ID,
email address, display name and profile picture URL. We request only the
openid,emailandprofilescopes. We never receive your Google password, and we have no access to your Gmail, Drive, Calendar or any other Google service. - What you post: your claims, confidence numbers, notes, source links and the full dated history of every revision. Revision history is retained by design — a record of how your thinking changed is the purpose of the site.
- A session cookie so you stay signed in. It is HttpOnly, Secure and SameSite=Lax, and it holds a random session identifier and nothing else.
- People you have hidden from your feed. Hiding someone writes their handle to a cookie on your device, and that is the whole of it: no account is needed, nothing is recorded on our side, and the person is never told. No page on this site shows how many readers have hidden anyone. The feed says who it is leaving out whenever it is leaving anyone out, and one tap on that line clears it.
- What you have read, if you are signed in. Which korrents were on your screen long enough to have been read, which ones you opened, how many times, and when. It exists for one purpose: so the feed can show you what you have not read yet. It is private to you — no page shows anyone else what you have read, and no korrent anywhere shows how many people have read it. This is kept against your account rather than in the anonymous measurements below, and the two are never joined. Forget what I have read on your settings page deletes all of it, and deleting your account deletes it too. Signed out, none of it is recorded.
- Anonymous visit measurements. Which pages you opened
— including the filters in the address bar, because
/?who=someoneand/are different pages — which links and controls you clicked, anything you typed into this site’s own search box, how far down a page you scrolled, and how long the page was actually in front of you. Also the country and rough city the request came from, a coarse “operating system / browser”, and the network your connection belongs to.
We record two things that are about the site rather than about you: a control clicked three times in two seconds, and a click on something that looked pressable and did nothing. Both are stored as a count and the control’s label. We never record mouse movement, screen contents, keystrokes outside the search box, or anything you type into a form.
No cookie and no lasting identifier. A random session number is kept in your tab’s own storage so that three pages read one after another are legible as one visit; your browser throws it away when you close the tab. It is not linked to your account, it cannot follow you to another site, and coming back tomorrow makes a new one. Your IP address is used to work out the country and a one-way daily hash that counts a visitor once instead of five times — it is never stored. We also get a notification when someone is reading, containing the fields listed here and nothing else. - A visual recording of your visit, outside the EU, the EEA
and the UK. Our server looks at where your request comes
from before your browser ever sees the page. If that is the EU, the
EEA or the UK — or if we cannot tell — the page loads nothing beyond
what is described in this list. Anywhere else, it also loads
PostHog, a third-party analytics
provider, which records a replay of the session: the pages you
moved through, what you clicked and scrolled, and your cursor and
page content reconstructed well enough for us to watch it back. It
sets one more cookie on this domain, to tell one visit from the
next, only while it is running. Text typed into any field on this
site is masked before it leaves your browser, so we never receive
it. We use this to see where the site confuses or frustrates people
in a way a table of counts cannot show. This is separate from — and
not affected by — the anonymous counting opt-out below, which is
purely about the measurement described above it. It is not loaded
at all in a browser that says it is being driven by software (a
headless browser, an automated link checker).
Two facts about the page, not about you. The anonymous measurements above also record whether that recording script was included in the page you were served, whether it then loaded in your browser, and whether it declined to because the browser reported itself as automated. Many people block it, and without these two we cannot tell a reader who blocked it from a page we never offered it on. Nothing links the two records: the anonymous measurement does not carry the recording’s identifier, or any other, so they cannot be joined — by us or by anyone.
Other than that, there are no advertising or third-party tracking
scripts on this site — for a visitor inside the EU, the EEA or the
UK, the page loads no script from any domain but this one, and its
content security policy forbids it. The measurement code is
/static/b.js, served by korrents.com, reporting
to korrents.com. A copy of the same measurements is sent to
stats.kapps.dev, which is ours, so that several of our sites
can be compared in one place; nobody else receives any of it.
Opt this browser out of counting — that
preference is stored as a cookie on your device.
Three cookies of ours, in all: the session cookie that signs you in,
the counting opt-out above, and the people you have hidden from your
feed. Two of the three are preferences you set yourself, they are
read only by this site, and none of them can follow you to another
one. A fourth, k_js=1, is set only if you open a feed
filtered two or more ways at once (two people, or a person and a subject): it says "this browser runs
JavaScript", which is how we tell a reader from a scraper walking
those combinations. It holds nothing else and expires in a day. Outside the EU, the EEA and the UK, PostHog's own cookie is a
fourth, described above.
What is public
Your handle, display name, bio, and every korrent and position you post are public and visible to anyone, including search engines. A korrent marked private is visible only to you. Your email address is never shown publicly and is used only to identify your account.
Archive profiles
Some profiles are marked archive. These are compiled from statements people made publicly elsewhere; those people did not sign up and have not endorsed this site. Each such position carries a verbatim quote, a link to the original source, and the date it was stated. If an archive profile is of you and you want it corrected or removed, email hello@korrents.com and we will act on it without requiring you to prove anything.
Deleting your data
Email hello@korrents.com and we will delete your account, your posts and your revision history. You can also revoke this site's access from your Google account permissions page, which prevents future sign-ins but does not by itself delete content you already posted.
If you send us feedback
The form at /feedback stores what you typed, the page you sent it from, and an email address only if you chose to give one so we could reply. Leave it blank and the message is anonymous. If you were signed in, the message is linked to your account, and deleting your account deletes that link with everything else.
One thing is derived rather than typed: to stop the form being used to send the same message a thousand times, your IP address is combined with today's date and hashed, and only that hash is stored. It cannot be turned back into an address, and because the date is part of it, it cannot connect what you send today to what you sent last week. No raw IP address and no browser details are kept with a message.
If you ask us to add someone
The form at /add needs you signed in. It stores the name you typed, the note and the web address if you gave them, and which of our suggestions you confirmed, linked to your account. To suggest matches we send the name you typed to Wikipedia's search and to a language model run by Cloudflare; neither is told who you are, and the address you give us is never fetched. When the person is live we write a notification to your account and, once email sending is set up, send one email to the address on your account, with the link. Deleting your account deletes all of it.
Where data lives
Data is stored in Cloudflare D1 and served from Cloudflare Workers. Cloudflare processes it as our infrastructure provider. Feedback is kept until it has been dealt with; ask and yours is deleted.