Sections
Docs › Removal
Notices
How takedown notices are queued, timed and sent, what the notice settings control, what the queue statuses mean, and what happens after a notice goes out.
A notice is filed for a page that ranks on your queries, is not on your whitelist, has held its position through the wait after discovery, and has evidence captured. It is submitted through a real browser, with the evidence attached, on behalf of the contact given in the project.
Notice settings
In the project, under Notice settings.
- Sending on or off. Off means nothing leaves; pages are still recorded. New projects start off until contacts and evidence are in place.
- Wait after discovery. How many days a page must hold its position after it is first seen before a notice is queued. Pages come and go; the wait filters out the ones that would have vanished anyway.
- Notices per day. An upper limit for the project. Hosts and platforms notice bursts; a steady rate is answered better than a flood.
- Contacts. Who the notice is filed on behalf of, and where replies go.
The queue
Takedowns, in the left menu, shows the queue across projects: the next send and when it is due, how many are planned for today, how many pages are ready, how many are still waiting out the delay. The per-project view under Notice queue shows the same for one project, with each notice and its state.
Notice states
| State | Meaning |
|---|---|
| Queued | Evidence captured, waiting for its turn under the daily limit. |
| Submitted | The notice was filed; the reference and time are recorded. |
| Failed | The submission did not go through — a form changed, a page was gone by the time of sending, a check was not passed. Failed notices are retried or reviewed. |
A submitted notice is not a removed page. What the host does with it is their decision, and the answer arrives over days or weeks.
After the notice
The query keeps running. The page's status changes when the results change: resolved when it is no longer seen, reappeared if it comes back. A page that returns under a new address is a new link, captured and filed again. Filing is a step; removal is the outcome, and the outcome is something the system checks rather than assumes.
Credits
Collection and notices are billable operations. The home page shows the balance and the operations charged; the notice settings show what a notice costs for the project. When the balance runs out, collection pauses and a message on the project says so — nothing is lost, and it resumes when the balance is topped up.