Privacy blocklists
The Privacy page sets how much a profile blocks, one category at a time. You never pick individual blocklists: each step of a category turns on what was chosen for it. The blocklists are compiled into one signed artifact that every PoP (server location) and self-hosted node loads, so a change applies everywhere at once.
One slider per category
Section titled “One slider per category”Three categories have a slider: Ads & trackers, Malware & phishing and Scams & abuse. Each goes from step 1, least restrictive, to step 5, most restrictive, and each step blocks everything the step before it does in that category, and more. Under each slider one line says what the current step blocks in that category and what it leaves alone.
| Step | Ads & trackers | Malware & phishing | Scams & abuse |
|---|---|---|---|
| 1 Minimal | Nothing: ads and trackers load. | Known malware, phishing and botnet servers. | Nothing. |
| 2 Light | The best-known ad and tracking networks. | Same as step 1. | In-browser crypto miners. |
| 3 Balanced | Most ads, trackers and analytics. The default. | Same as step 1. The default. | Crypto miners. The default. |
| 4 Strict | Also less common trackers and affiliate redirects. | Also dynamic DNS names that malware and phishing hide behind. May block a home server on such a name. | Also known fake shops, subscription traps and other scam sites. |
| 5 Maximum | Everything known to show ads or track. May break sites. | Also free hosting and file-sharing services malware is often served from. May block legitimate pages on them. | Also domains registered in the last 14 days. May break new sites. |
Malware & phishing blocks the same threat feeds at steps 1 to 3: its stricter blocking starts at step 4, and steps 2 and 3 say so rather than pretend to block more.
A new profile starts every category at step 3. If a site stops working at a stricter step, add it to the allowlist rather than moving the whole category down.
Each slider works with the keyboard: Tab to it, then the arrow keys move one step at a time and Home and End go to either end. Every change is saved at once. A screen reader announces the category, the step, its name and what it blocks.
All categories
Section titled “All categories”The All categories slider at the top is a shortcut, not a setting of its own: moving it puts every category on the same step. Under it, one line says exactly what changed, for example “Ads & trackers 2 → 4, Scams & abuse 3 → 4”, and Undo puts every category back where it was. When the categories are on different steps it shows Mixed.
Changed outside the slider
Section titled “Changed outside the slider”A category whose blocklists no longer match its step, for example after a change through the API, says so and offers Reset to step N, which puts it back on exactly that step.
Native tracking
Section titled “Native tracking”Below the sliders, Native tracking has one switch per manufacturer: Apple, Microsoft, Google, Samsung, Amazon, Xiaomi, Huawei, LG, OPPO/Realme, Vivo, Roku, Sonos and TikTok. Each one stops that maker’s devices and apps from phoning home (usage reports, diagnostics, ad measurement and the content recognition some TVs run in the background). They are all off until you turn them on. Native tracking has no slider.
Each switch shows how many queries it blocked in the last 7 days. The count needs query logs: when this profile keeps none, the section says so and the switches still block.
The switches are independent of the sliders: moving a slider never turns one on or off. Blocking a maker’s tracking can affect features that rely on it, such as some smart-TV recommendations, app crash reports or, on some Sonos firmware, playback; turn the switch off again if something stops working. What each switch blocks is curated from published research and the makers’ own documentation, and never includes what the device needs to work: activation, sign-in, updates, push notifications and the connectivity check.
A query blocked this way shows in the logs as “Blocked by Privacy › Native tracking › Samsung”.
Affiliate & tracking links
Section titled “Affiliate & tracking links”Links in newsletters, videos, social posts and deal sites often go through a click tracker or an affiliate redirect, which records the click before sending you on. Block affiliate and tracking links stops those redirects. It is off by default because of the trade-off: a link that goes through one stops there instead of reaching the shop, and the creator who shared it is not credited. Typing the shop’s address, or an allow rule for the redirect, still works.
A query blocked this way shows in the logs as “Blocked by Privacy › Affiliate & tracking links”.
Disguised trackers
Section titled “Disguised trackers”Block disguised third-party trackers checks the names a CNAME points to, so a tracker served from a first-party subdomain is blocked like the tracker itself. It is the same setting as CNAME uncloaking in Settings.
Where it applies
Section titled “Where it applies”Blocklists are the last step of the policy order: your allowlist overrides them. The Security and Parental control pages keep their own switches; the sliders do not change them.
Some sources have licences that are not yet cleared for redistribution. The cloud uses them, but the public artifact sent to self-hosted nodes does not carry them: a node filters without such a list. Every source and its licence is on the public Sources and licences page.
The API
Section titled “The API”A profile stores its list ids and, beside them, each slider’s step in
settings.protection (ads_trackers, malware_phishing,
scams_abuse, each 1 to 5). The public catalogue,
GET /v1/lists, gives
each list’s group, its level (the lowest step of its group’s slider
that turns it on, null outside the sliders) and, for a telemetry list,
its manufacturer. The lists of a set of steps are, for each of the
three groups, the non-retired lists of that group whose level is 1 to
the group’s step. To change a step through the API, send the step with
PATCH /v1/profiles/{id}
and those ids, plus any telemetry or parental ids you want to keep, with
PUT /v1/profiles/{id}/lists.