Pick the right tool. We win on some axes, lose on others. The table tells the truth.
Provenance is a wide field with several specialised standards and tools. Each of the comparisons below describes what the alternative does correctly, where it wins, and where receipts.you fits differently. If the alternative is the right tool for your case, the comparison says so. The goal is a decision, not a sales pitch.
- No.01 · Provenance standardsCompare →
receipts.you vs. C2PA (Content Credentials)
Camera-side provenance at capture. Use receipts.you when the source isn't C2PA-aware (i.e., for screenshots).
- No.02 · ArchivalCompare →
receipts.you vs. Archive.today
Server-side URL snapshots. Use receipts.you when the content is behind a login, in an app, or you need cryptographic anchoring.
- No.03 · Mobile captureCompare →
receipts.you vs. ProofMode
Android in-the-field photo capture with device-context binding. Use receipts.you for screenshots and seal-side workflows.
- No.04 · Qualified timestampingCompare →
receipts.you vs. TrueScreen
eIDAS-qualified screenshot evidence (paid). Use receipts.you when you don't need QTSP status and want free.
- No.05 · Raw primitiveCompare →
receipts.you vs. OpenTimestamps CLI
The raw cryptographic anchor receipts.you uses internally. Use the CLI when you want minimal-trust and you're CLI-comfortable.
- No.06 · Creator toolingCompare →
receipts.you vs. Privly / Ovarra
Paid SaaS bundles for adult-creator watermarking + leak monitoring. Use Snitch Tracker for free watermarking; keep paying for monitoring if you need it.
- No.07 · ClassifiersCompare →
receipts.you vs. AI image detectors
Probabilistic 'is this AI?' classifiers. Use receipts.you for the different (and stronger) provenance question.
- No.08 · MetadataCompare →
receipts.you vs. EXIF metadata
Self-asserted file metadata that anyone can edit. Use receipts.you when 'when' actually needs to be un-disputable.