Takedown Policy

Last updated: 2026-04-26 · Effective: 2026-04-26

This policy describes how to request the removal of content from the Amitte registry, and how we process those requests.

What this covers

You can request takedown of any published skill, agent, or MCP server entry on grounds including:

• Violation of the Content Policy
• Copyright infringement (DMCA or equivalent in your jurisdiction)
• Trademark infringement
• Defamation, harassment, or doxxing
• Personal data published without consent (privacy / GDPR Article 17)
• Court order or government takedown notice
• Security risk (e.g. a skill that turned out to leak credentials)

If you're the publisher and want to remove your own content, see "Publisher self-takedown" below — no formal request needed.

How to file a takedown request

We accept three intake channels:

1. GitHub issue (preferred for non-sensitive cases)

Open an issue at github.com/amitte-ai/amitte/issues/new using the Takedown request template (or tagged takedown if no template exists yet).

Include:

• Skill ID and version (namespace/name@version)
• The grounds (Content Policy violation, copyright, etc.)
• A description of the harm or violation
• For copyright claims: a statement that you have a good-faith belief the use is unauthorized, and that the information is accurate

2. Email

For sensitive cases (CSAM, ongoing harassment, security exploitation), email takedown@amitte.com with the same information.

For CSAM specifically, you may also report directly to the National Center for Missing & Exploited Children (NCMEC) at report.cybertip.org.

3. DMCA notice (US copyright claims)

Send a notice that complies with 17 U.S.C. § 512(c)(3) to dmca@amitte.com, including:

1. A physical or electronic signature of the copyright owner or authorized agent.
2. Identification of the copyrighted work claimed to be infringed.
3. Identification of the material claimed to be infringing (skill ID, version, URL).
4. Your contact information.
5. A statement that you have a good-faith belief that the use is not authorized.
6. A statement, under penalty of perjury, that the information is accurate and you are authorized to act.

Counter-notices follow the same statutory format and may be sent to the same address.

Our response timeline

Severity	First-response SLA	Resolution SLA
Critical (CSAM, active credential theft, court order)	24 hours	48 hours, content removed in interim
High (ongoing harassment, doxxing, security exploit)	48 hours	7 days
Standard (copyright, trademark, content-policy violation)	5 business days	30 days
Low (quality, spam, low-stakes disputes)	14 days	as time permits

These are targets. We're a small team. Critical items are paged 24/7; everything else is best-effort within the SLA.

What removal looks like

When we remove content, we:

1. Mark the skill version revoked in the database. The version becomes inaccessible via /v1/fetch and is excluded from search.
2. Delete the artifact from object storage within 24 hours of revocation.
3. Add the version to the public revocation feed at /v1/revocations.json so SDK consumers can update their caches.
4. Notify the publisher by email (if we have one) with the reason and any next steps.
5. Log the action to an audit trail accessible to the publisher and to authorized regulators on request.

Removed content is not deleted from immutable system backups within the 7-day backup window, but is not accessible via the registry.

Appeals

Publishers whose content has been removed can appeal:

1. Email policy@amitte.com within 14 days of the takedown notification.
2. Include the skill ID, version, and a written response to the takedown grounds.
3. We will review with someone other than the original decision-maker (where possible) and respond within 14 days.

Appeals decisions are final. Repeat appeals on substantively similar content will not be re-reviewed.

For DMCA counter-notices, US law sets the procedure: we'll restore the content 10–14 business days after a valid counter-notice unless the original claimant files a court action.

Publisher self-takedown

You can remove your own content at any time without filing a request:

• Make a skill private (when visibility ships): /me → skill row → Make Draft / Make Private.
• Revoke a version: from /me, click into the skill, choose Revoke version. Confirm.
• Delete an entire skill: same flow with Delete skill.

Self-revocation is immediate. Versions remain in the immutable revocation feed (so consumers know to drop their caches).

Bad-faith takedown requests

Filing a takedown request you know to be false is grounds for account suspension and, for DMCA notices, may expose you to liability under 17 U.S.C. § 512(f).

Transparency

We publish a quarterly transparency report summarizing the volume of takedown requests, source (publisher / third party / government), and resolution. The first report will be published once we have enough data to anonymize meaningfully.

Contact

Channel	Use for
takedown@amitte.com	Standard takedowns
dmca@amitte.com	DMCA notices and counter-notices
policy@amitte.com	Appeals and policy questions
security@amitte.com	Security-related takedowns (vulnerabilities in published skills)
GitHub issues tagged takedown	Non-sensitive cases