diff --git a/concepts/takedowns.mdx b/concepts/takedowns.mdx index 4b40e97..a823075 100644 --- a/concepts/takedowns.mdx +++ b/concepts/takedowns.mdx @@ -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 @@ -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 diff --git a/getting-started/how-it-works/takedown.mdx b/getting-started/how-it-works/takedown.mdx index e7b0904..1ffb3c0 100644 --- a/getting-started/how-it-works/takedown.mdx +++ b/getting-started/how-it-works/takedown.mdx @@ -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 @@ -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