Copyright and DMCA

Notices under 17 U.S.C. §512 should be sent to:

Registering that agent with the Copyright Office is an operator prerequisite before relying on safe-harbor protection. Until the directory entry exists, send notices to the email above anyway — we will still act on them.

A valid notice should include the information 17 U.S.C. §512(c)(3) requires, including:

• your physical or electronic signature;
• identification of the copyrighted work claimed to be infringed;
• identification of the material and a URL or hostname/image path on Obiquity sufficient for us to find the route (for example https://registry.example.com/v2/myimage/manifests/latest);
• your name, address, telephone number, and email;
• a statement that you have a good-faith belief that use of the material is not authorized by the owner, its agent, or the law;
• a statement that the information in the notice is accurate, and under penalty of perjury that you are authorized to act on behalf of the owner.

We may ignore incomplete notices. Because we do not store layers, "removing" material means disabling the Obiquity domain or route, not deleting files at Docker Hub or another upstream. We may share your notice with the tenant who configured that domain.

1. We log receipt and identify the tenant, hostname, and route.
2. If the notice is complete and identifies material we can disable, an operator deletes the route or domain (and may suspend the tenant) using the admin panel, with the reason recorded in the audit log.
3. We aim to act on complete notices promptly, typically within one business day of receipt.
4. We may notify the tenant so they can file a counter-notice if they believe the claim is mistaken.

That timeline is an operational target, not an SLA and not a waiver of any defense. We may act faster on obvious malware or CSAM reports — those should go to abuse as well.

If you are a tenant whose route was disabled and you believe the material is not infringing, you may send a counter-notice to dmca@obiquity.io with the elements in 17 U.S.C. §512(g), including your contact information, identification of the disabled material, a good-faith statement under penalty of perjury that the disablement was a mistake or misidentification, and consent to jurisdiction of the federal district court for your address (or for Delaware if you are outside the United States). We may restore the route after the statutory waiting period unless the complainant seeks a court order. We may still refuse to restore if the use independently violates the Acceptable Use Policy.

We terminate, in appropriate circumstances, tenants who are repeat infringers. As a working rule, two or more substantiated copyright notices in a twelve-month period, or a clear pattern of infringement (including ignoring prior disablements), will result in account suspension and, if the pattern continues, termination. We may terminate sooner for egregious or willful infringement. Strikes are tracked via the admin audit log on the tenant and domain, not a public score.

Trademark, impersonation, and typosquatting reports can use abuse@obiquity.io. We may disable a hostname that is being used to pass off another party's project or registry.