A browser is not a VPN and does not hide 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. Pages can also break when a needed resource matches a rule. Private Browser Incognito is rated 17+ for unrestricted web access and is intended for adults. This is not a speed-test claim with numbers.
A page is not one request. The document you typed is the first hop. Then scripts, images, frames, and beacons try to follow, many of them to companies you did not open as the destination. Ads auction. Analytics reports that the page viewed. Social widgets pull a share button or a comment count. Each extra request is work: another connection, another parse, another chance for the layout to wait. Blocking those known extras means fewer third-party requests start. That is why a page can feel lighter. It is a mechanism, not a stopwatch.
Private Browser Incognito blocks ads, analytics, and social trackers with content-blocking rules powered by the open Disconnect lists. The lists ship inside the app and run on the device. They are not downloaded at runtime. We will not invent benchmark results, lab percentages, or millisecond tables. The product fact is fewer extra requests when a name matches. The product limit is that matching is not 100 percent, and that a match can also take down a module you wanted. For the lists themselves, see On-Device Ad and Tracker Blocking on iPhone.
Fewer third-party requests, not a stopwatch
Think in traffic, not in trophies. A banner creative, an auction script, a pixel that fires on scroll, a widget from a network you are not using: each is a subresource. If the rule matches, that subresource never leaves the phone. The main document can still paint. The extras that would have contended for radio time and main-thread work never join the queue. People describe that as faster. The accurate sentence is fewer third-party requests.
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 score, ask what window, what page set, and who paid for the test. Then assume the next week’s hosts were not in it. This page will not compete with that theater.
The site you typed is still a party to the visit. It still sees your IP address, the usual headers, and whatever you type into its forms. Blocking extra companies is a reduction of known noise. It is not invisibility to the destination. Your network operator still sees that a connection happened. A workplace gateway can still log hosts. None of that is fixed by a list file, and none of it becomes a speed claim about the first-party page.
History is a separate design. Every tab is a private session in memory. There is no browsing history feature and no history file to clear. Blocking does not replace a forgetful session, and a forgetful session does not replace blocking. One-tap erase still closes every tab and destroys cookies, cache, and site data when you are done. Faster or not, the session is still something you can throw away.
Lists that already live in the app
The lists ship in the binary. When you tap a link, matching requests are not sent. Opening a tab does not check a list server. There is no second download you opt into, and there is no profile to install so iOS will send lookups somewhere else. The rules are already there, next to the rest of the app. That location is a privacy choice. A runtime feed would learn the app is open. We would rather freeze the list at ship time than run a fetcher that watches you in order to stay current.
Private Browser Incognito has no accounts, no sign-in, and no app server for browsing. The App Store privacy label is Data Not Collected. There is no analytics SDK, no ads in the app, and no third-party SDKs. Block lists are not downloaded at runtime. Updates arrive as App Store updates to the app that contains the lists. If you never update, you keep the older freeze. That is visible, boring, and honest. How the file lives in the binary is How On-Device Block Lists Work.
We describe three buckets with generic labels. An ad request tries to load a creative or an auction. An analytics beacon reports that a page viewed. A social widget tries to attach a share button or a comment count from a network you did not open as the main page. Company names do not belong in the examples. If a request sits in those buckets and on the list, it can be stopped. If it sits outside, it can pass. There is no fourth bucket called everything a company might learn, and there is no fifth bucket called a guaranteed quicker paint. HTTPS-Only Mode is adjacent, not identical. Encryption hides contents from a listener on the local network. It does not hide the host, and it does not replace a block list. A tracker over HTTPS is still a tracker until a rule matches.
Private Browser IncognitoDisconnect lists ship in the app. Fewer extra requests. No speed-test theater.
Get the app
What you might notice on the page
The visible half of blocking is the empty slot: fewer banners, fewer popovers, fewer third-party scripts humming in the background. The invisible half is the request that never left the phone. Both can make a page feel less busy. Neither is a promise that every article will render the same way it does in a browser with those extras turned on. Some sites budget for the auction. When the auction never runs, the layout can look sparse. That can be a relief. It can also look broken.
First-party work still happens. The article text, the site’s own images, the checkout form you meant to use: those still load from the host you opened. Blocking is not a read-mode product that strips the page to a novel. It is rule matching on subresources. iOS content blocking has limits. A script served from the same site you opened may not look like a tracker. That is one reason blocking is not 100 percent, and one reason we will not pretend the first-party page got a free performance rewrite. Fingerprinting can use fonts, canvas, and other signals we do not claim to spoof. We do not sell anti-fingerprinting as a product. Fewer extras are not a hidden identity, and they are not a number we will print.
When blocking makes a page worse
A blocker that never breaks a page is a blocker that is not matching much. When a video, a comment thread, a paywall, or a checkout script lives on a host the lists also use for ads, the page can fail. A player never appears. A pay button never binds. A map tile never paints. That is the other half of fewer requests: the request you actually needed was on a listed name.
Per-site exceptions exist so you can finish the task. Turning an exception on is a local choice on that device. It does not send a report to us. It does not disable tracking protection on other sites. Use exceptions sparingly. Finish. Erase if you do not want that site’s cookies to linger for the rest of the session. The exception does not survive as a cloud preference because there is no account. It lives on that device, for that app. That is the same local stance as the lists themselves.
Exceptions are also why a status line that says blocked everything is a bad design. If you allowed a site through, you allowed it. The UI should not pretend the shield is sealed. We would rather show a gap than invent a perfect score. The dedicated honesty page for that gap is Tracker Blocking Is Not Absolute. Blocking also does not empty a history file that a different browser wrote. A private browser with on-device lists only governs its own sessions.
Not a VPN, not a DNS filter, not a score
A VPN encrypts traffic to a remote hop and, in typical consumer use, changes the IP address sites see. That is a network product. Private Browser Incognito is not one. We do not hide IP addresses. We do not route browsing through our servers. We do not market a proxy. On-device blocking only means a matched extra request never started from this process. The remaining requests still leave from your address.
A DNS filter answers name lookups and can refuse known ad domains, often with a profile or a local VPN shell, and often for more than one app. That is a different machine. Our rules apply to this browser. They do not require a profile. They do not claim to clean Mail, Safari, or a game’s web view. The architecture contrast is Content Blockers vs DNS Filters. Stealth Suite does not change how lists work. The blocker is free and already in the binary. There is no paid stronger list, and there is no paid faster list.
If you are keeping the moving parts straight, a compact table is more useful than a race.
| Claim you might have heard | What we actually ship | What we will not say |
|---|---|---|
| Blocking makes pages faster | Fewer third-party requests can start | Any millisecond, percent, or lab rank |
| Lists stay current from the cloud | Lists ship in the binary | A runtime download while you browse |
| Everything is blocked | Known ads, analytics, social trackers | 100 percent. New names still appear |
| Pages always work | Per-site exceptions when they do not | A blocker that never breaks a module |
| You are hidden on the network | Nothing. Not a VPN | A new IP, Tor, or fingerprint spoofing |
Use the lists. When a page breaks, exception, finish, erase. When you are done with the session, destroy it. When someone else might open the app, lock it. App Lock with a six-digit passcode and Face ID is free. None of those switches is a benchmark. Together they are a local stance: less extra traffic from this browser, a gap we will not paper over. Rated 17+ still applies. You choose URLs. You are responsible for using the app lawfully. Pages can load with less third-party noise. That can feel quicker. We will leave the stopwatch in the drawer.
Private Browser IncognitoFree on the App Store. No history, on-device blocking, one-tap erase.
Get the app
Frequently asked questions
Does ad blocking make pages load faster on iPhone?
It can, because fewer third-party requests start. Ads, analytics, and social widgets that match the lists never leave the phone. That is less work for the network and for the page. It is not a speed-test claim. We do not publish milliseconds, percentages, or benchmark results. Some pages also break when a needed resource was on a blocked host.
Does Private Browser Incognito publish speed-test numbers?
No. We do not invent lab results, stopwatch scores, or catch rates. A demo counter can show that rules fired. It is not a study. The honest mechanism is fewer extra requests from bundled Disconnect lists that ship in the app. Treat that as architecture, not as a race against another browser.
Where do the block lists live in Private Browser Incognito?
In the binary. Ads, analytics, and social trackers are stopped by content-blocking rules powered by the open Disconnect lists. The lists ship inside the app and run on the device. They are not downloaded at runtime. Opening a tab does not check a list server. Updates arrive as App Store updates to the app that contains the lists.
Can blocking break a page?
Yes. A video player, comment thread, or checkout script may live on a host the lists also use for ads. When that happens, a per-site exception is the honest fix: allow that site to load what it needs, finish the task, and erase the session if you do not want those cookies to linger. Exceptions are local. They do not phone home.
Is faster loading the same as hiding my IP address?
No. A browser is not a VPN. Fewer third-party requests do not hide your IP from the site you typed or from your network operator. Blocking is list-based and not 100 percent. New names appear. First-party scripts can pass. The destination still sees you. Tracking protection reduces known noise. It does not assign a new address.