Receipts for screenshots.
Dated. Signed. Externally anchored. So when stops being your word against theirs.
We don't store your image — we take a fingerprint of it, sign it, and stamp it with a time anyone can verify against a public blockchain. Later, when the question becomes “did this exist on X date?”, the answer is a receipt instead of a debate. The receipt proves the timestamp, not the truth of what's in the image. The math behind it (SHA-256, ECDSA P-256, OpenTimestamps anchor) lives on the methodology page if you want to read it, or there's a 12-min guide if you'd rather have the long version.
Seal early. A receipt is only as strong as the gap between when it was sealed and when the dispute started. Sealing right after you take the screenshot carries the most weight; sealing after an argument is already underway is fine but proves much less.
A receipt proves when. Not what, not who, not why.
We'd rather be explicit about what we actually deliver than oversell. receipts.you stamps a file with a cryptographic hash + an ECDSA signature + an external timestamp anchor. That combination proves one specific thing: these exact bytes existed at this exact timestamp. It does not prove the image is unedited footage of a real event. It does not prove authorship. It does not prove the content is true.
- Proves the file existed at the sealed time. Independently anchored to an external blockchain. Even we can't back-date it.
- Settles “when did this happen?” arguments. If a screenshot was sealed before an event/dispute, that ordering is mathematically verifiable.
- Defeats post-hoc backdating. Anyone can edit an EXIF timestamp in seconds. Nobody can edit an anchored OpenTimestamps proof.
- Survives if we disappear. The OpenTimestamps proof verifies forever against public blockchain headers with the standard
otsCLI.
- Does not prove the image is true. Anyone can seal anything — a real screenshot, a doctored one, a fully generated one. The receipt is valid either way. It only says the bytes existed at the timestamp.
- Does not prove who created the file. The signature is ours (we signed it for you), not yours. We don't verify identity.
- Does not prove provenance. Where the image came from, whether it's an unedited capture, whether it represents a real event — out of scope.
- Can be abused. Someone can seal a fake screenshot today and use the resulting receipt to lend false credibility. The receipt's timestamp is real; the image content's relationship to reality is not anything the receipt addresses.
Because when is a load-bearing question in a surprising number of disputes. “Did you see this before the announcement?” “Was this DM sent before the breakup or after?” “Did this listing say €40 on Tuesday or €60?” In each, the disagreement is fundamentally about timing — and a dated, signed, externally-anchored receipt resolves the timing in a way no screenshot alone can. The strength of any receipt is in sealing early: sealing at the moment you saw the file, before anyone has reason to dispute the date. If you can do that, the receipt carries the argument. If you seal late, after a dispute is already underway, the receipt only proves what it can — that you had the file by the sealing time — which is rarely enough.
The full methodology, including what the cryptography actually does and what it doesn't, is on the methodology page. The live extraction test rig for the Snitch Tracker watermark (a separate question about leak attribution, not about truth) is at /lab.
Nine moments when when is the whole argument.
You don't need a court case to want a receipt. Each one is a real, ordinary moment where the disagreement boils down to timing — and where a dated, signed, externally-anchored receipt replaces “your word against theirs” with a timestamp anyone can verify. The receipt does not prove the content is true; it proves when it existed.
When your parent says "I never told you that"
Seal the WhatsApp screenshot the moment they send it. Months later, when memory becomes negotiable, the receipt is dated, signed, and externally anchored.
When the ex tries to rewrite history
"I never said that" / "I never threatened you." The receipt's timestamp predates the restraining-order conversation, the breakup, the gaslighting attempt.
When the harasser deletes the DM
Screenshot it the second you see it, seal it in ten seconds. The post-deletion claim of "that never happened" becomes math, not memory.
When a group-chat leak gets out
Mint per-recipient invisibly-watermarked copies of a sensitive screenshot. When one shows up where it shouldn't, the Snitch Tracker tells you which friend leaked it.
When an OnlyFans / Fansly subscriber leaks your content
Per-subscriber watermarks bake an invisible ID into every copy. Free, in your browser — no $30/mo monitoring subscription required.
When you called it first and someone steals the take
Seal your hot take, your meme, your draft post the moment you write it. The receipt is the timestamped "I called it."
When a public figure deletes the tweet
Screenshot, seal, post the receipt URL — the timestamp is anchored to a public blockchain, so even we can't backdate it. Faster than archive.today; portable; private.
When you're buying or selling on Marketplace / Vinted
Seal the "we agreed on €40" message. When the seller flips to "no, €60," produce the receipt with a timestamp that predates the dispute.
When someone slips you a fake screenshot
Drop it in /verify. If it has a receipts.you QR, you immediately learn whether it's the byte-identical original, a platform-recompressed copy, or a paste-the-QR-on-a-fake (red verdict).
The leak-detection variants (group chat, OnlyFans) use the Snitch Tracker. Everything else uses the plain sealer. Both are free, both run in your browser, neither sees your image.
The image bytes existed at the timestamp.
Cryptographic signature + independent third-party timestamp. We record two hashes per receipt — the clean original you uploaded AND the QR-stamped version. Either one verifies; one extra pixel = different hash = mismatch.
That what's in the picture is true.
Anyone can seal anything. The receipt is a notary stamp, not a truth machine. We are aggressive about this distinction.
Keep the original. Share the stamped one.
Every receipt records two hashes: the clean original you uploaded, and the QR-stamped version you share. Either matches against the same receipt at /verify.
This means a receipt can also serve as a dated record of the file's existence — even if you never share the stamped version. If a dispute ever comes up about whether a given image existed by some earlier date, your receipt is dated, signed, and anchored to an independent third-party timestamp.
The caveat we're explicit about: a receipt only proves the bytes existed by the timestamp. It does not prove authorship or possession. If someone seals an image they didn't make, their receipt is still valid — they just can't claim credit honestly. So the rule is the same as for any timestamped evidence — seal early, seal often. One receipt isn't a verdict, but it's a hard fact in any timing argument.
One stamped image. One receipt URL. Anyone can re-verify the timestamp.
The whole flow takes about ten seconds. You drop your screenshot, we hash it locally, sign it, anchor the timestamp externally, and hand you back three things: the stamped copy of your image, a public receipt URL anyone can scan, and the original SHA-256 so you can re-verify the receipt offline forever. The receipt is evidence of when the file existed — not of what it depicts or whether the depicted content is true.
The QR on the stamped image scans to this URL. Anyone with a phone camera can verify the receipt — no app, no signup.
- Sealed at2026-05-24 14:23 UTC
- Signed byreceipts-you-2026 · ECDSA P-256
- Anchorconfirmed · external timestamp
- Original hasha3f1c2…b9d8 (sha-256)
- Verifydrop the stamped image here → instant SHA + signature check
Anyone whose screenshot might be questioned.
- Journalists — seal source screenshots as you collect them — tweets get deleted, DMs get withdrawn.
- Lawyers — file a dated, signed artifact that doesn’t depend on your word for the timestamp.
- Moderators & fraud teams — settle “when was this said” disputes with an externally anchored timestamp.
- Anyone — building a case, fighting gaslighting, or archiving a disappearing post — one receipt at a time.