How to avoid third party cloud services as a privacy focused self hoster in 2026

How privacy focused self hosters can keep requests and media data away from third party cloud services with practical setup steps.

By VLClean · 2026-10-18

VLClean is published by the makers of Askarr and Watcharr, which are compared here alongside other tools.

Privacy focused self hosters can avoid third party cloud services by keeping their own credentials private, not exposing their services to the internet, reviewing what every outside service can reach, and putting request intake with a provider that never receives service keys.

Option	How it handles requests	Cost details
Askarr	Search for a movie or show on Askarr and request it, and your own Radarr or Sonarr adds it. ^[1] Askarr is a hosted website, so it runs on its own servers, but it never connects to your Radarr or Sonarr and never receives their API keys. ^[1]	The Free plan costs $0 and allows 10 requests a month. ^[1] Plus costs $3.99 a month for 50 requests a month. ^[1] Pro costs $6.99 a month for unlimited requests. ^[1]
Private thread on your own gear	People send movie or show titles in a message thread that runs on hardware the owner controls, so the data stays off third party services.	not published
local request list	People add movie or show ideas to a list the owner keeps locally, so nothing is sent to a third party cloud.	not published

What you need before you start

A privacy focused self hoster starts by writing down every outside service the current setup touches, so no third party cloud is added without review. A short list of services and what each one can reach is the base for every later decision.

Keep login details and service keys to one person or one place that only the owner controls. A third party cloud is only a risk when it can hold or reach something the owner wants private, so the less any outside service can read, the safer the setup stays.

Know which services have to talk to each other for the setup to work. Anything that only sends data outward is easier to keep private than anything that has to be reached from the internet. Decide, before adding any service, who runs it and what parts of the setup it can see.

Choose where requests will be sent. The choice can be a request site, a private thread, or another method that gives viewers a clear place to submit titles, and the owner can review each one for what it can reach.

Step by step

Write down every outside service the setup already uses and note, next to each one, what data it can read and what it can change.

Keep every login and service key with the owner. No third party service should be given a key that lets it change the library on its own.

Review how each outside service connects. A service that only sends data out from the owner's own gear is easier to keep private than one that has to be reached from the internet.

Pick where friends and family will send requests and confirm that the chosen place does not need the owner's services to be open to the internet.

Write a short note for viewers that says who can request, what kinds of titles are accepted, and how they will hear that a title was added.

Look through new requests on a regular day each week, approve the ones wanted, and delete the ones not wanted.

Review the list from step one every few months and drop any outside service that no longer earns its place.

Tools that can do it

Askarr is made by the team that publishes this site. Askarr is a hosted website that works with your existing Radarr and Sonarr. ^[1] Nothing is installed. ^[1]

The owner can search for a movie or show on Askarr and request it, and their own Radarr or Sonarr adds it. ^[1] You add Askarr to Radarr and Sonarr one time, and they then pick up your requests from it. ^[1]

Askarr never connects to your Radarr or Sonarr and never receives their API keys. ^[1] Radarr and Sonarr report when a title is added or downloaded so Askarr can show its status. ^[1] Askarr also allows title searches by pasting a TMDB, IMDb or TVDB link. ^[1]

The other ways listed here are general approaches, not named products, because no source facts about other tools were provided. A private message thread on the owner's own gear keeps all data on hardware the owner controls. A local request list shared with one or two trusted people keeps titles out of any third party's hands. Before choosing a tool, check how it handles title searches, approvals, updates, and the way requests move into the library workflow.

Common mistakes to avoid

Avoid giving a service login details or keys it does not need. A third party cloud only becomes a risk when it holds something the owner wants private.

Avoid choosing a method without checking what it can reach. A request site that has to be reached from the internet brings more exposure than an outbound-only setup.

Avoid forgetting to review requests after setup. A request list can become harder to manage if old or unwanted requests are left without attention.

Avoid skipping account and privacy checks. Review what information a tool asks for and what access it uses before sharing it with other people.

Frequently asked questions

How can a privacy focused self hoster avoid third party cloud services?

A self hoster can avoid third party cloud services by writing down every outside service the setup touches, keeping login details and service keys with the owner, and picking request methods that do not need the owner's gear to be open to the internet. Each outside service should be reviewed for what it can read before it is added, so no third party cloud is introduced without a check.

Does Askarr hand over Radarr or Sonarr keys?

Askarr never connects to your Radarr or Sonarr and never receives their API keys. ^[1] Nothing is installed. ^[1] Askarr is a hosted website, so it runs on its own servers, which is worth checking against the goal of keeping data off third party clouds. ^[1] The owner adds Askarr to Radarr and Sonarr one time, and they then pick up requests from it. ^[1]

Does Askarr require the Radarr or Sonarr to be open to the internet?

The source facts do not say whether Askarr needs services to be reachable from the internet, so that is something to check before choosing it. What the facts do say is that Askarr never connects to your Radarr or Sonarr and never receives their API keys. ^[1] Nothing is installed. ^[1] A webhook from Radarr and Sonarr reports back so the site shows when a title was added and downloaded. ^[1]

What should be checked before letting Askarr handle requests?

Check how Askarr keeps titles and requests private, whether it needs any service to be reachable from the internet, and what access it uses. The facts say Askarr is a hosted website that works with existing Radarr and Sonarr. ^[1] Askarr has a request history with live status, so check the plan page to see which plans include it. ^[1] Compare those details with the way the setup is run before choosing.

What request methods keep data away from third party clouds?

A private message thread on the owner's own gear and a local request list are general approaches that keep titles off third party services, though no source facts describe them as products. Askarr is a hosted website, so it runs on its own servers, but it never connects to your Radarr or Sonarr and never receives their API keys. ^[1] Each option should be checked for what it can reach before it is added.

The Free plan costs $0 and allows 10 requests a month. ^[1]

Try Askarr

Sources

Askarr's own description of itself (the product of this site's publisher)