Dispute a False Content ID Claim With Your Own Dates — Free
Paste the claim details and your upload history, and check the dispute has every element it needs — your original date, the source files, the disputed minute — before you press the button.
The proof surface
Most disputes fail on missing provenance, not on being wrong; checking the reader's own draft against the five elements turns a hopeful paragraph into a dated, evidenced filing.
Why the flat version breaks
Disputing in one line
'This is my video' gives the reviewer nothing to verify and gets processed as boilerplate.
Skipping the timecode
A dispute that never names the disputed minute asks the reviewer to hunt for it — they don't.
Filing before the license is in hand
The receipt that proves the license lives in your inbox until you attach it; after a denial, the appeal window is shorter.
How to work the dispute register
The notice, your upload date, the disputed timecode and every license fact you hold.
Each required element is present or missing, with the readiness count in the margin.
Find the receipt, name the originals, write the timecode — then re-run.
Submit the dispute with the five elements attached, and keep the register for the appeal.
What the register replaces
| Question | Before | On the register |
|---|---|---|
| Is the dispute ready | send it and hope | five elements stamped present or missing |
| What is the claim against | a vague email quote | the claim ID, claimant and timecode boxed at the head |
| Where is the proof | scattered across drives and inboxes | each element's location written on its line |
The register audits what you paste; the platform's own dispute form is where the filing actually happens.
Run it on the samples, right here
FIRST-LOAD
Data note: Everything runs in this browser tab on the dispute register: your claim notices and your upload history stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a bound register page
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the ready-to-mail packet, and holds your drafts on this device — one free run, then $ 7 one-time for the layer that keeps filing.
The register and the readiness check are free. The paid layer keeps a register per claim, prints the dispute sheet with your dates, and tracks retraction and appeal deadlines.
Open the claim dispute register companionBoundary
This dispute register works only on the claim details and your own dates you paste. It does not decide who owns the copyright, does not file the dispute on the platform for you, and does not advise on takedown law. The figures describe what you supplied, not what is true in the world. Confirm anything you plan to act on with the platform's creator support for a denied dispute, and a media lawyer for a copyright strike before you rely on it.
What this is built on
- Every figure comes from the claim details and your own dates you paste; nothing is looked up, scraped or asserted as verified.
- Method: each required element is tested against the text you paste with a pattern per element; every element is stamped found or missing and the readiness count is printed in the margin
- Sample values are labelled samples — illustrative by design, not your data and not a quotation of any organisation's policy.
Before: the reader fired off a one-line dispute and lost. After: they file as someone whose provenance is documented — upload date, camera originals and license all on the register — because they checked each element themselves.