DMCA Copyright Notice and Takedown Policy

Effective Date: May 25, 2026

Global Data Store LLC respects the intellectual property rights of others and expects users of OntoBoom (the "Service") to do the same. We respond to clear notices of alleged copyright infringement that comply with the DMCA.

1. How to Submit a Takedown Notice

If you believe that content on OntoBoom — including an ontology manifest, README, description, or review — infringes a copyright you own or are authorized to enforce, send a written notice to our designated agent containing all of the following:

1. A physical or electronic signature of the copyright owner or a person authorized to act on their behalf.
2. Identification of the copyrighted work claimed to have been infringed (e.g., the title, registration number, or URL of the original work).
3. Identification of the material that is claimed to be infringing and information sufficient to locate it on the Service. The most useful form is the full canonical URL, for example https://hub.ontoboom.com/@namespace/slug/versions/x.y.z or https://mcp.ontoboom.com/o/@namespace/slug@x.y.z.
4. Your name, mailing address, telephone number, and email address.
5. A statement that you have 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 made under penalty of perjury that the information in the notice is accurate and that you are the copyright owner or authorized to act on behalf of the copyright owner.

2. Designated Agent

Send takedown notices to the designated agent listed below. We will respond to properly-formatted notices within a reasonable time, typically within 10 business days.

• Company: Global Data Store LLC
• Designated Agent: Copyright Agent, Global Data Store LLC
• Submit via: /support (subject line: "DMCA Takedown Notice")
• Website: globaldatastore.com

3. What Happens After We Receive a Notice

When we receive a properly-formatted notice, we will:

• Remove or disable access to the allegedly infringing material — for Hub versions, we will yank the version (mark it unavailable) and remove it from public feeds and search;
• Notify the namespace owner of the takedown and the substance of the notice (with your contact details redacted unless required by law);
• Track the takedown against the user's account for repeat-infringer enforcement.

4. Counter-Notice

If you are the user whose content has been removed and you believe the removal was the result of a mistake or misidentification, you may file a counter-notice. A counter-notice must include:

1. Your physical or electronic signature.
2. Identification of the material that has been removed and the location at which the material appeared before removal.
3. A statement under penalty of perjury that you have a good-faith belief that the material was removed as a result of mistake or misidentification.
4. Your name, address, and telephone number, and a statement that you consent to the jurisdiction of the federal court for the judicial district in which your address is located (or, if outside the U.S., the U.S. District Court for the District of Delaware), and that you will accept service of process from the person who provided the original notice or that person's agent.

We will forward your counter-notice to the original complainant and, if we do not receive notice of a court filing within 10–14 business days, we may restore the material.

5. Repeat-Infringer Policy

Consistent with the DMCA and our Terms of Service, we maintain a policy to terminate, in appropriate circumstances, the accounts of users who are determined to be repeat copyright infringers.

6. Misrepresentations

Under 17 U.S.C. § 512(f), any person who knowingly materially misrepresents in a notice or counter-notice that material is infringing or was removed by mistake may be liable for damages. Please do not submit a notice unless you have a good-faith basis to do so.

7. Hub-Specific Considerations

Because published Hub versions are immutable, our preferred remediation is to yank the affected version rather than delete it — the record persists (marked unavailable) so that any downstream consumer that took a hard dependency on the checksum receives a clear signal rather than a 404. The yanked version is removed from public feeds, search, and the canonical URL responds with a 404 / version-not-found for pulls and MCP requests. Subsequent versions in the same catalog remain available unless they are independently the subject of a notice.