A browser is not a VPN. Omitting a history file does not hide your IP address from sites you visit or from your network operator. 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.
Most browsers treat privacy as a cleanup job. They write a history file, a cookie jar, and a cache, then they offer a screen where you clear those stores after the fact. Private mode is a temporary exception inside that design. The file still exists in the product. You are asked to remember to empty it.
A forgetful browser is built the other way around. Every tab is a private session in memory. There is no browsing history feature. There is no history file to clear, because the file is never created. That is the claim worth testing, including on our own app, Private Browser Incognito. This article walks through what a history file is, what Safari private browsing still leaves for you to manage, and what a memory session actually holds until you erase it.
What a history file actually is
A history file is a local record of URLs, titles, and timestamps the browser keeps so you can go back, autocomplete, and sync. It is convenient. It is also a diary. On a phone that other people unlock, or that you hand over at a desk, that diary is the thing people worry about first, even when they cannot name the file format.
Clearing history is a deletion of records that were already written. Timing matters. The list existed between the visit and the tap. Screenshots of Settings, recently closed tabs, and iCloud features in a general-purpose browser can keep related traces in other places. A product that says “we have private mode” is often saying “the default mode still logs.”
Private Browser Incognito does not ship a history list. There is nothing to open under Recents, nothing to swipe away in a history pane, nothing to export. The engine is not hiding a log behind a switch. If you want the broader checklist of what else to demand from a private browser (blocking, erase, lock, accounts), start with The Best Private Browser for iPhone: What Actually Matters.
How Safari private browsing still leaves work
Safari private browsing is a genuine mode, and it is fair to describe it honestly. Tabs opened that way are meant to keep local data more tightly scoped, and they are not supposed to land in the usual history list. The architecture underneath is still Safari: a full browser with history and a Settings path for clearing what accumulated in the non-private half of life. Private browsing is a lane. The rest of the app still remembers.
There is also a difference between “this tab will not be in History” and “this app has no history feature.” The first is a filter. The second is an absence. Filters fail when you forget which window you are in. Absence does not depend on that memory. That is why a dedicated forgetful browser exists as a category, not as a dunk on Safari. Safari is a general browser. A no-history app is a specialized one.
Neither Safari private browsing nor a forgetful browser hides you from the site you opened. The server still sees an IP address. The local file is a separate problem from the network.
Memory sessions: tabs that never write a log
In Private Browser Incognito, every tab runs as a private session held in memory. You search, you follow a link, you keep a few pages open. The app does not append those URLs to a history store. When the session ends, there is no file left to scrub.
Memory is not magic. While a tab is open, the page is in RAM, cookies for that session exist, and the cache can hold assets so the site loads. That is required for the web to work. The design choice is that those stores are session-scoped. They are not promoted into a long-lived history database. They are not waiting in a Recents list after you leave.
Search is separate from history. You can use Google, Bing, DuckDuckGo, Wikipedia, or a custom engine. Suggestions are off by default. A query you send to a search engine is still a request that engine can log. The private browser simply does not keep a local copy of where you went afterward.
Cookies, cache, and what erase does
People ask whether a no-history browser still uses cookies. Yes. Sites set cookies so a login persists on the tab you are using, so a cart stays filled, so a language preference sticks for that visit. Cache holds images and scripts so the next scroll does not refetch everything. Those are session tools.
One-tap erase is the control that ends the session on purpose. It closes every tab and destroys cookies, cache, and site data. The page you were reading is gone. There is a home-screen quick action so you can wipe without opening the UI first. Stealth Suite adds an Auto-Erase timer if you want the session to die after you leave the app.
Erase is permanent. Erased data cannot be recovered, by you or by us. There is no support email that restores a tab. If you needed the article, copy it before you tap. The panic code and self-destruct in Stealth Suite are even broader: they are designed to destroy, not to archive. A forgetful browser that could undelete would be a different product.
Session erase does not clear the encrypted download vault. That store is AES-256, with no plain copy on disk, excluded from backups. Files you chose to keep are supposed to survive a browsing wipe. If you expected erase to mean the whole phone forgets the app, read the vault note before you rely on it. The vault is optional Stealth Suite. The session wipe is free.
What still exists after you close a tab
Closing a tab is not the same as erase, and honesty requires both sentences. When a tab is gone, that page is no longer on screen. The rest of the session may still be alive: other tabs, cookies those tabs need, a lock screen in front of the app. App Lock with a six-digit passcode and Face ID is free. It hides the session from someone who picks up the phone. It does not delete the session. Erase deletes it.
A second passcode can open a clean, empty browser while real tabs stay hidden. That is the decoy, part of Stealth Suite, described in Decoy Passcode: A Second Browser That Shows Nothing. The decoy is a presentation for a borrowed phone. It is not a history feature. The real session still has no history file. The decoy simply does not show the real tabs.
On-device blocking is also independent of history. Ads, analytics, and social trackers can still be stopped by lists that ship in the app even though no URL is being written to disk. The two features answer different questions: what the phone records, and what extra requests a page is allowed to make. For the second question, see On-Device Ad and Tracker Blocking on iPhone.
The App Store privacy label for Private Browser Incognito is Data Not Collected. There are no accounts, no sign-in, and no app server for browsing. We cannot show you a history we never received. That is the useful half of “no server.” The other half is the limit already in the callout: the sites and the network still see traffic.
Why “clear history” is the wrong promise
Clear history is a promise that something was written and will now be removed. It invites a race: visit, list, delete. Shared phones, surprise unlocks, and screenshots of a Settings pane all live in that race. A product that never writes the list does not ask you to win it.
It also does not ask you to trust a cloud dashboard. There is nothing to sync. Search suggestions stay off until you agree to share keystrokes. If you came here from a comparison of private browsers, keep the local question in front: is there a history file? If yes, who can open it, and when is it cleared? If no, what still lives for the session, and what does erase destroy? A browser with no history file is still a browser. It just refuses to keep a diary.
Private Browser IncognitoFree on the App Store. No history, on-device blocking, one-tap erase.
Get the app
Frequently asked questions
Does a private browser save history on iPhone?
Private Browser Incognito does not. Every tab is a private session held in memory. There is no browsing history feature and no history file to clear. That is different from a regular browser with a private mode, which still has a history store for everyday tabs and a cleanup task for the rest.
How is a no-history browser different from Safari private browsing?
Safari private browsing is a mode inside a browser that also keeps history, website data, and other records for normal use. A forgetful browser never writes a history file at all. Cookies and cache still exist for the life of the session, then one-tap erase destroys them. Neither design hides your IP address from sites or your network operator.
What happens when I erase a private browsing session?
One-tap erase closes every tab and destroys the session: cookies, cache, and site data. There is a home-screen quick action for the same wipe. Erased data cannot be recovered, by you or by us. Session erase does not clear the encrypted download vault if you use Stealth Suite. The vault is a separate store.
Can erased browsing data be recovered?
No. Erase, Auto-Erase, the panic code, and self-destruct permanently destroy data by design. There is no recycle bin and no support path that puts a tab back. If you needed the page, it is gone. That is the honest trade: a session you can throw away cannot also be a session we can restore.
Do cookies survive after I close a private browser?
Cookies and caches live only for the session. They are there so a site you are using can stay signed in on that tab. Closing up and using erase destroys that session data. There is no history list left behind, and there is no separate cookie pane you are expected to mop up later. Sites you visit can still set cookies while the tab is open.