There is no signup
No email. No phone. No password. No "continue with Google." You pick a tag and you're in — usually under a minute.
An anonymous platform for writers. Your tag lives in your pocket, not on our servers.
1NKY is a place to post flicks, run boards, and talk shit without leaving a paper trail that ends with a detective at your door.
Every other platform that writers use was built around a profile: an email, a phone number, a follower graph, a login history, an ad ID. That profile is the product, and it is subpoenable. Writers get identified off their own Instagram accounts routinely — the follower graph, the caption, the face in the background of a flick. That's not paranoia, that's case law and press releases.
So 1NKY doesn't have profiles in that sense. It has tags, and a tag is not an account on our system. It's a secret that gets made on your phone or laptop, stays there, and is used to put your name on your posts in a way that anyone can verify and nobody can forge.
Nothing to log in to. There is no password to phish, no email to link back to you, no "forgot password" flow that leaks your identity to a mail provider.
Nothing to leak. We don't run request logs, and the database schema has no column for an IP address — not a nulled-out one, not a hashed one, none. See No logs, by architecture, which tells you exactly where to look in the public code to confirm it.
Nothing in your photos. Camera metadata — GPS coordinates, timestamps, the serial number of your phone — is destroyed on your device before a single byte is uploaded. We never receive it, so we can never lose it. See Opsec for writers for how to verify that with exiftool.
Nothing that dies with us. Your tag and your posts are cryptographically yours. If 1NKY gets raided, sued, or hit by a bus, the identity in your pocket still works.
We're not going to sell you magic. Read this part twice.
Every privacy pitch on the internet is a paragraph of adjectives. This site is built to be checked, not believed. Where we make a claim, we try to point at the file, the command, or the browser tool that proves it — and where we can't prove something yet, we mark it as a promise instead of dressing it up as a fact.
If you find a place where the docs and the code disagree, that's a bug and we want to hear about it: report it here.