Takedown Policy
Last updated: June 11, 2026
In plain English: If something on the registry infringes your rights or harms you, tell us — by email or GitHub issue — with the skill ID and the grounds. We aim to respond within 7 days (faster for critical harm); we're a small team and these are best-effort targets. Publishers can contest removals with a counter-notice. Every takedown is counted in the public transparency report.
This policy describes how to request removal of content from the Amitte registry and how we process those requests.
Who can file
- Rights holders — copyright or trademark owners (or their authorized agents).
- Affected parties — people harmed by the content: targets of doxxing, harassment, defamation, or publication of personal data without consent.
- Anyone — for Content Policy violations (malware, prompt-injection payloads, secrets, CSAM) or security risks. You don't need to be personally affected to report dangerous content; the "Report" button on every detail page also works.
- Publishers — to remove their own content. No formal request needed; see "Publisher self-takedown" below.
What to include
Whatever the channel, include:
- Skill ID and version —
namespace/name@version(or the URL). - Grounds — Content Policy violation, copyright, trademark, privacy, defamation, security risk, court order.
- Description of the harm or violation — specific enough that we can verify it.
- Your relationship to the issue — rights holder, affected party, or third-party reporter.
- Contact information — so we can follow up and notify you of the outcome.
- For copyright claims — a statement that you have a good-faith belief the use is unauthorized, and that your information is accurate. For formal US DMCA notices, follow 17 U.S.C. § 512(c)(3) (signature, identification of the work and the infringing material, contact info, good-faith statement, accuracy statement under penalty of perjury).
How to file
| Channel | Use for |
|---|---|
| takedown@amitte.com | Standard takedowns; required for sensitive cases (CSAM, ongoing harassment, active exploitation) |
| dmca@amitte.com | DMCA notices and counter-notices |
GitHub issue tagged takedown at github.com/amitte-ai/amitte/issues | Non-sensitive cases |
For CSAM you may also report directly to NCMEC at report.cybertip.org.
Response timeline
We are a small team; these are best-effort targets, not contractual guarantees. Our default commitment is a first response within 7 days. Severity moves things up:
| Severity | First response | Resolution target |
|---|---|---|
| Critical (CSAM, active credential theft, court order) | 24 hours | 48 hours; content pulled in the interim |
| High (ongoing harassment, doxxing, security exploit) | 48 hours | 7 days |
| Standard (copyright, trademark, content-policy violation) | 7 days | 30 days |
| Low (quality, spam, low-stakes disputes) | 14 days | as time permits |
What removal looks like
When we remove content, we:
- Mark the version revoked — inaccessible via the API and excluded from search.
- Delete the artifact from object storage within 24 hours.
- Add the version to the public revocation feed at
/v1/revocations.jsonso SDK consumers drop their caches. - Notify the publisher by email (if we have one) with the reason and next steps.
- Log the action to the audit trail.
Removed content persists in immutable backups for the 7-day backup window but is not accessible via the registry.
Counter-notice & appeals
Publishers whose content has been removed can contest it:
- Email policy@amitte.com within 14 days of the takedown notification.
- Include the skill ID, version, and a written response to the takedown grounds.
- We review with someone other than the original decision-maker where possible, and respond within 14 days.
For US DMCA counter-notices, statute sets the procedure: send a compliant counter-notice to dmca@amitte.com and we will restore the content 10–14 business days later unless the original claimant files a court action.
Appeal decisions are final; repeat appeals on substantively similar content will not be re-reviewed.
Publisher self-takedown
You can remove your own content at any time from /me: revoke a version or delete a skill — no request needed, effective immediately. Revoked versions stay listed in the revocation feed so consumers know to drop their caches.
Bad-faith requests
Filing a takedown 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
Every moderation and takedown action is counted in the live, public transparency report — aggregate totals and a redacted recent-action feed, no publisher identifiers.
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 |