You're not the
product
anymore.
Your inbox is worth money to researchers. We built the vault that lets you sell it without anyone — including us — ever reading it.
V0 proves Uber ride receipts, no dollar amounts yet. V1 ships the first dollar-extracting blueprints in May.
Open DevTools. Watch the counter. Our server receives nothing until a finished proof ships. The browser enforces it.
Your data has been a fire sale since the early 2000s.
Brokers made billions.
You made nothing.
We're renegotiating the contract.
What leaves your browser.
And what doesn't.
- Your email address
- Your name
- Your home address
- Your phone number
- Your credit card digits
- Item-level detail (what exactly you ordered)
- The people you email
- Your password
- Your other messages
- Anything else Google has on you
{
merchant: "DoorDash",
merchant_domain: "doordash.com",
category: "food_delivery",
amount_cents: 3420,
currency: "USD",
tip_cents: 520,
timestamp: "2026-04-03T14:22:00Z",
metro: "US-NY-NYC",
payment_method: "card",
is_first_order: false,
dkim_valid: true,
anon_user_id: "p_8f2a...c91b",
proof: "0x7f3a...c91b"
}The browser is hard-locked via Content-Security-Policy headers. connect-src is whitelisted to Google's APIs and nothing else. If a future bug or dependency ever tries to POST the contents of your email anywhere, the browser blocks the request. The promise is architectural, not aspirational. Read the policy →
Researchers. Not advertisers.
Three buyers. None of them want you as a target. All of them want the signal without the PII.
They want to read DoorDash's next earnings report thirty days before it prints. Aggregated verified receipts across 10,000 real users tell them whether Q3 beat consensus. They pay $50k to $500k per dataset, per quarter.
Her consumer behavior study needs real spending data without an IRB nightmare. Verified panels from verified humans, with cryptographic provenance, sold per-record. Published papers, not ad targeting.
Your bank statement can be faked. Your Uber Eats payout emails can't. Lenders pay for proof-of-income that can't be forged, sent directly by you when you apply for a loan. You get cut in every time.
* Not in scope: ad networks, data brokers, anyone who wants to target you back. If we ever accept that kind of buyer, we stop being Redactable.
Drag the sliders.
Find out what you've been giving away.
Honest numbers, benchmarked against current alt-data market rates. We split 80/20 in your favor, always.
Four steps. Zero servers touching your email.
Not to us. You OAuth directly with Google. The token never touches our server. We have no session, no backend auth route, nothing to leak.
A zero-knowledge prover runs in a Web Worker in your tab, built on zk.email's open-source SDK — the same cryptography that powers zkP2P and Clave. Sixty to one hundred eighty seconds per receipt. Slower than remote proving. That's the whole point.
Line by line. Every field that will be published is shown to you before it ships. If you don't like what it says, hit cancel. Nothing leaves.
Only the finished proof is uploaded. Our server receives a ~20KB JSON blob of math and nothing else. Buyers get verified data. You get your cut.
The ones we'd ask too.
No. The browser blocks us. Read the Content-Security-Policy header on this page. connect-src is whitelisted to Google's APIs and our own origin. If any code on this page tries to POST the contents of your email anywhere else, the browser refuses the request.
There's nothing to steal. Our database contains finished zero-knowledge proofs. Proofs contain math. Math is not personal data. Even if we shipped every row tomorrow, no inbox contents would leak.
USA only on purpose. California's CCPA governs the resale of personal information, and our whole design avoids that category: the proofs contain no personal information by construction. Once we onboard actual buyers we'll register as a data broker in California. GDPR is deliberately out of scope for V1.
Alt-data hedge funds, academic researchers, credit underwriters. Not ad networks. Not data brokers. Not your employer. If we ever accept that kind of buyer, we stop being Redactable.
Don't. The entire browser client is open source. Audit every line. If you find a way email contents could leak, file an issue and we'll fix it publicly.
Sixty to one-hundred eighty seconds per email on a normal laptop. Remote proving exists and is faster, but that would require sending the raw email to someone. We refuse the trade.
Gmail and Outlook. Both flow through the same client-side SDK. Yahoo, iCloud, and ProtonMail are on the roadmap once V1 ships.
That's between you and Google. We're not in the chain. We don't have your token, your emails, or your identity. Our database contains proofs attached to a random user ID you control.
Your inbox is holding money.
First thousand users get priority payouts and a lifetime bump on the split.
We'll email you when V1 opens. Nothing else.