DMCA Procedure

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:

3. Filing a takedown notice

To be effective under § 512(c)(3), a notice must contain all six of the following elements. Notices missing any element will be replied to with a description of the deficiency; the response window does not begin until a substantially compliant notice is received.

1. A physical or electronic signature of the person authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.
2. Identification of the copyrighted work claimed to have been infringed (or, if multiple works at a single online site are covered by a single notification, a representative list of the works at that site).
3. Identification of the material claimed to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled. For socials.download captures, please provide the capture session ID, the source URL, and (if known) the operator account email or capture ID. Including the SHA-256 hash from the capture sidecar materially speeds processing.
4. Information reasonably sufficient to permit us to contact the complaining party, including an address, telephone number, and (if available) an email address.
5. A statement that the complaining party has a good-faith belief that the use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law.
6. A statement that the information in the notification is accurate, and under penalty of perjury, that the complaining party is authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.

Send the notice to dmca@socials.download. We acknowledge receipt of every notice within one business day with a tracking ID assigned to the case.

4. 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.
• 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.

5. 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 dmca@socials.download referencing the original takedown tracking ID.

6. 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.

7. 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.

8. 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 legal@socials.download; 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.

9. 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.

10. Contact

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