A browser is not a VPN. Sites you visit and your network operator can still see your IP address. Tracking protection is list-based and not absolute: known ads, analytics, and social trackers from bundled lists are blocked on the device, but no blocker catches everything. Private Browser Incognito is rated 17+ for unrestricted web access and is intended for adults.
A page you open is one request. An analytics beacon is often another: a small extra call that reports that the page viewed, how long it sat, or which button was tapped. People search for analytics blocking when they want those extra calls stopped on the phone, not forwarded through a privacy company in the cloud. Private Browser Incognito does that job with content-blocking rules powered by the open Disconnect lists. The lists ship inside the app. They run on the device. This article is about that class of request, not a scoreboard of named vendors.
Blocking a beacon is not the same as the destination forgetting you. The site you typed still sees the visit. Your network operator still sees that a connection happened. We will not name analytics companies in examples. Generic labels are enough: ads, analytics, and social trackers. If a request sits in those buckets and on the list, it can be stopped. If it sits outside, it can pass. The broader gap essay is Tracker Blocking Is Not Absolute. This page stays on the analytics request itself, and on where the matching happens.
What an analytics request is
An analytics request is a subresource a page fires so a measurement system can record the visit. It is not the HTML of the article you meant to read. It is not always a banner. It is often a tiny image, a script, or a POST that says the page loaded. From the phone’s point of view it is just another URL. From a privacy point of view it is an extra party, or an extra path on the same party, learning that you were there.
We keep three generic labels and stop there. An ad request tries to load a creative or an auction. An analytics beacon reports behavior. A social tracker tries to attach a widget, a pixel, or a count from a network you did not open as the main page. Those labels match how the bundled lists are categorized. They are not a census of every company that might learn something. There is no fourth bucket called everything a business might infer from a first-party page.
The site you typed is still a party to the visit. It sees your IP address, the usual headers, and whatever you type into its forms. Stopping a known analytics host is a reduction of known noise. It is not invisibility to the destination. If you sign in, the account is you. If you search, the engine you chose received the query. Suggestions stay off by default. The app asks before sharing a keystroke. None of that is solved by matching a beacon rule.
Lists that ship in the binary
Disconnect is a well-known open set of categories. In this app those categories power the rules. The lists are in the binary you installed. They are not downloaded at runtime. When we release an app update, the copy you install is the copy you browse with. There is no list server in the path while you tap links. That is a load-bearing choice. A blocker that phones home for a fresher file is a blocker that can see the app is open.
Private Browser Incognito has no accounts, no sign-in, and no app server for browsing. The App Store privacy label is Data Not Collected: no analytics SDK, no ads in the app, no third-party SDKs. We would rather miss a new analytics host until the next release than run a feed that watches you in order to stay current. The ship date is a freeze date. Something registered after that freeze is a miss until you update. The mechanics of that bundle are in How On-Device Block Lists Work.
On-device also means the matching happens before the extra request leaves, when a rule hits. It does not mean the browser sits in the middle of your traffic as a proxy. It is not a VPN. Page loads still go to the sites you visit. Opt-in search suggestions still go to the chosen engine. Downloads you start still go to their hosts. StoreKit still talks to Apple if you buy Stealth Suite. Block lists are not among the things the app fetches while you browse.
Private Browser IncognitoAnalytics blocking on the device. Lists in the app, not fetched while you browse.
Get the app
Not 100 percent, and exceptions exist
No blocker catches everything. New names appear. Hosts are cheap. A measurement script can move. A site can copy a beacon onto its own domain so a third-party rule never sees a foreign host. First-party analytics is ordinary web architecture. It is also why “we blocked analytics” can be true for listed extra requests and false for “nobody learned that you loaded this.” The destination still learned it. Extra listed names might not.
We do not publish a catch rate. A number would go stale on the same day we printed it, and it would invite a comparison we cannot police. A demo counter can show that rules fired. It is not a study. If another listing shows a precise percentage, ask what window, what page set, and who paid for the test. Then assume the next week’s hosts were not in it. We also do not claim fingerprint spoofing as a product. Fonts, canvas, and screen size can distinguish a device without a named analytics host. Saying that plainly is better than implying a shield that closes every side channel.
Per-site exceptions exist because pages break. When a video, a comment thread, or a paywall lives on a host the lists also use for ads or analytics, the page can fail. You can allow that site through to finish the task. The exception is a local choice. It does not report to us. It does not disable tracking protection everywhere else. It does not sync, because there is no account. Use it sparingly. Finish. Erase if you do not want that site’s cookies to linger for the rest of the session. The how-to is Turning Blocking Off for One Site.
Ads and social trackers sit in the same engine
Analytics is one label inside one engine. The same on-device rules also target ads and social trackers. That is why a page can feel quieter even when you were only thinking about measurement pixels. It is also why a broken module is not always “the analytics block.” A listed ad host and a listed social widget can fail a layout just as easily. The product does not sell three separate blockers. It ships one set of lists and three generic buckets.
If you want the wider on-device walkthrough, including what a content blocker can and cannot catch on iPhone, read On-Device Ad and Tracker Blocking on iPhone. Social widgets as a class have their own page. This one stays on the beacon that reports the visit. The useful posture is the same on all three: keep blocking on, do not bet a secret on a list match, and do not confuse a stopped extra request with a hidden IP.
One-tap erase is independent of the lists. Erase closes every tab and destroys cookies, cache, and site data. Lists stay in the binary. They are not session data. HTTPS-Only Mode stays on by default. Search engine choice stays. App Lock stays, if you set it. Blocking reduces extra requests during the visit. Erase ends the working state afterward. Neither one is a VPN. Neither one is 100 percent coverage of measurement.
What still sees the visit
Name the leftover observers or the feature turns into a myth.
| Request | What on-device lists can do | What still happens |
|---|---|---|
| Known analytics beacon | Stop it when the name is on the list | New or first-party names can pass |
| Known ads | Stop listed ad requests | Unlisted creatives can still load |
| Known social trackers | Stop listed widgets and pixels | The main site still sees you |
| The page you typed | Not blocked for being the destination | IP, headers, forms, your account if you signed in |
| Your network | Nothing. Not a VPN | Destinations can still be logged |
Rated 17+ still applies. This is unrestricted web access. You choose URLs. You are responsible for using the app lawfully. Analytics blocking will not make a site appropriate and will not hide you from a network administrator. It will reduce known extra requests from bundled Disconnect lists that ship on the device. That is a real feature. It is not a cloak, not anonymous, and not a promise that measurement stopped everywhere. Keep the lists. Keep the freeze date in mind. Keep the exception switch honest when a page needs it. The destination you opened remains a conversation, with or without a beacon on the side.
Private Browser IncognitoFree on the App Store. No history, on-device blocking, one-tap erase.
Get the app
Frequently asked questions
Does Private Browser Incognito block analytics on iPhone?
It blocks known analytics requests that match bundled Disconnect lists. The lists ship inside the app and run on the device. They are not downloaded at runtime. Blocking uses generic labels: ads, analytics, and social trackers. The destination site you typed still sees the visit. This is not a VPN and does not hide your IP.
Are analytics blocked 100 percent?
No. Tracking protection is list-based and not absolute. New names appear. Some requests never match a rule. A site can fold measurement into its own origin. Per-site exceptions exist when a page needs a blocked resource to function. Treat on-device blocking as a reduction of known extra requests, not as a guarantee.
Do block lists download while I browse?
No. The lists ship in the binary. When you install an app update, that copy is the copy you browse with. There is no runtime download of a fresher file. That choice keeps a list server out of the path. It also means a name registered after the ship date is a miss until the next release.
Can I allow analytics on one site?
Yes. Per-site exceptions exist so you can finish a task when a page needs a blocked resource. Turning an exception on is a local choice on that device. It does not report to us. It does not disable tracking protection everywhere else. There is no account that would sync the exception, because there is no app server for browsing.
Does blocking analytics hide my IP address?
No. Stopping a known analytics beacon reduces an extra request. It does not change the address the destination site sees, and it does not hide you from your network operator. Private Browser Incognito is not a VPN, a proxy, or Tor. Analytics blocking is on-device list matching. Network identity is a different layer.