Enterprise · Publishing

Every title you publish, watched by its own identifier.

Give us your catalog — books, journals or audiobooks — and Redflag AI finds where each title is being pirated, gets it taken down, and gets it delisted from Google search. Across pirate libraries, marketplaces, file-sharing sites, social platforms and the private messaging channels where academic piracy really happens.

Getting started

Your catalog. Three ways in.

Your standard metadata feed

Send us the same industry-standard catalog feed you already send retailers. We read the identifiers, rights and availability out of it and build your monitored catalog from that — no new file format to produce.

A spreadsheet

Upload a CSV in your console. Useful for a priority title list, a single imprint, or adding a handful of new releases.

Straight from your systems

If you'd rather not send files at all, your systems can add titles directly as they're published.

Publishing catalog protection dashboard showing confirmed removals, catalog titles monitored, dead-link filtering and institution leak traces.
What makes it different

Built for catalogs, not one-off takedowns.

Identifiers

Matched by ISBN, ISSN and DOI

We match on the identifiers your industry already runs on, not just similar-looking titles. That's what keeps accuracy high across a catalog of hundreds of thousands of books.
Audiobooks

Not just the printed word

Audiobooks are pirated as heavily as ebooks and get watched far less closely. We track audio editions alongside print and digital, on the same identifiers.
Real copies only

A live download, not a dead link

A lot of what looks like piracy is dead links and bait pages. We check whether a copy can actually be obtained, so your team isn't chasing pages that lead nowhere.
Private channels

Where academic piracy really lives

Much of the highest-value academic piracy happens by request in private messaging groups, not on websites. We monitor those groups, obtain the shared files, and follow the trail out of them.
Social platforms

Titles shared socially

Full copies and download links spread through social platforms and community forums too. Those surfaces are covered on the same catalog, with the same enforcement behind them.
Leak tracing

From a leaked PDF back to the account

For academic PDFs we read the licensing watermark out of the file itself to identify which subscribing institution's access was used — turning a piracy problem into an account you can actually address.
How enforcement escalates

If the site ignores us, we go past the site.

01

The site, and Google

A removal notice to the site itself — and in parallel, a request to delist the page from Google search results. Getting a pirated copy out of search often matters more than the page coming down, because search is how readers find it in the first place.

02

Whoever hosts it

If the site doesn't act, we go to the company hosting it. Hosting providers have terms their customers have to meet, and they enforce them.

03

Whoever connects it

Still nothing? We escalate to the network carrying the site's traffic. By this point a site is choosing between removing your title and losing its connectivity.

Google Trusted Copyright Removal Program

Redflag is a member of Google's Trusted Copyright Removal Program, so our delisting requests are handled through trusted-partner channels rather than the public form that anyone can submit. In practice that means they're processed faster and at volume — which is what makes search delisting workable across a whole catalog.

We report confirmed removals, not notices sent. Every removal is independently re-checked — including the case where a page quietly redirects to a homepage instead of actually coming down — and we track single-page removals separately from whole-site ones.

Reporting

You see everything we see.

Everything below lands in your console as you go, and in reporting you can take to a rights committee or a board without rebuilding it first.

What we found and what came down
Every detection, every notice sent, and — separately — every removal we've actually confirmed. Compliance is reported as verified removals, not notices issued.
Who's behind the site
Hosting and network details for each infringing site, including domain registration records — and what we can resolve even when the site hides behind a proxy or CDN.
How much it's costing you
Traffic and audience estimates per site, so you can see which sources are doing real damage and which are noise.
How wide the net is
Thousands of known piracy sites, libraries and channels are already covered, and we add new sources every month as they appear.

Scope your catalog.

From a priority title list to a full imprint feed — we'll onboard the shape of your business, not a spreadsheet template.