Full issues reposted to Telegram and Discord
Usually a channel that aggregates several publications, sometimes charging its own subscription for your work. The most direct revenue loss and the easiest to prove.
For paid research and newsletters
Paid research leaks within hours of sending. The subscriber who forwarded it is not the problem — the channel republishing every issue to four thousand people who would otherwise have paid you is.
Fit
Finance, markets, and investing newsletters with a paid tier, independent research shops, and paid communities. Works the same for courses and paid reports.
Threats
Usually a channel that aggregates several publications, sometimes charging its own subscription for your work. The most direct revenue loss and the easiest to prove.
Your back catalogue on a file host, indexed and ranking for your own issue titles.
A lookalike domain reproducing your posts wholesale, monetised with ads or collecting sign-ups that you never see.
A copy of your checkout taking real money from readers who think they are subscribing to you. You get the support email and the chargeback.
Stakes
Passage-level
We match the actual text of your issues, so a takedown notice cites the reproduced passage rather than asserting a resemblance.
Every channel
Telegram, Discord, file hosts, document hosts, marketplaces, code registries, and search — not just the web.
10/mo
Which is more than most publications need, because the same handful of channels reoffend.
Paste a paragraph from a recent paid issue into the public scan and see where it already appears.
Plan
Essential is built for this: daily monitoring, passage matching against your published issues, and up to ten takedown cases a month with evidence prepared for you.
Questions
More in the full FAQ.