Skip to content

Update from code changes: document PENDING EVIDENCE takedown status #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update from code changes: document PENDING EVIDENCE takedown status #96

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8b140c1
docs: document PENDING EVIDENCE takedown status
mintlify[bot] Jul 7, 2026
53def91
docs: improve SEO descriptions on takedown pages
mintlify[bot] Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion concepts/takedowns.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Takedowns"
description: "Understanding how ChainPatrol removes malicious content from the internet"
description: "Learn what takedowns are, why they matter for brand protection, and how ChainPatrol removes phishing sites, scam apps, and impersonation content."
---

## Overview
Expand Down Expand Up @@ -71,6 +71,7 @@ Regardless of the platform, the purpose of a takedown is the same: **to remove d
### Alternative Outcomes

- **CANCELED** - Takedown stopped (e.g., content invalid or unnecessary)
- **PENDING EVIDENCE** - Takedown is paused while ChainPatrol waits on externally-supplied evidence needed to proceed. Available for email and phone-number assets only. While in this state, no retractions, provider outreach, or automations run against the takedown. If it remains in **PENDING EVIDENCE** for longer than 21 days, a daily job automatically cancels it with an insufficient-evidence note
- **PENDING RETRACTION** - Identified as false positive, marked for retraction
- **RETRACTION SENT** - Formal retraction request submitted to provider
- **RETRACTED** - Provider confirmed retraction, takedown reversed
Expand Down
3 changes: 2 additions & 1 deletion getting-started/how-it-works/takedown.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Takedown"
description: "How ChainPatrol removes malicious content through coordinated takedown requests"
description: "How ChainPatrol submits, monitors, and retracts takedown requests across hosting providers, registrars, social media platforms, and app stores."
---

## Overview
Expand Down Expand Up @@ -47,6 +47,7 @@ Every takedown follows a clear lifecycle inside ChainPatrol:
### Alternative Outcomes

- **CANCELED** - The takedown was stopped (e.g., content turned out to be invalid or unnecessary)
- **PENDING EVIDENCE** - The takedown is paused while ChainPatrol waits on externally-supplied evidence required to proceed. Only email and phone-number takedowns can enter this state. While a takedown sits in **PENDING EVIDENCE**, no retractions, provider takedown emails, or background automations act on it — staff can move it in or out of this state from any other status. A daily job automatically cancels takedowns that stay in **PENDING EVIDENCE** for more than 21 days with an insufficient-evidence note
- **PENDING RETRACTION** - Identified as false positive, marked for retraction but not yet sent to provider
- **RETRACTION SENT** - Formal retraction request submitted to provider to halt or reverse the takedown
- **RETRACTED** - Provider confirmed retraction, takedown fully stopped or reversed
Expand Down