TitleLessTitleLess has no account, no sign-in, and no analytics. Nothing you do in it is sent to its developer, because there is nowhere for it to be sent.
What is stored, and where
History, bookmarks, downloads, saved pages, open pages, wallpapers, extensions and your settings are held on your device only. They are never uploaded, backed up to a server, or shared with anyone. Downloaded files are kept encrypted inside the app until you save them to Files. Deleting the app deletes all of it.
A private page keeps its history, cookies and cache in memory alone. Closing the app discards them.
Clear History & Website Data, in Settings, removes the pages you have visited along with the cookies, caches and local storage of every site. Shred App Data removes everything TitleLess has stored — pages, history, bookmarks, favourites, downloads, saved pages, wallpapers, installed extensions and what they stored, and every setting — and puts it back the way it arrived. Downloads you have already saved to Files are left there, where they are yours to delete.
What connects to the network
- The pages you choose to visit, and whatever those pages themselves request. A page you open is between you and that site; TitleLess does not add anything to it or report it anywhere.
- Searches go to the search engine you picked in Settings — TitleLess does not attach an identifier.
- Search suggestions: while you type in the address bar, the text so far is sent to that same search engine to fetch suggestions, over a connection that carries no cookies and no identifier. This never happens in private browsing or for anything that looks like a web address.
- Site icons are fetched from the site whose page you are on, over a connection that carries no cookies and keeps nothing on disk.
- Filter lists are downloaded from the addresses shown under Content Filtering, including any you add yourself, and re-checked about once a day. Those requests carry no cookies and say nothing about you beyond the fact that someone asked for a public file.
- Extension updates: only when you tap Update on the Extensions screen, TitleLess asks addons.mozilla.org for the current version of each installed extension that is published there — which tells Mozilla which of those you have — and downloads any newer one. TitleLess adds no identifier of its own to these requests, and Mozilla's privacy policy covers what it does with them. Installing an extension from a file sends nothing.
Extensions
Extensions are installed by you, from a file, and made by third parties, not by TitleLess, which does not review what they do or where they came from. An extension is given the permissions it asks for when you install it, and the install prompt lists them. Many can read and change every page you visit, see the addresses and titles of your tabs, and block or change what pages load. What an extension does with what it sees, including anything it sends to its own developer, is covered by that developer's privacy policy, not this one.
Extensions also run in private tabs unless you turn off Allow Extensions in Private Tabs, in Settings › Privacy & Safeguards › Extensions. With it off, extensions cannot see private tabs at all, and their blocking and page scripts do not run there.
An extension's files, and whatever it stores, are kept on your device. Removing the extension deletes both, and so does Shred App Data.
Permissions
TitleLess asks for the camera, microphone, location or motion only when a website you are using asks for them, and a site gets them only if you allow it. What they capture goes to that site; TitleLess itself keeps and sends none of it. Location, in Settings › Privacy & Safeguards › Privacy, turns location off for every website.
Saving an image from a page asks for permission to add to Photos, and only to add — TitleLess cannot see your library. Choosing a photo or file for a page, or a photo or video for the background, uses the system picker, which hands over only the item you pick.
Opening a page on your own network, such as a router's settings page, asks for local network access the first time.
What is not done
No advertising identifier is read, and contacts are never requested.
No crash reports or usage statistics are collected.
Blocking
Ad and tracker blocking runs entirely on your device. The rules are files; the addresses of the pages you visit are matched against them there, and are never sent anywhere to be checked.
Face ID and Touch ID
Content you keep in the app can be put behind Face ID or Touch ID. That check is performed by iOS, and the app is told only whether it succeeded. No biometric data is ever available to the app.
Children
TitleLess shows the web, which is not a curated place. It is not directed at children and has no content rating of its own.
This website
This website is hosted on GitHub Pages. It sets no cookies and runs no analytics or third-party scripts. GitHub keeps standard server logs, which include IP addresses, for security and operational purposes.
Changes
If this policy changes, the new version is posted here with a new date, and material changes are noted in the changelog.
Contact
Questions about privacy: support@titlelessbrowser.com