How proof works
How proof works
You don't need to take our word for it. Every match in LicenseTrack leaves a paper trail you can show a platform, a lawyer, or a judge. Here is what each layer is and when it matters.
1. The certificate that ships with each match
A proof-of-use certificate is a one-page PDF that records a single detection. It carries the detection ID, the platform, the source URL of the infringing upload, the match confidence, and the timestamp the scanner first saw it.
If a detection matters to you, download the certificate from the matching row in Activity. It is the file you attach to a takedown notice and the file you hand to a platform's trust and safety team when you need to escalate. One record, one page, no database login required to read it.
The certificate is downloadable from Activity once a detection exists. Until a match is found there is nothing to certify, so you do not get anything before the scanner has seen the infringement.
2. The timestamp that proves when we saw it
The blockchain anchor is an optional second layer that records the detection's proof-of-use hash to a public chain at the moment of detection. Once anchored, the receipt can be re-verified at any time without trusting LicenseTrack.
When you turn anchoring on for your account, every new detection runs through the chain proxy and the receipt surfaces in the matching Activity row. You decide when to flip it on, and you can leave it off without affecting the certificate or the DMCA workflow.
Anchoring is optional per account. It only runs where the chain proxy is configured for your workspace, and it is disabled by default so accounts on smaller plans are not billed on-chain traffic they did not ask for.
3. The DMCA notice that gets filed on your behalf
The DMCA workflow is what actually resolves an infringement. When a detection matters, you open it from Activity, hit “File takedown,” and LicenseTrack submits the notice through the platform's own webform using the auth cookies you saved on signup.
The day you sign up, you paste the platform auth you already have (YouTube channel cookies, SoundCloud login, and so on) into the Setup flow. From then on, every notice goes straight from the dashboard to the platform's takedown queue. You get an archived copy of every notice filed, and the matching Activity row updates as the platform responds.
The DMCA is filed through your saved platform auth. If your cookies have expired or you have not saved them yet, the takedown step surfaces a reminder rather than submitting a half-completed form.
Get the weekly detection digest
Ready to watch your first detection roll in?
Start your 7-day free trial — card required. No charge for 7 days; cancel before day 8 and you won't pay a penny.
Questions? Email licensetrack@polsia.app.