Tracking — what left, and where it wentENGINE — watermark (Mav owner map, 2026-08-09: Leak tracer and Tracked accounts are both engine rows). Reclassified COMMON in round 3 — “each platform has its own tracking.” One surface, every admin mounts it; Receipt’s tab set is its own real thing — click & attribution tracking — because that is what Receipt actually tracks. folo.link answer: the tracer is a read of the engine’s one forensic store, so it runs the same everywhere; the only writes on this page (observation flags) route through the owning platform’s creator record.
Leak tracing and observed test accounts — the watermark engine’s two reads.
PartialDemo data
Leak tracerDrop a suspected leaked file; the tracer reads the forensic alpha-LSB watermark back out and names the account it was served to. Nothing is uploaded anywhere public — this is an internal forensic read.reads the shared watermark pipeline · engine
Upload a leaked file · the watermark names the buyer it was served to.
Effect: the trace identifies the buyer across whichever platform delivered the file — Folo or Fanogram — because marks are written and read against one forensic store, never per-product copies.
◎
Drop the file here, or click to choosePNG and WebP read back best — lossy re-encodes (screenshots, re-saved JPEGs) can destroy the mark; the tracer says so rather than guessing.▩
One watermark engine, both products. Marks are applied on serve by the shared vault CDN — see Vault & media. Every trace run is audited.
Traces run · 30d
23
by staff · every run auditedDEMO DATA · window: 30d · source: watermark engineMarks recovered
17
6 unreadable — lossy re-encode named as the reasonDEMO DATA · window: 30d · source: watermark engineFormat truth
Stated up front, not discovered in failure.
✓
PNG · WebPlossless alpha — full payload survives
best△
JPEG re-savealpha flattened — partial or no readback
degrades✕
Screenshot / screen-recordmark destroyed — tracer reports “no mark”, honestly
lost