DMCA Procedure

Last updated: May 5, 2026

File a takedown notice

The form below collects every element required under § 512(c)(3), generates a tracking ID and SHA-256 fingerprint at the moment of submission, and routes the notice to our designated agent automatically. Notices missing any required field are rejected at the form level, so the response window does not start until a substantively complete notice is on file.

The form is the fastest path. Form submissions are structured, validated, and triaged automatically, which lets us act on substantively complete notices typically within hours rather than the published 24-to-48-hour ceiling. Email submissions to the contact address at the bottom of this page reach the same designated agent but are processed manually, which adds a queue step and uses the full 24-to-48-hour window. Use the form unless your situation requires email submission.

When we act on a valid notice, the targeted material is removed from the operator’s archive AND the URL pattern is added to our intake blocklist so the same content cannot be captured again by any operator going forward. Each block is recorded in the audit log against your tracking ID, so a single notice covers both the existing artifact and any future attempts.

After you submit, you’ll receive: (a) an immediate on-page tracking ID and notice hash, (b) an email acknowledgement within one business day, (c) action on the targeted material within the published window, and (d) updates if the affected operator files a counter-notification under § 512(g)(2).

Complainant
Copyrighted work
Allegedly infringing material
Statutory affirmations (required)

Submitting transmits this notice to contact@socials.download and creates a tracking ID you can reference in correspondence.

1. Summary

socials.download responds to copyright takedown notices under the Digital Millennium Copyright Act, 17 U.S.C. § 512 (the “DMCA”). Valid notices are acted on within 24 to 48 hours of receipt. Counter-notifications are processed under 17 U.S.C. § 512(g) within the statutory window. We maintain a tamper-evident audit log of every notice received, every action taken in response, and every counter-notification filed. Repeat-infringer accounts are terminated.

2. Designated agent

Notices must be sent to our designated agent for receipt of notifications of claimed infringement:

Designated Agent, DMCA
socials.download
Reach the agent via the contact email at the bottom of this page. A physical mailing address for service is available on request through the same address.

3. Response timeline

  • Within 1 business day: acknowledgement of receipt and assignment of a takedown tracking ID.
  • Within 24 hours of receipt of a substantially compliant notice: the targeted material is removed or access is disabled and the audit-log entry is written. The 24-hour target is the operational standard; in some cases (notice received outside business hours, ambiguity in the identified material) the action is taken within 48 hours and the audit log records the reason for the delta.
  • At takedown: the URL pattern from the notice is added to our intake blocklist so the same content cannot be captured again by any operator going forward. The block persists until the matter is withdrawn, successfully counter-notified, or otherwise resolved. The blocklist entry is itself audit-logged against the takedown tracking ID.
  • Promptly upon takedown: the affected operator is notified by email with a copy of the notice (with the complainant’s personal contact information redacted unless the law requires otherwise), the tracking ID, and instructions for filing a counter-notification under § 512(g) if they believe the takedown was in error.
  • If a valid counter-notification is filed (§ 512(g)(2)): we forward it to the complainant and, unless the complainant notifies us within 10–14 business days that they have filed a court action seeking a restraining order, we restore access to the material.

4. Filing a counter-notification

To be effective under § 512(g)(3), a counter-notification must contain all four of the following:

  1. A physical or electronic signature of the operator.
  2. Identification of the material that has been removed or to which access has been disabled and the location at which the material appeared before it was removed (the capture tracking ID is sufficient).
  3. A statement under penalty of perjury that the operator has a good-faith belief that the material was removed or disabled as a result of mistake or misidentification of the material.
  4. The operator’s name, address, and telephone number, and a statement that the operator consents to the jurisdiction of the federal district court for the judicial district in which the operator is located (or, if the operator is outside the United States, for any judicial district in which the service provider may be found), and that the operator will accept service of process from the complainant or an agent of the complainant.

Send the counter-notification to the contact email at the bottom of this page, referencing the original takedown tracking ID.

5. Repeat-infringer policy (§ 512(i))

We maintain a written repeat-infringer policy and we enforce it. An operator who accumulates three substantiated takedowns within a rolling 12-month period is subject to account termination. “Substantiated” means a notice that was complete, was not the subject of a successful counter-notification, and was not the subject of a court order finding the use lawful. Termination is irreversible: the case archive is deleted within 24 hours; the audit log is retained as required by applicable record-keeping obligations.

Knowingly material misrepresentations in a takedown notice or a counter-notification are themselves grounds for liability under § 512(f) and may result in account suspension regardless of which side made the misrepresentation.

6. Audit log of takedowns

Every takedown action against the Service is recorded in a tamper-evident audit log. For each takedown the log contains:

  • The takedown tracking ID.
  • The UTC timestamp of receipt of the notice.
  • The UTC timestamp of the takedown action.
  • The hash of the notice as received (so the original document can be reconstructed and verified).
  • The hash of the affected artifact (so the artifact subject to the takedown is unambiguously identified).
  • Any counter-notification filed, with its own timestamp and hash.
  • The final disposition (taken down and not restored / taken down and restored after counter-notification / refused as deficient / withdrawn).

Audit-log entries are immutable in the ordinary course; corrections are made by appending new entries that reference the entry being corrected. The log is available to lawful counsel under the procedure documented in our Compliance Policy.

7. Non-DMCA takedown requests

Some takedowns arise from rights other than copyright: privacy, defamation, harassment, GDPR / data-protection erasure rights, court orders, or platform-policy violations. Send those to the contact email at the bottom of this page; we evaluate and act on credible requests with the same audit-log discipline as DMCA notices. Time-to-action depends on the nature of the request. Most are resolved within the same 24–48 hour window; complex matters (overbroad requests, jurisdictional issues, requests we have reason to challenge) are tracked and disclosed in our compliance reporting.

8. Hosting context

Free-tier captures are not hosted by us; they stream through the worker and are deleted from worker memory within seconds of delivery. Paid-tier captures are stored in the operator’s case archive for the published retention window of the plan (Pro: 30 days; Studio: 90 days), then permanently deleted. Takedown actions remove the artifact from object storage; the audit-log entry referencing the takedown persists.

9. Contact

All correspondence (DMCA takedown notices, counter-notifications, subpoenas, preservation requests, non-copyright takedowns, and privacy / data-protection requests as they relate to a specific capture): contact@socials.download.