Knowledge
Takedown procedures, by platform.
Sourced reference cards for YouTube, TikTok, Instagram, Telegram, and the Mega.nz / anonfiles family / streamable-mirrors set — each pulled from the platform’s public IP/copyright policy and verified as of 2026-08-01. Every card lists the report-form URL, the evidence required, the platform’s published response window, and the appeal path so a creator who hits a wall can find a workaround fast. Filter live by platform, content type (deepfake vs. clip-rip), and evidence type — timestamps, original upload, ownership proof, or face / voice evidence for deepfakes.
Filterable platform procedures
Filter the KB
10 of 10 procedures match your current filters. All filtering happens in your browser — no network roundtrip.
Platform
Content type
Toggle one or more to scope the KB to a particular complaint category.
Evidence type
Narrow to platforms whose policy rewards a specific kind of proof — timestamps for re-uploads, face / voice evidence for deepfakes, ownership for authorized-agent claims.
Verified 2026-08-01
Where to file
Submit through the YouTube Copyright webform (available to logged-in account holders); include the specific video URL(s) and a description of the original work. Trademarks use a separate trademark webform on the same help center.
Evidence required
- Direct link(s) to the allegedly infringing video(s) on youtube.com.
- Description of the original work and a link to your authorized copy (channel, official upload, or published source).
- Your contact details and a statement, under penalty of perjury, that the claim is accurate and you are authorized to act for the rights holder.
- Physical or electronic signature (typed name is generally accepted for the webform).
Evidence checklist6 items
Timestamps & links
- Note each clip’s start time (e.g. “3:42–4:17”) and the matching URL fragment.
- Capture a still frame or transcript snippet that pinpoints the infringing segment beat-for-beat.
Original upload
- Link to your authorized copy on your own channel, the publisher’s official upload, or a released source.
- If the original is mirrored on the platform, include the official URL so reviewers can compare.
Ownership proof
- Show you hold the rights or are authorized — a publishing contract excerpt, content-ID ownership proof, or signed statement naming you as the agent.
- Provide your full contact details and a perjury statement; typed signature is accepted on the webform.
Response window
Typically a few business days for a counter-notification to be acknowledged; full resolution can take longer depending on review volume per the YouTube Copyright help center.
Escalation paths
- If a counter-notice is ignored or rejected without cause, file a second notice referencing the prior submission.
- For repeated inaction, escalate via YouTube’s escalated copyright support channel in the help center, or escalate to a designated agent through the US Copyright Office public directory if you need to invoke §512(g).
Verified 2026-08-01
Where to file
Use the TikTok intellectual-property report form (logged-in webform): choose the IP category that matches your claim (copyright or trademark) and provide the infringing video URLs. A separate Counter-Notice flow exists for users who believe content was wrongly removed.
Evidence required
- Direct link(s) to the allegedly infringing TikTok video(s).
- Description of the original work and proof of ownership or authorization (link to your original, registration certificate, or authorship evidence).
- Your contact details (name, email, physical address) and the country of residence.
- A good-faith statement that the use is not authorized by the rights holder, agent, or law.
- A statement, under penalty of perjury, that the information is accurate and you are authorized to act for the rights holder; your physical or electronic signature.
Evidence checklist8 items
Timestamps & links
- Quote the video URL plus the precise start/end of the reused segment.
- Capture a screenshot of the timestamped comment or overlay so a reviewer can match the frame.
Original upload
- Provide a link to your original TikTok, your YouTube/cross-post, or the publisher’s source.
- If you have a registered copyright, attach the registration number as supporting context.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) with documentation.
- Include your physical address — TikTok’s policy mirrors §512(c) and rejects notices without one.
Face / voice evidence
- For impersonation / deepfake content, attach a side-by-side comparison clip or stills showing the original face / voice vs. the synthesized version.
- Reference your published likeness rights or biometric identity proof where available.
Response window
Per TikTok’s IP policy, complaints are reviewed in order of receipt; reviewers typically respond within a few business days, though full removal + notice turnaround can run longer under high volume.
Escalation paths
- Submit a fresh IP report referencing the prior submission if the platform does not act.
- If you’re a US filer and need a written §512(g) acknowledgement, escalate via the legal/copyright contact referenced in TikTok’s help center.
Verified 2026-08-09
Where to file
Submit through Meta's Instagram IP Report form at (covers copyright, trademark, and counter-notices for Instagram posts, Reels, and accounts). The fastest path for a single post or Reel is the in-app Report flow → "Intellectual Property" → "Copyright" / "Trademark"; the webform is the canonical path for multi-URL filings, DMCA-style submissions, and case tracking
Evidence required
- Direct link(s) to the allegedly infringing Instagram post(s).
- Description of the original work and proof of ownership or authorization.
- Your contact details, including a physical address (required for a complete DMCA-style submission).
- A good-faith statement that the use is unauthorized.
- A statement, under penalty of perjury, that you are authorized to act for the rights holder, with your signature.
Evidence checklist8 items
Timestamps & links
- List each post / Reel URL plus the start time of the infringing segment when it’s a video.
- For carousel posts, pin the exact slide number that reproduces your work.
Original upload
- Link to your own Instagram handle / Reel, Facebook page, or the publisher’s release.
- If the original post has been removed, supply an archived snapshot (Wayback, archive.today) as proof of authorship.
Ownership proof
- Submit proof of rights: a publishing contract, license, or authorship declaration.
- Include your full physical address and signed perjury statement — Meta’s form mirrors §512(c).
Face / voice evidence
- For impersonation or face-swap content, attach biometric evidence (side-by-side images, forensic comparison, prior likeness release).
- Reference Meta’s policies on impersonation where the deepfake is the dominant claim.
Response window
Per Meta’s IP policy, the platform typically acknowledges or acts within a few business days; counter-notifications follow a similar pace, with the full cycle varying by reporting volume.
Escalation paths
- Re-file via the IP webform with the prior case reference if no action is taken.
- For repeated inaction, escalate to Meta’s IP contact referenced in the Help Center, or invoke a counter-notification if your own content was wrongly removed.
Verified 2026-08-11
Where to file
File through Meta's IP Reporting Portal at — the canonical webform for Facebook copyright, trademark, and counter-notifications, and the same queue Meta routes Instagram and WhatsApp claims through. The fastest path for a single post or Reel is the in-app Report flow: on the offending post tap ⋯ → "Report" → "Intellectual Property" → "Copyright" / "Trademark". For multi-URL filings, §512-style DMCA submissions, and case tracking, use the Meta IP Reporting Portal webform; the documented email fallback for cases the webform cannot capture is ip@meta.com
Evidence required
- Direct URL(s) to the allegedly infringing Facebook post(s) or Reel(s).
- Description of the original work and a link to your authorized copy (your own page, the publisher’s official upload, or a published source).
- Your contact details — full legal name, monitoring email, country of residence, and a physical address (required for DMCA-style submissions per Meta’s IP form, which mirrors §512(c)(3)(D)).
- A good-faith belief statement that the use is not authorized by the copyright owner, its agent, or the law.
- A statement, under penalty of perjury, that the information is accurate and you are authorized to act for the rights holder, with your physical or electronic signature.
Evidence checklist9 items
Timestamps & links
- Capture the full facebook.com/<page>/posts/<id> URL of each infringing post or facebook.com/reel/<id> for each Reel — do not shorten or use a tracker.
- For clipped excerpts (a Reel that uses a segment of your work rather than a full rehost), supply the precise start/end of the reused segment and one still frame from the timeline.
- If the post or Reel may be deleted before Meta’s team reviews, mirror it through archive.today / Wayback and attach the snapshot URL as a fallback.
Original upload
- Link to your authorized copy — your Facebook Page, your cross-post on Instagram/YouTube, or the publisher’s release.
- If the original has been removed from Facebook, supply an archived snapshot (Wayback, archive.today) proving your prior publication on the platform.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) with supporting documentation (publishing contract excerpt, license, or authorship declaration).
- Include your full contact details (legal name, mailing address, country of residence) and a perjury statement with your signature — Meta’s webform mirrors §512(c)(3) and rejects notices without a complete address block.
Face / voice evidence
- For deepfake / impersonation content, attach a side-by-side comparison still or transcript fragment showing the original face / voice vs. the synthesized copy.
- Anchor on timestamps + original-post provenance rather than a voiceprint comparison alone — Meta’s reviewers treat biometric-only evidence more sceptically than timestamped comparison evidence.
Response window
Meta’s IP policy does not publish a formal SLA. Complete §512-style webform reports are typically acknowledged within a few business days; full removal + repeat-offender enforcement typically resolve within 1–2 weeks under normal volume, and the queue can run longer under high intake. Treat any unacknowledged notice after 10 business days as needing a re-send via the same Meta IP Reporting Portal with the prior case reference.
Escalation paths
- Re-file via the Meta IP Reporting Portal (https://www.facebook.com/help/963328529904498) referencing the prior case ID — keep the confirmation page / email so the second notice is timestamped against the first.
- Email ip@meta.com as the documented fallback when the webform cannot capture the report (e.g. mass infringement across many posts); subject header formatted as "DMCA Notice — <page or username> — <work title>" matches Meta’s published intake convention.
- For repeated inaction on a US-jurisdiction copyright claim, route to Meta’s designated-agent record in the US Copyright Office public directory at https://www.copyright.gov/dmca-directory/ — that path is what §512(g) restoration rights run through when Meta wrongly restores after a counter-notice.
- For an impersonation-only claim (a Page or profile posing as you / your brand with no underlying copyright work to allege), do NOT file on the copyright webform — file the impersonation report on the offending Page via the in-app Report flow (⋯ → Report → Pretending to be someone else → Me) and route any brand-Page claim to Meta’s brand-impersonation intake; the impersonation queue is separate from copyright review and the rules differ.
Verified 2026-08-09
Where to file
Twitch does not operate a separate in-product copyright webform. File through the published Twitch DMCA notice policy () — fill out the §512(c)(3) statement and send it to the Twitch designated agent at copyright-issues@twitch.tv, with the VOD / clip / channel URL on its own line. For non-copyright abuse (harassment, account impersonation that's not a deepfake), use the in-product channel report (https://www.twitch.tv/p/support/article/Reporting-a-User-or-Channel) instead — that's the trust & safety queue, not the copyright queue
Evidence required
- Direct URL(s) to the infringing VOD, clip, or channel — for a clip use https://clips.twitch.tv/<id> or the https://www.twitch.tv/<channel>/clip/<id> share URL.
- Description of the original work and a link to your authorized copy (your own channel, official upload, or publisher source).
- Your contact details (full legal name, monitoring email, country of residence). Twitch's DMCA policy does NOT require a physical-address block, but for US §512(g) escalation add a mailing address anyway.
- A good-faith statement that the use is not authorized by the rights holder, agent, or law.
- A statement under penalty of perjury that you are authorized to act for the rights holder, with your physical or electronic signature.
Evidence checklist9 items
Timestamps & links
- Capture the full twitch.tv / clips.twitch.tv URL of each infringing clip or VOD — do not shorten or use a tracker.
- For clipped excerpts, give the precise start/end of the reused segment and one still frame from the VOD timeline.
- If the clip may be deleted before Twitch's team reviews, mirror the URL through archive.today / Wayback and attach the snapshot.
Original upload
- Link to your authorized copy — your own channel VOD, your official upload on YouTube, or the publisher release.
- If your original was on Twitch and has been removed, supply an archived snapshot (Wayback, archive.today) proving your prior publication.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) with supporting documentation.
- Twitch's DMCA notice policy mirrors the §512(c)(3) statement set — see the good-faith + perjury paste-able text in the copy-paste notice below.
Face / voice evidence
- For deepfake / impersonation clips, attach a side-by-side comparison still or transcript fragment showing the original face / voice vs the synthesized copy.
- Anchor on stream-archive timestamps and a known-livestream frame — Twitch's reviewers treat biometric-only evidence more sceptically than timestamped comparison evidence.
Response window
Twitch does not publish a formal SLA on the DMCA notice page. Complete §512 notices are typically acknowledged within a few business days; full VOD / channel removal and repeat-offender enforcement typically resolves within 1–2 weeks under normal volume. Treat any unacknowledged notice after 10 business days as needing a re-send to copyright-issues@twitch.tv with the prior Subject header referenced.
Escalation paths
- Re-send the complete §512 notice to copyright-issues@twitch.tv referencing the prior Subject header and ticket — keep the email-receipt record so the second notice is timestamped.
- For specific clips/VODs on Twitch, use the in-product report (click the offending clip → ⋯ → Report) so the trust & safety team sees a parallel flag alongside the DMCA notice.
- For persistent inaction on a US-jurisdiction claim, route to Twitch's designated-agent record in the US Copyright Office public directory; that path is what §512(g) restoration rights run through.
- Twitch clamps biometric / face-voice comparison as evidence less reliably than timestamps / original VOD archive / chain-of-custody — for deepfake claims, anchor the notice on timestamps, original VOD archive, and ownership proof rather than a voiceprint comparison.
Verified 2026-08-08
Where to file
File through Telegram’s in-app copyright intake bot @copyright_abuse_bot (start the bot, send /start, then paste the t.me permalink + work metadata into the DM) for the documented in-app DMCA path, or email abuse@telegram.org (subject header formatted per the copy-paste notice) for the long-standing mailbox route published at . For in-app content where you only want to flag the message itself, use the post / message menu → Report → Spam or Abuse to surface it to Telegram’s trust & safety team
Evidence required
- Direct link(s) to the infringing channel, group, or message (canonical t.me/<channel>/<id> permalinks).
- Description of the original work and a link to your authorized copy on a platform you control, or a published source.
- Your contact details (name, email, physical address) and a statement, under penalty of perjury, that you are authorized to act for the rights holder.
- Physical or electronic signature, plus country of residence — required for a §512-style escalation.
Evidence checklist7 items
Timestamps & links
- List each channel handle and the canonical t.me/<channel>/<id> permalink of the infringing message(s).
- For clips, capture the precise start/end of the reused segment and one still frame from the message.
- If the message has been deleted, attach an archived snapshot (archive.today, Wayback) before sending the report.
Original upload
- Link to your authorized copy (your own channel, a publisher’s release, or a public source).
- If your original is on another platform, include that URL so a reviewer can corroborate authorship.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) and attach supporting documentation.
- Include your full contact details (name, email, physical address) and a perjury statement with your signature — required for §512-style escalation.
Response window
Telegram’s published policy does not commit to a formal SLA — reports are triaged by the trust & safety team and typically acknowledged within a few business days, with full resolution (channel takedown, repeat-offender enforcement) taking longer under high volume. Treat any unacknowledged report after 7–10 business days as needing re-submission.
Escalation paths
- Re-send to abuse@telegram.org referencing the prior ticket; if the channel was deleted before you could capture it, attach an archived snapshot (archive.today, Wayback) of the t.me permalink.
- For repeated inaction on a US-jurisdiction copyright issue, route to a designated agent through the US Copyright Office public directory to invoke §512(g).
- Telegram does not accept biometric / face-voice comparison as a native evidence class — for deepfakes, anchor the report on timestamps, original-upload provenance, and ownership proof rather than a voiceprint comparison.
Verified 2026-08-23
Where to file
File through X's published copyright report form at (the documented DMCA intake — also reachable from the in-app Report flow on a Tweet: ⋯ → Report → It's suspicious or spam → Intellectual Property → Copyright). For tweets that impersonate you but don't reuse an underlying copyrighted work, use the impersonation intake at https://help.twitter.com/forms/impersonation instead — that queue is separate from copyright review. For mass cases the forms portal cannot capture, send the §512(c)(3) notice by email to copyright@twitter.com (X's published designated-agent inbox), with the form-envelope Subject header formatted per the copy-paste template below
Evidence required
- Direct URL(s) to the allegedly infringing Tweet(s) — the canonical https://x.com/<handle>/status/<id> or https://twitter.com/<handle>/status/<id> permalink, one per line.
- Description of the original work and a link to your authorized copy (your own X account, your cross-post on YouTube / Instagram / TikTok, or a publisher source).
- Your contact details — full legal name, monitoring email, country of residence, and (for a §512-style escalation) a physical address matching §512(c)(3)(D).
- A good-faith belief statement that the use is not authorized by the copyright owner, its agent, or the law.
- A statement, under penalty of perjury, that the information is accurate and you are authorized to act for the rights holder, with your physical or electronic signature.
Evidence checklist9 items
Timestamps & links
- Capture the canonical https://x.com/<handle>/status/<id> URL of each infringing tweet — do not shorten or use a tracker, and screenshot the tweet header (display name, @handle, follower count, timestamp).
- For cropped clip rips that use a segment of a longer video rather than a full rehost, supply the precise start/end of the reused segment and one still frame from the timeline.
- X deletes tweets within hours of certain report categories — mirror every offending URL through archive.today / Wayback before sending the notice, and attach the snapshot URL as a fallback link.
Original upload
- Link to your authorized copy — your own X account, your cross-post on YouTube / Instagram / TikTok, or the publisher release.
- If your original tweet has been deleted, supply an archived snapshot (Wayback, archive.today) proving your prior publication on the platform.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) with supporting documentation (publishing contract excerpt, license, or authorship declaration).
- Include your full contact details (legal name, monitoring email, country of residence) and a perjury statement with your signature — X's DMCA form mirrors §512(c)(3) and rejects notices without a complete contact block.
Face / voice evidence
- For deepfake / impersonation tweets, attach a side-by-side comparison still or transcript fragment showing the original face / voice vs the synthesized copy.
- Anchor on tweet-archive timestamps + the original-post provenance rather than a voiceprint comparison alone — X reviews biometric-only evidence more sceptically than timestamped comparison evidence.
Response window
X's copyright policy does not publish a formal SLA. Complete §512-style form reports are typically acknowledged within a few business days; full tweet / account removal and repeat-offender enforcement typically resolves within 1–2 weeks under normal volume. Treat any unacknowledged notice after 10 business days as needing a re-send via the same DMCA form with the prior case reference.
Escalation paths
- Re-send via the X copyright report form (https://help.twitter.com/forms/dmca) referencing the prior case ID; keep the confirmation page so the second notice is timestamped against the first.
- For mass cases the form cannot capture, email copyright@twitter.com with a Subject header formatted exactly as: "DMCA Notice — <@handle or work title> — <work title>". X's intake does not accept large attachments, so link archived snapshot URLs inline.
- For impersonation-only claims (a handle posing as you / your brand with no underlying copyright work to allege), do NOT file on the copyright form — use the impersonation intake at https://help.twitter.com/forms/impersonation and supply ID upload or brand documentation; that queue is separate from copyright review.
- For repeated inaction on a US-jurisdiction copyright claim, route to X's designated-agent record in the US Copyright Office public directory at https://www.copyright.gov/dmca-directory/ — that path is what §512(g) restoration rights run through when X wrongly restores after a counter-notice.
Verified 2026-08-17
Where to file
OnlyFans does not operate a copyright webform for third-party takedowns — file through Fenix International Limited's designated-agent intake published at (the parent-company abuse page), or email the parent-company abuse address documented in OnlyFans's Terms of Service under the "Reporting Intellectual Property Infringement" section. For pirated uploads of paid OnlyFans content rehosted on third-party platforms (pirate mirrors, scrapper sites, anonfiles-family hosts), file the §512(c)(3) notice to the third-party host's designated agent — Fenix will only act on content hosted on OnlyFans itself
Evidence required
- Direct URL(s) to the infringing material — the OnlyFans profile / post / DM URL when the imitation is on OnlyFans; the third-party https://… URL when the rehost lives off-platform.
- Description of the original work and a link to your authorized copy (your published profile, your verified creator-issued release, or a publisher source).
- Your contact details (full legal name, monitoring email, country of residence) and a statement, under penalty of perjury, that you are authorized to act for the rights holder.
- Physical address and physical or electronic signature — required for a §512-style escalation to the third-party host's designated agent.
Evidence checklist10 items
Timestamps & links
- Capture the full OnlyFans profile URL (onlyfans.com/<username>) or, when the offense is a third-party rehost, the direct https://… URL of the infringing page as it stands at the time of report.
- For clipped excerpts (a 30-second lift from your full-length clip), supply the precise start/end of the reused segment and one still frame from the page.
- Mirror every offending URL through archive.today / Wayback before sending the notice — pirate mirrors delete evidence within days, and the archived snapshot is what a reviewer will look at if the live URL is gone.
Original upload
- Link to your authorized copy (your published OnlyFans profile, your verified cross-post on another platform, or a publisher release).
- If your original has been removed from OnlyFans, supply an archived snapshot (Wayback, archive.today) proving your prior publication on the platform.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) with supporting documentation (verified-creator badge evidence, publishing contract excerpt, or authorship declaration).
- Include your full contact details (legal name, mailing address, country of residence) and a perjury statement with your signature — Fenix's intake mirrors §512(c)(3) and rejects notices without a complete address block.
Face / voice evidence
- For deepfake impersonation profiles (a profile on OnlyFans posing as you), attach a side-by-side comparison still or audio-track fingerprint showing the original face / voice vs. the synthesized copy.
- For voice-clone leaks on file hosts (audio tracks ripped from your paid DMs and re-uploaded to anonfiles-family hosts as 'voice pack'), attach a transcript of one of your authorized DMs alongside the offending audio file — timestamps + authorship provenance matter more than a voiceprint comparison alone.
- Reference Meta's / OnlyFans's policies on impersonation and biometric-identity proof where the deepfake is the dominant claim.
Response window
OnlyFans (Fenix International) does not publish a formal SLA on its IP / DMCA policy page. Reports routed to the Fenix abuse intake are typically triaged within a few business days; full removal + repeat-offender enforcement typically resolves within 1–2 weeks under normal volume. For third-party rehosts (the dominant piracy vector for leaked OnlyFans content), the host's SLAs drive the response window — treat the third-party host's abuse inbox as the primary filing path, not the OnlyFans intake.
Escalation paths
- Re-send the §512 notice to the Fenix abuse intake referenced in OnlyFans's Terms of Service (under "Reporting Intellectual Property Infringement") with the prior Subject header / ticket reference — keep the email-receipt record so the second notice is timestamped.
- For leaked OnlyFans content rehosted on third-party platforms, file the §512 notice to the third-party host's designated agent. Look up the WHOIS for the offending domain (whois.domaintools.com / whois.icann.org) to identify the registrar, then move up to the hosting provider's abuse contact (Cloudflare / Amazon / Google abuse address) and cc the registrar on the same mail.
- For deepfake / impersonation OnlyFans profiles (a profile on OnlyFans itself posing as you, with face-cam / voice-cloned audio tracks), file ON OnlyFans through Fenix's abuse intake with biometric evidence and timestamps of the impersonating posts — this is distinct from a third-party rehost and the queue paths are separate.
- For repeated inaction on a US-jurisdiction copyright claim, route to a designated agent through the US Copyright Office public directory (https://www.copyright.gov/dmca-directory/) — that path is what §512(g) restoration rights run through when the host wrongly restores after a counter-notice.
Verified 2026-08-01
Where to file
For Mega.nz, use the DMCA webform at (the contact / DMCA section of the help center) or email dmca@mega.nz. For anonfiles and the anonfiles-family hosts (filebin, megaupload-style mirrors), email support@anonfiles.com — there is no formal webform. For streamable embeds, file through the TOS-violation page at https://streamable.com/abuse
Evidence required
- Direct URL(s) to the infringing file or embed (Mega public link, anonfiles URL, or the streamable.com/<id> embed).
- SHA-256 hash of the file when you can compute it — Mega’s DMCA team cross-references hashes against their storage layer to confirm a match.
- Description of the original work and a link to your authorized copy (your own channel, publisher, or registered source).
- Your contact details (name, email, physical address) and a statement, under penalty of perjury, that you are authorized to act for the rights holder.
- Physical or electronic signature; Mega asks for the country of residence, mirroring §512(c).
Evidence checklist7 items
Timestamps & links
- Capture the direct URL of each infringing file or embed (Mega public link / streamable.com/<id> / anonfiles URL) as it stands at the time of report.
- For video clips, capture the start/end of the reused segment and one still frame; for streamable embeds include the embedding page URL as well.
Original upload
- Link to your authorized copy on a platform you control or a published source.
- If your original has been removed, attach an archived snapshot (Wayback, archive.today) before filing.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) and attach supporting documentation.
- Include your physical address and perjury statement with signature; Mega’s form requires country of residence.
- Compute and attach a SHA-256 hash of the infringing file when you can — Mega cross-references hashes against storage to confirm a match; this is the single highest-leverage datum for file-host takedowns.
Response window
None of these hosts publish a formal SLA. Mega commonly acknowledges DMCA reports within a few business days; anonfiles-family and streamable are inconsistently staffed and frequently take longer, with no public commitment on counter-notification turnaround. Treat this group as the slowest tier in the KB — pre-archive evidence before filing.
Escalation paths
- For Mega, re-send to dmca@mega.nz referencing the prior ticket; Mega is NZ-incorporated and the designated-agent contact listed in their ToS is the escalation path for stalled takedowns.
- For anonfiles-family and streamable, re-send to support@anonfiles.com / https://streamable.com/abuse with the prior ticket reference; if mirrored to an upstream CDN or registrar, escalate to that operator’s abuse contact in parallel.
- This group cannot reliably review biometric / voice comparison as filed evidence — anchor on timestamps, original-upload provenance, ownership proof, and ideally a SHA-256 hash of the file.
Verified 2026-08-09
Where to file
There is no published webform for most long-tail pirate mirrors and aggregators — the filing path is the hosting provider’s designated §512(c) agent. Look up the WHOIS for the offending domain (whois.domaintools.com / whois.icann.org / whois.iana.org) to identify the registrar, then move up to the hosting provider’s abuse contact (often a Cloudflare / Google / Amazon / OVH abuse address). Send the DMCA §512(c)(3) notice to that abuse inbox as a plain-text email; cc the registrar’s abuse@ contact in the same mail. When the offending content is on a Cloudflare-fronted site that won’t reveal the origin IP, follow up with a Cloudflare Trust & Safety abuse report at alongside the host’s notice — Cloudflare’s abuse queue has its own SLAs and can pressure the underlying origin
Evidence required
- Direct URL(s) to the infringing material (the exact https://… page or hosted file on the offending site), plus the WHOIS record (Registrar, Name Server, Registrant Org, Creation Date) of the offending domain.
- Archived snapshot of each infringing URL through archive.today (and Wayback Machine as a backup) — long-tail hosts frequently delete the infringing material within days of receiving a notice, leaving the reviewer without proof.
- Description of the original work and a link to your authorized copy (your channel, official upload, or publisher source).
- Your full contact details (legal name, mailing address, monitoring email, country of residence) — mirroring §512(c)(3)(D).
- A good-faith belief statement and the §512(c)(3) perjury + accuracy statement, together with the registration timestamp of your original work.
Evidence checklist7 items
Timestamps & links
- Capture the full https://… URL of each infringing page (or file URL on the offending host) as it stands at the time of report — long-tail sites rotate paths aggressively.
- For clipped excerpts, give the precise start/end of the reused segment and one still frame from the page.
- Mirror every infringing URL through archive.today / Wayback before sending the notice — long-tail hosts delete evidence within days, and the archived snapshot is what a reviewer will look at if the live URL is gone.
Original upload
- Link to your authorized copy on a platform you control or a published source.
- If your original has been removed from its original platform, supply an archived snapshot (Wayback, archive.today) proving your prior publication.
Ownership proof
- State your relationship to the work (creator, licensee, authorized agent) and attach supporting documentation (publishing contract excerpt, registration certificate, or authorship declaration).
- Include your full mailing address, country of residence, and perjury statement with signature — long-tail hosts treat the address block as the single strongest signal of a legitimate filer.
Response window
Most long-tail hosts have no published SLA. Abuse inboxes at Cloudflare, Google Cloud / Workspace, AWS, and OVH typically acknowledge within 2–5 business days; smaller hosts are best-effort and acknowledgments run 5–15 business days. Treat any unacknowledged notice after 7 business days as needing a re-send; if the abuse contact bounces, fall back to the registrar’s abuse@ and the US Copyright Office designated-agent directory.
Escalation paths
- Re-send to the same host abuse inbox with the prior Subject header and the email-receipt ID from the initial notice — keep the mail-thread so the second notice is timestamped and visibly referenced.
- Escalate to the registrar’s abuse@ (Namecheap, GoDaddy, Porkbun, …) and cc the US Copyright Office designated-agent directory (https://www.copyright.gov/dmca-directory/) — registrars hold contractual leverage over their resold hosting in a way the host’s own abuse team often does not.
- For Cloudflare-fronted sites that won’t reveal the origin host, file a parallel Trust & Safety report at https://abuse.cloudflare.com/ — Cloudflare’s abuse queue operates in parallel with the host’s and has its own SLA.
- For hosting-as-a-service providers (AWS Abuse, Google Cloud abuse@, OVH abuse@), the provider’s TOS often bans the infringing use even when the customer’s app has no published policy; address the abuse email at the provider, not the app.
- On US-hosted mirrors, the §512(g) restoration path runs through the US Copyright Office’s designated-agent directory; if the host wrongly restored after a counter-notice, that is the escalation backstop.
Showing 10 of 10procedures. Response windows are per each platform's published policy and may change — verify against the source before filing.
Need a step-by-step filing guide?
Filing walkthroughs by platform
Three-platform walkthroughs for YouTube, TikTok, and Instagram, with the exact webform to open and the fields to fill in. Cross-linked from the knowledge base so the procedure and the form stay side-by-side.
Suggest a platform
Missing a takedown target?
Tell us the platform you keep losing work to — Twitch, Discord, a niche file host, an emerging creator economy app — and we'll research the public takedown procedure, add it to this knowledge base, and route it through Snareline's filing agent.