Enforcement & takedowns
Notices that get actioned, and chased when they are not
Sending the first notice is easy. Knowing which of last quarter's notices were quietly ignored, and following up on every one of them, is the work that decides whether a brand protection programme actually removes anything.
Notice lifecycle
Four states, one of which is a human
Automation covers drafting, routing and follow-up. Approval stays with a person, because that is the step with legal consequences.
Stage 1 of 4
Drafted in the format the platform expects
A confirmed case produces a notice built from the template for its platform and infringement class, pre-filled with the evidence captured at detection and the specific mark cited from your document vault. Amazon does not want what YouTube wants, and neither accepts a generic letter.
Stage 2 of 4
Held until a human with the right role signs off
Nothing leaves the platform automatically. The draft is editable, and approval is restricted by role and recorded in the audit log with a user and a timestamp. This is the control that makes automated drafting safe.
Stage 3 of 4
Routed to the correct abuse channel
Each platform has its own destination. Notices go to the specific abuse route for that platform rather than a shared inbox, and the sent copy is retained against the case.
Stage 4 of 4
Followed up on a fixed cadence, without a spreadsheet
Unanswered notices are chased automatically — the first reminder after a week, then weekly, up to three times. After that the case surfaces for escalation rather than sitting silently.
Templates
Purpose-built notices per platform
Each major platform has its own expected format, evidence requirements and abuse destination. TracBrand ships a dedicated template and route for each, and a generic route with the full evidence package for everything else.
Because the template is chosen from the infringement class the AI assigned, a counterfeit listing and an impersonating profile on the same platform produce different notices.
Dedicated templates and routes
- Amazon
- eBay
- YouTube
- Registrars, hosts and everything else — generic abuse route with full evidence
Grouped by shared signals
Findings that share a seller identity, a domain, a handle or infrastructure are linked into a cluster automatically.
Enforce once, across many
A cluster can be actioned as a unit rather than one listing at a time, which is how you get ahead of a professional operation.
Recognised on return
When the same operator reappears under a new storefront, the shared signals put it back in the existing cluster instead of a fresh queue.
Escalation-ready
A cluster with a documented history is what counsel needs to move from platform notices to legal action.
Seller clusters
Take down the operation, not the listing
Serious counterfeiters run dozens of storefronts and rebuild within days. Removing one listing is a rounding error; removing the network behind it is enforcement.
Inbound reports
Reports from customers and staff join the same pipeline
Any URL or image can be submitted for a scan and receives the same AI verdict, the same evidence record and the same takedown path as an automatically discovered finding — so a customer email does not become a parallel process in someone's inbox.
See a notice drafted against a real infringement
Bring an infringement you already know about. We will register the brand, let the platform classify it, and show you the notice it produces — including the mark it cites.