If you're sure you used only your own (or properly licensed) content and still got a strike, it's usually a false claim, an automated mismatch, or a misidentification. Here's how to confirm and respond — paste the notice above first.
Three common ones: (1) a fraudulent or mistaken claim from someone who doesn't actually own anything in your content; (2) an automated content-match (like Content ID) firing on common audio, stock, public-domain, or your own re-used material; (3) misidentification — the claimant targeted the wrong video, listing, or account. None of these means you actually infringed.
Automated systems and careless claimants don't evaluate fair use, licenses, or ownership before a takedown — content is removed first to preserve safe harbor. So legitimately licensed music, your own older uploads, royalty-free assets, and clear fair-use clips all still get struck. That's not proof you did anything wrong; it's the system erring on removal.
Paste the notice above to see whether it even identifies a specific work and meets §512. If it names no real work you used, comes from an unverifiable sender, or targets content you own or licensed, it's likely invalid or abusive — and you have a strong counter-notice.
Gather proof of your rights (project files, license receipts, upload dates). Don't delete the content preemptively. File the platform's counter-notification or dispute, stating a good-faith belief the strike was a mistake. Keep records in case the claim repeats.
Usually a false claim, an automated content-match error, or misidentification. Takedowns happen before anyone checks ownership or fair use, so original, licensed, or public-domain content can still be struck. It doesn't mean you infringed.
Confirm the notice's validity (paste it above), collect proof of your rights, and file the platform's counter-notification/dispute stating the strike was a mistake. If the claim was knowingly false, it may also violate §512(f).