ink // void
We Are Working For Your Privacy...
#stopchatcontrol #nullsec
INKVOID is a temporary, throwaway email service built for one purpose: letting you exist online without handing over your identity. No account. No password. No recovery email. You open an inbox, you use it, and thirty minutes later it is gone — permanently, irreversibly, with nothing left behind for anyone to find.
Every time you sign up for something — a forum you'll visit once, a social account you're not sure you'll keep, a site you don't trust yet — you're asked to hand over a real email address. That address gets stored, sold, leaked, or quietly cross-referenced against everything else you've ever typed into a form. Data breaches don't ask permission. Marketing databases don't forget. And once your address is out there, it's out there for good.
INKVOID exists to remove that trade-off entirely. You get a working inbox instantly, no identity attached to it, and when the thirty minutes are up, the inbox and everything inside it is deleted. Not archived. Not soft-deleted. Gone.
In this first phase, INKVOID runs on external server infrastructure. That's a deliberate, temporary choice — it lets the service launch fast without the overhead of building physical infrastructure from zero, while the core no-logs architecture is already fully in place regardless of who hosts the hardware.
As the project grows, that will change. The long-term plan is to migrate INKVOID onto servers we own and operate ourselves — hardware under our direct control, in jurisdictions chosen specifically for their privacy protections, with no third-party provider ever in a position to see, log, or hand over what passes through the system. Owning the infrastructure is what turns "we don't log anything" from a policy into a physical fact.
There is no CAPTCHA on INKVOID, and there never will be. Putting a CAPTCHA in front of a privacy tool is backwards — most CAPTCHA providers are themselves tracking systems, fingerprinting your browser and behavior under the excuse of "proving you're human." That's not a trade-off INKVOID is willing to make.
That doesn't mean the service is left open to abuse. Instead of identity checks, protection is handled at the network layer, without collecting anything personal:
During Phase 1, network-level DDoS mitigation may run through external infrastructure, strictly to absorb large-scale attacks at the connection level — never to inspect, log, or fingerprint individual users. Anything resembling application-level tracking is out of scope, now and after the migration to self-owned servers.
Across the world, the direction of travel is the same: more surveillance, more data retention, more "just in case" monitoring of ordinary people who have done nothing wrong. Governments keep proposing systems that scan private communications by default, under the justification that it's for safety, while the actual effect is a permanent infrastructure of mass surveillance that, once built, never gets dismantled.
This isn't a European problem alone. Data retention laws, backdoor requirements, "lawful access" mandates — the same pattern repeats in different countries under different names. The right to a private conversation, a private thought, a private account you can walk away from without being tracked, is being eroded piece by piece, one "temporary emergency measure" at a time. INKVOID is a small, practical piece of resistance to that trend: a tool that simply refuses to keep the data it was never asked to keep.
INKVOID is currently in active development. Public launch is targeted for late October, with the core disposable-inbox system as the first release. Everything shown here reflects the actual build in progress, not a concept — the architecture works, the no-logs behavior is enforced, and what's left is refinement, testing, and getting it ready for real traffic.
A privacy tool that asks you to just trust it is no better than the systems it's trying to replace. So as soon as INKVOID opens to the public, the core codebase will be released as open source, for anyone to read, audit, fork, or run themselves.
That includes the parts that actually matter for trust: how temporary addresses are generated, how the 30-minute deletion is enforced, how the proof-of-work anti-abuse system works. Nothing about the "no logs, no accounts, real deletion" claims will be a black box — you'll be able to check the logic yourself instead of taking anyone's word for it.
What stays private is only what has to: API keys, server credentials, and infrastructure-specific configuration — the actual secrets, not the logic. The code will be structured so that anyone can run their own instance by supplying their own configuration, without ever touching ours.
The repository will be released under the AGPL-3.0 license. That choice is deliberate: AGPL requires that anyone who runs a modified version of INKVOID as a public service also releases their changes. It exists specifically to stop someone from taking this code, closing it off, and quietly turning it into the kind of opaque, unaccountable service INKVOID was built to avoid.