Privacy policy
What Vitrel sends, and what stays on your Mac.
Vitrel is a web browser for the Mac, made by Teralis. This page covers the app and this website, vitrel.app. Vitrel is in development, so it describes the development builds that exist today. It will be updated before the private beta.
Last updated 12 October 2026.
The short version
- No accounts and no tracking. Vitrel doesn't report what you do. When it crashes, it sends us a crash report that says what failed and nothing about you, unless you turn that off.
- Your history, open tabs, passwords and settings stay on your Mac. Nothing is synced unless you turn on Sync, and what it syncs is encrypted on your Mac with a key we never have, so our server stores it without being able to read it.
- Apart from the pages you open, the app makes a few requests of its own. Each one is listed below, with where it goes and why.
- vitrel.app sets no cookies, runs no analytics and loads nothing from other sites. Our server keeps no access log for the site's pages, the sign-up form, crash reports, feedback or sync. It keeps two short logs, to count how many copies of Vitrel are in use: the app's update checks and downloads of the Mac app. Each is deleted within four days, and only daily totals are kept.
- If you sign up for the alpha, we keep your email address to tell you when it's ready, until you unsubscribe. Every email has an unsubscribe link.
What the app sends, and why
Besides the pages you open, these are the only requests Vitrel makes. None of them carry the cookies from your browsing.
Search suggestions
- Goes to
- Your search engine: Google, unless you pick Bing, DuckDuckGo, Kagi or Brave in Settings.
- When
- As you type in the address bar, for text that isn't a web address.
- What
- The text typed so far. No cookies are sent, so the engine can't tie it to an account.
- Never
- From private windows. For anything that looks like a web address or an email address, or text over 200 characters. Or when you set your own search engine: Vitrel doesn't ask it for suggestions. There's no switch to turn them off yet.
Filter lists for the blocker
- Goes to
easylist.to(EasyList, EasyPrivacy),ublockorigin.github.io(uBlock Origin's filters, privacy and quick fixes lists) andpgl.yoyo.org(Peter Lowe's list).- When
- At first launch, then about once a day.
- What
- A plain download. Nothing about the pages you visit: the lists are matched against pages on your Mac.
Tab icons
- Goes to
- The site you're visiting, or wherever its page says its icon is. Vitrel uses no icon service.
- When
- When a page loads and Vitrel doesn't have its icon yet.
- What
- A request for the icon, without cookies. In private windows, icons are kept only in memory.
Adding an extension from the Chrome Web Store
- Goes to
- Google:
clients2.google.com, which hands the package over from Google's download servers. - When
- Only when you choose to add an extension.
- What
- The extension's ID and a Chrome version number, without cookies. Vitrel checks the package's signature before installing it and deletes the download afterwards.
Extension updates
- Goes to
- Google's update service, the one Chrome uses.
- When
- About once a day, and only while you have extensions from the store installed.
- What
- The ID and version of each store extension you have, without cookies. Google answers with any newer versions, and flags extensions it has found to be malware, unwanted software or against its policies. Vitrel turns those off, and keeps them with their data until you remove them.
Vitrel's own lists
- Goes to
- Our server,
api.vitrel.app, for three small files: sites that need a different user agent (/v1/user-agents.json), extensions we need to turn off because they're harmful or broken (/v1/extensions/kill-switch.json), and fixes that help extensions run in Vitrel (/v1/extensions/compat.json). - When
- About once a day, in the background. The two extension files only while you have extensions installed: the list of extensions to turn off comes with each extension update check.
- What
- A plain request for each file, without cookies. It says only that it comes from Vitrel, and which copy of the file your Mac already has, so an unchanged file isn't sent again. Nothing about you, your Mac, your browsing or your extensions. We sign every file, and Vitrel uses one only if the signature checks out. Your Mac does all the matching.
Vitrel's own updates
- Goes to
- Our server:
api.vitrel.appfor one small file that names the newest Vitrel (/v1/update.json), andvitrel.app/download/for the update itself. - When
- The file: when Vitrel opens, about once a day after that, and when your Mac wakes if the last check was over an hour ago. The update: only when you click Update.
- What
- A plain request, without cookies. It says that it comes from Vitrel, which version of Vitrel is asking (such as 0.4.4, build 8), and which copy of the file your Mac already has, so an unchanged file isn't sent again. Every copy of that version sends the same version number, which we use to count how many copies of each version check for updates. Nothing else about you or your Mac: Vitrel compares the versions itself. We sign the file, and Vitrel installs an update only when that signature, the download's fingerprint and the new app's own signature all check out.
- Kept
- Our server writes each check down: when it came, the IP address it came from and, from versions that send them, the version and build. It deletes that within four days. From it we count how many copies checked each day and on which version, counting each IP address once a day without keeping it. Only those daily totals are kept. Downloading an update isn't logged.
- Your choice
- Settings ▸ General ▸ Check for updates automatically, on unless you turn it off. Check Now asks once.
Crash reports
- Goes to
- Our server,
api.vitrel.app(/v1/crash). - When
- The next time you open Vitrel after it crashed, a few seconds after its window opens. And when macOS tells Vitrel that it stopped responding for a while or used too much CPU or disk. At most 10 reports a day.
- What
- What went wrong and where: the kind of crash, the part of Vitrel's code that was running (as positions in Vitrel's and macOS's code), and the short reason macOS gives. Also Vitrel's version, macOS's version, your Mac's model (such as Mac16,1) and processor type, the time to the minute, and how many times the same crash happened. A web address in it is cut down to the site (
https://example.com), a folder in your home folder loses your user name, and email addresses are removed. Without cookies or any identifier: no account, no serial number, not the identifier macOS gives its own crash reports. - Never
- Page content, form data, passwords, your history, your open tabs or anything you typed.
- Your choice
- On unless you turn it off: on the last step of the welcome when you first open Vitrel, or any time in Settings ▸ Privacy & Blocking ▸ Crash reports. Turning it off also deletes reports waiting to be sent.
Feedback you send
- Goes to
- Our server,
api.vitrel.app(/v1/feedback). - When
- Only when you choose Help ▸ Send Feedback… or Send feedback… in the ⋮ menu, write something and click Send. It works with crash reports off, because you choose to send it.
- What
- What you write. With Include diagnostics ticked (it starts ticked when crash reports are on): Vitrel's and macOS's versions, your Mac's model and processor type, and Vitrel's recent error notes (the short notes it writes to your Mac's system log, described below), which can name sites you visited (the site only, never the full address) and the IDs of extensions you have. With Include a screenshot of this tab ticked (it starts unticked): a picture of the page in the current tab, which shows whatever the page shows. Without cookies or any identifier. If you'd like a reply, put your email address in your message.
Sync, if you turn it on
Sync keeps a profile's bookmarks, tab groups, settings and, if you tick it, history the same on your Macs, and shows each Mac's open tabs on the others, each with its own checkbox in Settings ▸ Sync. Your saved passwords sync only if you turn on password sync, separately, on each Mac (Vitrel 0.4.4 and earlier don't offer it).
- Goes to
- Our server,
api.vitrel.app(/sync/v1/), through Cloudflare. - When
- Shortly after Vitrel opens, a few seconds after you change something (history at most once a minute while you browse), when you switch to Vitrel, when your Mac wakes or gets its network back, and about every 15 minutes while Vitrel is open. Only for the profiles where you turned Sync on.
- What
- The name and model of each Mac in the sync, and the kinds you tick in Settings ▸ Sync: your bookmarks, tab groups and the profile's own settings (its search engine, Privacy & Blocking's switches and the sites where you turned protections off), and, only if you tick History (it starts unticked), the pages you visited in the last 90 days, with their titles and the times you visited them. Deleting history on one Mac, or clearing it with Clear Browsing Data, does the same on the others. With Open tabs ticked (it starts ticked), the addresses and titles of the tabs open in the profile's windows (whether each is pinned, and its tab group's name), at most every 30 seconds while they change, so your other Macs can offer them in History ▸ Tabs from Your Other Macs and in tab search; unticking it, or turning Sync off on that Mac, withdraws the list first. Each item is encrypted on your Mac before it leaves, with a key we never have, and padded so its size doesn't give away how long an address is. With it go a random ID for the sync, a random ID for each Mac and each Mac's public key. Every request is signed by the Mac that sends it. With password sync turned on (its own switch in Settings ▸ Sync, after Touch ID or your Mac password and your recovery key), your Vitrel Pass logins: each one's site, username, password, notes, one-time code setup (if you saved one) and the dates you saved and changed it, encrypted with a key of their own that only the Macs where you turned password sync on have, and sent only while Vitrel Pass is unlocked. With them go, the same way, the earlier version of a login another Mac's newer save replaced (kept for 30 days so you can restore it), and for each Vitrel passkey the site, account name, the day you made it and which of your Macs holds it, so your other Macs can list it; never the passkey's key, which stays on the Mac that made it. Never your cards, addresses, the sites you chose never to save, or when you last used a password. Not page icons or anything inside the pages, and history older than 90 days stays on the Mac that has it.
- Our server sees
- The kind of each item (a bookmark, a tab group, a setting, a page in your history, a Mac's open tabs, or something of your passwords, which it can't tell apart from a password), how many of each you sync, each item's size rounded up to 256 bytes, the order in which items change and the day each one last changed, whether password sync and recovery help are on, how many Macs you use, the day each one last synced, and which version of each kind's format a Mac needs to keep syncing it. Each item is stored under an ID your Mac derives with a key we never have, so not even its ID gives away its address. Never what an item is: no web addresses, titles, site names, settings, passwords, or the names and models of your Macs.
- Never
- Private windows: their tabs and history. Tabs that AI agents opened. Your recovery key, which never leaves your Mac and isn't kept on it either. Settings that belong to one Mac, such as Appearance and whether AI agents may use Vitrel. Site permissions, cookies and website data, downloads and Diagnostics.
- How long
- Until you turn sync off with Also delete from the server and turn off on my other Macs, which deletes it from the server at once. A sync no Mac has reached for a year is deleted. When you delete an item, a marker that it's gone is kept for 180 days, so every Mac learns of it, and a removed Mac's public key is kept for 180 days, so that Mac learns it was removed. Backups keep encrypted copies for up to 5 weeks (below).
- Your choice
- Off unless you turn it on, for each profile, in Settings ▸ Sync, where you also choose what syncs and see your Macs.
Checking your passwords against data breaches
The Passwords window marks saved passwords that appeared in known data breaches, along with reused and weak ones. Reused and weak passwords are worked out on your Mac. For breaches, Vitrel asks Have I Been Pwned's Pwned Passwords service in a way that never reveals the password.
- Goes to
api.pwnedpasswords.com(Have I Been Pwned, through Cloudflare).- When
- When you click Check Now in the Passwords window, and when you open it at most once a day, then only for passwords saved or changed since they were last checked. Only while the Passwords window is unlocked, never in the background.
- What
- For each password, the first 5 characters of a 40-character code made from it (its SHA-1 hash), which hundreds of different passwords share. The service answers with every breached password's code that starts the same way, padded with made-up ones so the answer's size gives nothing away, and Vitrel looks for yours in it on your Mac. No cookies and no account. The service sees your IP address and when you ask.
- Never
- The password, the rest of its code, the site or the username. The results stay in Vitrel Pass's encrypted file on your Mac, and never sync.
- Your choice
- On unless you turn off Check for passwords found in data breaches in Settings ▸ Passwords, for each profile. With it off, nothing is sent.
The window's Change Password… button opens the site's own page for changing a password. When you click it, Vitrel first asks that site, without cookies, whether it has one at the standard address (/.well-known/change-password), and opens its home page if not.
Fraudulent website warnings
- Goes to
- Handled by macOS, not by Vitrel.
- What
- Vitrel leaves on WebKit's warning for known phishing and malware sites, which works as it does in Safari. macOS checks addresses against a list of harmful sites kept on your Mac. When one might match, macOS may send information calculated from the address, not the address itself, to Google Safe Browsing (or Tencent Safe Browsing on Macs set to mainland China) to confirm it. Vitrel has no setting to turn this off yet.
The pages you open
Websites get what any browser sends them. Vitrel sends Safari's user agent unchanged, so sites treat it as they treat Safari. The blocker stops requests to known ad and tracking servers before they're made. Extensions you add can make requests of their own, as in any browser, within the site access you give them.
There's nothing else.
What stays on your Mac
Vitrel keeps these in ~/Library/Application Support/Vitrel and your Mac's caches. None of it is sent to us or synced, except what you choose to sync with Sync (above). Cookies go only to the sites that set them, as in any browser.
- History: the pages you visit, for the History window (⌘Y) and address bar suggestions. You can delete pages, or all of it, from the History window. With Sync's History ticked, the last 90 days sync (above), and what you delete goes from your other Macs too.
- Open windows and tabs, so they come back after you quit.
- Vitrel Pass: your saved passwords, in a file encrypted with AES-GCM. Its key is in your login keychain, set not to sync to iCloud, and Vitrel asks for Touch ID or your Mac password to unlock it. Passwords sync only if you turn on password sync (above); cards and addresses never do. One-time code setups you save are kept in the same encrypted file and sync with their login; a QR code you paste or choose is read on your Mac, and nothing about it is sent. What breach checks found is kept in the same encrypted file and never syncs. Your passkeys' keys stay in the Secure Enclave of the Mac that made them; with password sync on, Vitrel keeps the list of your other Macs' passkeys, encrypted, next to them.
- Settings, such as your search engine and the sites where you turned the blocker off.
- Downloads go to your Downloads folder. Each file gets macOS's standard quarantine record, which notes the site it came from (its domain, not the full address) so macOS can check the file when you first open it. The list of recent downloads lasts only until you quit.
- Cookies and website data, stored by WebKit, as in Safari.
- Extensions and the data they keep.
- Tab icons and filter lists, as caches.
- Diagnostics: when something fails, Vitrel writes a short note to the macOS system log on your Mac. Web addresses in it are cut down to the site's domain, and it never includes page content, form data or passwords. Site names, addresses and error details are marked private, so the system log, and the diagnostics macOS collects from it (a sysdiagnose), show them as <private>. These notes reach us only inside feedback you send with diagnostics ticked.
- Sync, for a profile where you turned it on: which items were synced and the changes waiting to go, in the profile's folder (synced passwords stay encrypted there), and its keys in your login keychain, set not to sync to iCloud. Turning sync off deletes both and leaves your data as it is.
- Crash reports waiting to be sent, for at most 30 days, in the same folder. macOS keeps its own crash logs in
~/Library/Logs/DiagnosticReports; Vitrel reads its own there and sends the cut-down report described above, never the log itself.
Private windows keep nothing. Their history, tabs, cookies, site data and icons stay in memory and are gone when the window closes, and they send no search suggestions. Vitrel Pass fills passwords in them but doesn't offer to save new ones.
AI agents, if you turn them on
Vitrel can let an AI agent on your Mac, such as Claude Code, use it over MCP. It's off until you turn it on in Settings ▸ General ▸ AI agents. The connection stays on your Mac and never goes over the network, only Vitrel's own helper program can use it, and you click Allow before an agent gets in. An agent can only open, read, screenshot, click and type in tabs it opened itself, never your other tabs, and one button in the toolbar stops every agent.
Its tabs use your normal cookies, so it's signed in wherever you are. Vitrel sends nothing to any AI service itself. What an agent does with what it reads, such as sending it to its AI provider, is up to that agent and its provider.
No accounts, no analytics
Vitrel has no accounts and nothing to sign in to. It has no analytics and no ads, and it doesn't tell us how you use it: not which sites you visit, what you search for or which features you use. Crash reports are the one thing it sends us about itself on its own, so we can find and fix crashes, and you can turn them off.
Sync has no account either: no email address and no password. Vitrel makes a recovery key that only you have. We can't recover it: if you lose every Mac and the key, nobody can read the synced copy, us included, unless you turned on recovery help (below).
Crash reports and feedback on our server
- Where: on our own server, behind
api.vitrel.app. Only we, Teralis, read them, to find and fix problems in Vitrel. - How long: 90 days from when they arrive, then they're deleted automatically. To fix a problem we may copy the technical part (where in Vitrel's code a crash happened, or what your feedback describes) into our private bug tracker, where it stays as long as the issue does.
- Your IP address: to stop one network flooding the server, it counts reports per IP address for an hour, in memory, then forgets them. It never writes your IP address down, and it keeps no access log.
- Who else sees them: Cloudflare passes them on to our server, as it does for this website (below). Nobody else. We don't sell or share them.
- Deleting: a crash report carries nothing that ties it to you, so we can't pick yours out. To have feedback deleted sooner, email contact@teralis.dev with roughly when you sent it and what it said.
Sync on our server
- End-to-end encrypted: when you turn Sync on, Vitrel makes a recovery key for that profile and shows it to you once. Your Mac derives from it the keys that encrypt what it syncs and sign its requests. We never have the recovery key or the keys that open your data, so we can't read what you sync, and neither can anyone who gets into our server or its backups. Passwords have a key of their own, which only a Mac where you turned password sync on (with Touch ID and your recovery key) ever has: a Mac that syncs only your bookmarks can't read them.
- No account: no email address and no password. The recovery key is the only way to add another Mac, and we can't recover it: if you lose every Mac and the key, nobody can read the synced copy, us included, unless you turned on recovery help.
- Recovery help, if you turn it on: Let Vitrel help me recover is off unless you tick it. With it on, your Mac also seals the key to your synced data, together with an email address you give, to a Teralis key that's kept offline, never on any server. If you lose every Mac and your recovery key, you write to us, we check it's you through that email address, and we hand your synced data to your new Mac. Your other Macs are then removed from the sync, so someone who got into your email can't stay hidden. It also means Teralis could read your synced bookmarks, tab groups, settings, history and open tabs. It never includes passwords. Our server can't open the sealed copy and never sends it back. Turning recovery help off deletes it from the server at once, and from backups within 5 weeks.
- Backups: every night our server encrypts a copy of its sync data, which is already encrypted by your Macs, with a key only we hold, offline. The server keeps the last 14 nights, and a second server of ours keeps 7 nightly and 4 weekly copies. So something deleted from the sync server can stay in a backup for up to 5 weeks, still encrypted with your keys.
- Your IP address: to limit how many syncs one network can start (5 a day), our server counts new ones per network for a day (the first three parts of an IPv4 address, or the first 48 bits of an IPv6 one), in memory, then forgets them. It never writes your IP address down, and it keeps no access log.
- Who else sees it: Cloudflare passes requests on to our server, as it does for this website (below): it sees your IP address, when each request is made and how big it is, the random IDs and the encrypted data. Nobody else. We don't sell or share anything.
- Deleting: in Settings ▸ Sync on any of your Macs, Turn Off Sync… with Also delete from the server and turn off on my other Macs deletes everything at once, and backups drop it within 5 weeks. Each Mac keeps its own bookmarks, tab groups, settings, history and passwords.
The alpha waitlist
If you sign up for the alpha on vitrel.app, we keep your email address so we can tell you when the alpha is ready. It's the only thing the form asks for, apart from an optional question.
- What we keep: your email address; when you signed up, confirmed and unsubscribed; which page the form was on; the browser you said you use today, if you picked one; which of our emails we've sent you, and when, and whether one is waiting to go out (we send at most 100 emails a day, so on a busy day yours can wait until the next); and a random code that makes the links in our emails work. It's kept in a database on our own server.
- What we send: first, an email asking you to confirm your address. Nothing else goes to an address that isn't confirmed. Once you confirm, only the alpha invitation, and a note that you're already on the list if someone uses the form with your address again. No news and no newsletters. Our emails have no tracking pixels and no tracked links.
- Who else sees it: Resend, an email delivery service, sends our emails (through Amazon's email service), so it gets your address and what each email says, to deliver them. It keeps a record of each email it sends, and if an email to you bounces or is reported as spam, it stops sending to your address. What Resend keeps is covered by Resend's privacy policy. Nobody else sees the list. We don't sell or share it.
- How long: an address that isn't confirmed is deleted after 7 days. A confirmed one stays until you unsubscribe. After that we keep it marked as unsubscribed, so no email we send can reach it, until you ask us to delete it.
- Unsubscribing: every email has an unsubscribe link, with no login. It opens a page with an Unsubscribe button: opening the link changes nothing, because some mail filters open every link in an email to check it. Mail apps that show their own Unsubscribe button unsubscribe you in one click. To have your address deleted entirely, email contact@teralis.dev.
- Your IP address: to stop one network flooding the form, our server counts sign-ups per IP address for 15 minutes, in memory, then forgets them. It never writes your IP address down.
This website
vitrel.app is a set of static pages and the alpha sign-up form. It sets no cookies, runs no analytics or tracking scripts, and loads nothing from other sites: its fonts, images and scripts all come from vitrel.app.
- Our server keeps no access log for vitrel.app's pages or the sign-up form, so there's no record of who visited or what they read. The one exception is downloads of the Mac app (the .dmg files): for each, it notes when and which file, without your IP address, deletes that within four days, and keeps only the number of downloads a day. If the server fails while answering a request, the error and that request's details, including the IP address, can go to the server's system log so the fault can be fixed.
- Cloudflare sits in front of our server: it handles the secure connection and passes requests on. It sees every request, including your IP address, the page asked for and what your browser sends with it, and shows us totals such as the number of requests and the countries they came from. It also asks Chrome and other browsers that support Network Error Logging to report failed connections to vitrel.app to Cloudflare. Successful visits aren't reported. What Cloudflare keeps is covered by Cloudflare's privacy policy.
- Vitrel's own lists, which the app fetches from api.vitrel.app, and the crash reports, feedback and sync it sends there go the same way: our server keeps no access log for them either, and Cloudflare sees those requests as it sees the site's. Update checks are the exception, described under Vitrel's own updates.
If you email us, we use your address only to reply.
Changes and contact
When Vitrel starts or stops sending something, we'll update this page and the date at the top.
Questions, or something here you think is wrong: contact@teralis.dev.