Establishing secure connection…Loading editor…Preparing document…

Intellectual Property Takedown Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

INTELLECTUAL PROPERTY TAKEDOWN REQUEST

Parties

Requesting Party (Rights Holder):

Service Provider (Host/Platform/Agent):

WHEREAS (Recitals)

WHEREAS, the Requesting Party asserts that it owns or is authorized to act on behalf of the owner of certain intellectual property rights in the material identified below; and

WHEREAS, the Requesting Party has identified material that it reasonably believes infringes those rights and is accessible via the Service Provider's systems or platform; and

WHEREAS, the parties wish to document the Requesting Party's request for removal or other remedial action and the Service Provider's obligations, fees and procedures related to processing such request.

Scope of Work

The Service Provider shall, upon receipt of this completed Request and any required supporting documentation, undertake the following actions:

Description of Alleged Infringement

Payment Terms

The Requesting Party agrees to pay the Service Provider for takedown processing as follows:

Term and Termination

Effective Date:    Term Expires:

Either party may terminate this Request for material breach if the other party fails to cure a breach within the notice period set forth above. Termination does not relieve the Requesting Party of payment obligations for work already performed.

Confidentiality

All non-public information exchanged in connection with this Request, including evidence, account details, and any investigation results, shall be treated as Confidential Information. Neither party shall disclose Confidential Information except as required by law, regulation, or to enforce rights under this Request. The obligation of confidentiality survives termination for a period of three (3) years.

Certification and Good Faith Declaration

The Requesting Party certifies, under penalty of perjury, that it has a good faith belief that use of the material described above is not authorized by the rights owner, its agent, or the law, and that the information in this Request is accurate and, under penalty of perjury, the Requesting Party is authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.

Check to acknowledge certification

Governing Law

This Request and any dispute arising out of or relating to it shall be governed by the laws of the State of , without regard to its conflict of law principles. Venue for any action shall lie in the county of .

Entire Agreement

This Request constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous communications and proposals, whether oral or written. Any amendment must be in writing and signed by authorized representatives of both parties.

Requesting Party (Print Name):

By:

Date:

Service Provider (Print Name):

By:

Date:

Enter text✕

What an Intellectual Property Takedown Request Is

An Intellectual Property Takedown Request is a formal written notice used to report alleged infringement of copyrighted works, trademarks, or other IP on a third-party platform or service. The request identifies the IP owner or authorized agent, describes the copyrighted material, pinpoints the location of the allegedly infringing content, and includes a statement of good faith and signature to meet platform or statutory requirements.

Why this request matters for protecting your rights

A clear takedown request helps preserve legal rights, speeds removal of infringing content, and creates an evidentiary paper trail. It documents the claimant’s good-faith belief and the specific harm, which platforms generally require to act promptly under notice-and‑takedown procedures.

Why this request matters for protecting your rights

Who typically prepares and serves these takedown requests

Rights holders and their agents prepare takedown requests when online content appears to infringe intellectual property.

  • Independent creators and copyright owners who control the work and can attest to ownership and infringement.
  • In-house or outside counsel acting as authorized agents submitting notices on behalf of rights holders.
  • Online platforms, hosting providers, and ISPs who receive and process infringement notices under platform policies.

Proper preparation by the authorized party reduces the chance of counter-notice and supports downstream enforcement if removal is contested.

Core elements a professional takedown request should include

A complete request contains specific factual and contact information, an accurate identification of the copyrighted material, and a signed statement under penalty of perjury. These elements meet most platform forms and statutory notice standards.

Owner ID

Name and legal entity of the rights holder plus proof of ownership or an authorization statement from the owner explaining standing to file.

Infringing Location

Exact URLs or other precise locations of the alleged infringing content so platforms can locate and remove material without undue burden.

Original Work

Clear identification of the copyrighted work or trademarked material, including registration numbers if available and a brief description of the original.

Good-Faith Statement

A short declaration that the filer believes in good faith the use is unauthorized, matching notice-and-takedown expectations under platform policy and statute.

Contact Details

Phone, email, and mailing address for follow-up, and the name of the authorized representative if submitted on behalf of the rights holder.

Signature

Handwritten or electronic signature with date and a statement under penalty of perjury to validate the request and deter misrepresentations.

Security and compliance considerations for takedown records

Encryption: TLS 1.2/1.3 in transit
Data at rest: AES-256 encrypted storage
Audit trails: Detailed signing and action logs
Certifications: SOC 2 Type II, ISO 27001
Legal compliance: ESIGN and UETA support
Health data: HIPAA available with BAA

Step-by-step completion process

Follow these steps to prepare an accurate, platform-ready takedown request and reduce the risk of rejection or counter-notice.

  • 01
    Identify work: Describe the original IP and any registration details.
  • 02
    Locate infringing content: List exact URLs, timestamps, or file identifiers.
  • 03
    Provide contact info: Include authorized agent name, phone, and email.
  • 04
    Sign and date: Sign under penalty of perjury and add the date.

Configuring an online submission workflow

Use a consistent digital workflow to collect claim details, owner authorization, and an auditable signature for each takedown.

Field Configuration
Claimant Name Required text field, verify exact spelling
Proof Upload File field, accept PDF/JPG, require ID or registration
Infringing URLs Repeatable field, validate URL format
E-signature Required signature field with date

Typical notice-and-takedown flow

This sequence outlines how a properly formed request moves from submission to platform action and potential dispute.

  • Submit notice: Rights holder sends the takedown request to the host.
  • Platform review: Platform validates and locates the reported content.
  • Removal action: Host removes or disables access to content.
  • Counter-notice option: Respondent may submit a counter-notice to contest removal.

Technical and platform requirements to expect

Different hosting platforms require specific fields, proof levels, and authentication before processing a takedown.

  • File formats: PDF preferred for attachments
  • Authentication: Email verification or account login
  • Recordkeeping: Platforms retain removal logs

Confirm the recipient platform’s policy language and required declarations before submitting to prevent rejections or requests for supplementary information.

Typical timing and response expectations

Timeframes vary by platform and law; file promptly and track dates to preserve rights and comply with statutory windows.

Submission timing:

Send the notice as soon as infringement is discovered.

Platform action:

Hosts usually act expeditiously, often within 24–72 hours.

Counter-notice window:

Respondent may file a counter-notice; statutory period is about 10–14 business days under 17 U.S.C. §512.

Preserve evidence:

Capture screenshots and metadata promptly to support enforcement.

Litigation considerations:

Statute of limitations and litigation deadlines vary; consult counsel for timing.

Risks and legal consequences of incorrect claims

Perjury exposure: False statements risk criminal or civil penalties
Statutory damages: Exposure to damages if misrepresentation proven
Counterclaims: Respondent may assert misuse or wrongful takedown
Fee liability: Court costs and attorney fees possible
Reputational harm: Public disputes can damage brand credibility
Lost evidence: Delayed or improper notices can undermine claims

Common preparation errors to avoid

  • Submitting vague descriptions that do not clearly identify the copyrighted work or the infringing material leads to rejection or delay.
  • Providing incomplete or malformed URLs or file references prevents platforms from locating the content and may trigger requests for clarification.
  • Filing without proof of authorization when acting as an agent often results in requests for additional documentation and processing delays.
  • Omitting a signature, date, or required penalty-of-perjury language causes many platforms to deem a notice invalid.

Practical examples of takedown scenarios

These examples illustrate how rights holders convert facts into a complete takedown request that platforms can act on quickly.

Independent Creator

A photographer discovers unauthorized images on a marketplace page

  • Files exact image URLs and a registration number
  • The platform removes the content after receipt and requests proof of ownership for recordkeeping and reinstatement control.

Software Vendor

A SaaS vendor finds stolen code snippets in a competitor's repo

  • Submits code excerpts, repo locations, and license evidence
  • The host disables access pending verification and the vendor preserves logs for potential DMCA and contract enforcement.

Who is authorized to sign and submit

In-House Counsel

An attorney employed by the rights holder may sign as an authorized agent when acting within the scope of retained authority; include firm contact details and evidence of representation.

Authorized Representative

A named business officer or agent with written authorization can submit notices; attach a short authorization statement or corporate resolution showing authority to act.

Tips to prepare accurate, defensible takedown requests

Follow a consistent checklist and preserve supporting evidence to reduce processing time and strengthen later enforcement options.

Use precise URLs
Provide full, timestamped URLs and any file identifiers. Precise locations let platforms act immediately and reduce back-and-forth requests for clarification.
Attach proof
Include registration certificates, original files, or timestamps that demonstrate prior authorship or ownership; this shortens verification time and supports future litigation.
Retain records
Keep copies of submission confirmations, platform responses, and any counter-notices so you can document the administrative history if disputes escalate.
Be factual and measured
Avoid hyperbole in the notice. Stick to verifiable facts, avoid speculative assertions, and include a concise statement of good faith belief.

eSignature vendor pricing and capability snapshot for takedown workflows

Comparing eSignature plans helps determine cost and compliance fit for submitting and retaining signed takedown requests; signNow is listed first per vendor comparison requirements.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year No cap No cap No cap

Frequently asked questions and answers

Answers to common questions about preparing, submitting, and defending Intellectual Property Takedown Requests.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users