Documentation

How FanlockProtects Your Work

What we scan, how takedowns get filed, and what you control. This is the overview. For step-by-step guides, head to the Help Center.

Takes 30 seconds. No credit card required.

What's Covered

Everything in One
Place

Start with the basics, then dig into the parts you care about. Deeper how-to guides live in the Help Center.

Getting Started

Add your usernames and stage names, run your first scan, and read your results.

What We Scan

Telegram, Google, Bing, social media, forums, tube sites, and millions of file hosts.

Your Dashboard

Track detected leaks, pending takedowns, and removals in one place.

How Takedowns Work

Four-tier escalation: DMCA, host contact, infrastructure, search delisting.

Telegram Removals

Three-track enforcement for channels that ignore in-app abuse reports.

Plans & Billing

Basic, Pro, and Max. What each tier scans, and how agency pricing works.

How to read the evidence · Updated September 13, 2026

What a removal report tells you

Read each count with its reporting period, platform and outcome. The definitions below explain how to interpret evidence and ask useful questions about a report; individual exports may use different labels.

Detected match: A potential copy found by a scan. It still needs assessment for relevance and authorization.
Notice filed: A removal request was submitted. This records work sent, not a confirmed removal.
Source removal: The reported material was observed unavailable at the original website or platform location. Record the check date and result.
Search delisting: A search engine removed a result. The source website may still host the material.
Combined unique result: Count a reported location once when combining source and search outcomes; disclose the matching and deduplication rule.
Pending or unresolved: A request has no confirmed final outcome within the reporting window. Keep it visible in the denominator.
Duplicate or already unavailable: A repeated request or a location unavailable before the action should not be presented as a new removal caused by that request.

Google Search and Telegram measure different outcomes

Fanlock’s Google Transparency Report records Google Search copyright requests. It does not verify website deletion, Telegram removal, a combined success rate or revenue recovered. When reporting a percentage, specify the eligible requests, dates, pending cases and duplicate handling.

A Telegram case can show a complaint, elapsed time and a channel-removal notice. Keep its start and end events, case date and unit visible. The recordings below are Fanlock’s own case and report explanations; they should be read in the context shown, without turning one example into a promise for every request.

For practical next steps, read the DMCA reporting guide, review case studies, or check platform coverage by plan.

From Fanlock’s Instagram

Telegram takedowns and removal reports

Watch the cases and reports we share. Each case describes that example’s results; platform response times vary.

Telegram takedown example

A creator reported a Telegram channel with 5,000 members sharing her leaked content and deepfakes. Fanlock quoted 72 hours and reports getting the channel taken down within 16 hours.

This is one reported case. The transcript’s comparison refers to the Rulta support message shown in the recording, not a current service benchmark or a promise for every takedown.

Original post caption

Don’t wait forever to get telegram leaks down. Get fanlock.

Read the edited transcript

Edited for readability. This preserves the recording’s statements; read them with the source context above.

This creator sent us a Telegram channel with 5,000 members in it, leaking her content and deepfaking her without her consent. We told her 72 hours to be safe, but our team was able to get it down within 16 hours. This is what pirates saw when they opened her Telegram channel.

That is extremely fast. And just for comparison, this is Rulta’s own support team in writing this month. They take up to 90 days to process a Telegram removal, and you need a copyright certification. Even then, they say it’s only a 60 to 70% success rate.

So if you have a problem with leaks on Telegram, send us, or have your agency send us, a DM and we’ll help you out ASAP.

What appears on screen

The creator’s complaint describes a group sharing copyrighted posts and AI-generated material without permission.
A support reply gives a 72-hour estimate. The narrator reports a 16-hour result.
A Telegram notice says the group is unavailable because of copyright infringement.
The reel shows a separate message attributed to Rulta support, then discusses that message’s timing and success-rate statements.

Watch on Instagram

Fanlock removal report

Fanlock reports removing 1.43 million URLs and 1,738 active Telegram channels. The reel describes 34 million memberships across those channels and says autonomous scanners found most of the leaks.

The reel says “this quarter” without giving dates. Its URL total does not separate source removals from search delistings. Channel memberships can overlap, so 34 million memberships does not establish 34 million different people.

Original post caption

Fast, reliable, and transparent with our creators🔒

Read the edited transcript

Edited for readability. This preserves the recording’s statements; read them with the source context above.

Just this quarter alone, we removed 1.43 million URLs that were either leaks or deepfakes of creators that they did not consent to.

We’ve removed 1,738 active Telegram channels that were leaking or deepfaking our creators’ content. And those channels alone had 34 million members in them, which is just a mind-boggling number.

Our autonomous scanners found most of these leaks on their own. That means our creators can focus on creating content while we handle the enforcement and keep them safe online.

What appears on screen

The captions identify 1.43 million as a URL count, followed by a separate count of 1,738 active Telegram channels.
The narrator then describes 34 million members across those channels. The recording does not provide a dated export or deduplicated audience calculation.

Watch on Instagram

Creator support and protection

Fanlock describes dedicated-agent support on every plan, with a person creators can text or email. The reel says the agent usually replies within three hours and shows an example status-update conversation.

The three-hour figure is the reel’s reported response estimate, not a guaranteed response time. The industry-wide comparison in the transcript is not supported by a published benchmark in the recording.

Original post caption

Don’t wait, Fanlock has you covered

Read the edited transcript

Edited for readability. This preserves the recording’s statements; read them with the source context above.

If you’re a creator and your content gets leaked or deepfaked at 2 a.m., you should not be having to wait for a support ticket. The standard right now in the DMCA industry is if you find leaked content, you have to submit a request, and then you have to wait up to 16 hours to get a response back on that. And on the cheaper plans, some companies don’t even offer you support at all.

At Fanlock, what we did is every single plan gets a dedicated agent. You get a person that you can either text or email at any point of the day, and we’ll get a response back to you as quick as humanly possible.

Basic plan, Max plan, it does not matter. We have a dedicated agent for you that usually gets back to you within three hours. Because leaks and deepfakes, they do not wait for business hours, and neither do we at Fanlock.

What appears on screen

A plan-table excerpt illustrates the narrator’s comparison; it does not identify the source or establish current competitor terms.
An example text conversation shows a creator asking for a status update and their Fanlock contact replying that work is continuing.

Watch on Instagram

How It Works

From the Request
to the Result

We submit eligible requests, track responses and assess follow-up through hosts, infrastructure providers and search engines. The available route depends on the case.

Direct Takedown

We hit the host first

Infrastructure

Pressure the CDN & host

Financial Escalation

Cut off their payment providers

Search Removal

Search delisting tracked separately from source removal

AI-Powered Content Protection

Everything You Need to
to Fight Leaks

From detection to takedown, Fanlock gives you full visibility and control over how your content is protected online.

Search Delisting

We dig past page one, every alias and mirror, and delist from Google, Bing & Yahoo so fans can't find pirated copies.

Social Media Takedowns

Social takedowns on Pro and Max. We assess reports of leaked content and impersonation.

Telegram Monitoring

Telegram takedown requests on Max, with case-based follow-up and reporting.

Deep Web Coverage

High-traffic piracy sites Google never indexes, we crawl them anyway.

Piracy Sites & File Hosts

We scan where leaks actually live.

DMCA Filing

Filed

White-Glove Service

We file every takedown. You don't lift a finger.

Control Dashboard

Approve or reject takedowns in one click.

Dedicated Agent

A real person in your corner. Text them a leak, they take it down. On every paid plan.

FAQs

Frequently Asked
Questions

The questions creators ask most before and after they start with Fanlock.

How do I run my first scan?

Sign up, add your usernames and any stage names you use, and start the scan. We use those names to find potential leaks across accessible sources. Your first results land in your dashboard.

What does Fanlock cover?

Coverage depends on your plan: Basic includes Google and website removals; Pro adds Bing/Yahoo delisting and social takedowns; Max adds Telegram takedowns. Review the pricing table for included features and scan frequency.

How are takedowns filed?

We escalate across four tiers: automated DMCA notices, direct host contact, infrastructure and payment-processor pressure, and search-engine delisting. We track responses and follow up where the case supports further action. Recipients decide the request outcome.

What do I actually have to do?

Add your names once, then review results. You can approve or reject any individual takedown, whitelist your own platforms, and choose how hands-on you want to be. We handle the filings.

Where do the deeper how-to guides live?

This page is the overview. Step-by-step walkthroughs, troubleshooting, and account settings live at help.fanlock.com.

Is there an API?

There's a platform API for enterprise partners only. There's no API for agencies or solo creators. If you run a platform and want access, reach out through the contact page.