Trace · Report
The Leak Source Report.
A quarterly, anonymised look at how creator leaks actually happen, based only on Trace cases whose creators said yes.
There is no data on this page yet, on purpose.
The first edition will publish once there are enough consented cases to say something reliable. Until then, any number here would be a guess, and creators already get enough of those.
What it will cover
Questions creators ask us, answered from checked cases.
Answered from real, checked cases rather than forum stories:
How the leaked copy was delivered
PPV, DM, custom, vault or mass message.
What happened to it
Saved as is, screen recorded, cropped, re-uploaded, clipped.
Where it turned up
By type of place, such as leak sites, Telegram, Reddit or file hosts. Never links.
How fast
Time from delivery to the leak being found.
How often a check was conclusive
And how often it wasn’t. Inconclusive results stay in.
Methodology
Consent first. Only checked cases.
Consent first.
Creators are asked, case by case and separately from any other permission, whether a case can be counted. Nothing is included without a yes.
Only checked cases.
A case counts when a leaked copy was uploaded to Trace and checked. Suspicions don’t count.
Attribution language stays careful.
A match means the leaked copy was the one delivered to a particular account. The report counts copies and delivery paths, not people.
Every edition states its limits:
how many cases it is based on, the period covered, and what the sample can’t tell you.
Privacy
No names. No files. No links.
No names
No creator names, stage names, fan names or fan handles.
No media
No files, images, frames or audio. No links to where anything was found.
Grouped figures
Any group of fewer than 5 cases is merged or left out, so no figure can point at one creator.
Consent can be withdrawn
Before an edition is put together. See the privacy policy for how Trace handles case data.
In the meantime
What we can publish now.
How the marks hold up
The Trace Robustness Report lists every attack we ran and what Trace said.
Published research
For a published study of creator safety practices, a USENIX Security 2024 paper interviewed 43 OnlyFans creators about the threats they face, including content leaks (Soneji et al.).
Want to know when the first edition is out?
Email info@creatorsenseai.com.
FAQ
Common questions, short answers.
When will the first Leak Source Report come out?
When there are enough consented cases to say something reliable. We won’t set a date and then fill it with thin data. If you want to know when it is out, email info@creatorsenseai.com.
Will my case be in it?
Only if you say yes to that case. Nothing goes in by default, and you can change your mind before an edition is put together.
Will fans or creators be identifiable?
No. No creator names, fan names or handles, files, images or links are published. Figures are grouped, and groups too small to hide any one creator are merged or left out.
Is this a measure of all leaks?
No. It only covers leaks that creators using Trace found, checked and agreed to include. That is a useful view of how leaks happen, not a count of every leak.
Next step
See what’s already out there.
The free exposure scan counts indexed leaked files for your creator name. No account needed.
The scan takes about two minutes and needs no account.