There is no profile to build or identity to follow.
Privacy · Effective November 8, 2026
Your browsing
stays yours.
Crest has no account system, analytics pipeline, advertising SDK, or browsing-data backend. Crest does not collect or receive your browsing history, searches, passwords, cookies, or website data.
No tracking SDK, advertising identifier, or behavioral telemetry.
Your activity is not sent to Crest or its developer.
The short version
Crest is a browser,
not a data business.
Crest does not sell, rent, profile, or share your personal information because Crest does not collect it. There is no Crest-operated service receiving the pages you visit, the searches you make, or the accounts you use.
Like every browser, Crest connects directly to the websites and services you choose. Those services receive the requests needed to work and handle them under their own privacy policies. Optional Apple services are covered separately below.
01
What stays on your devices.
Cookies, website storage, service workers, downloads, and active page state stay on the device where you use them. Crest keeps this browsing data isolated by Space so one context does not silently become another.
Passwords are stored with the system Keychain. Crest does not upload password values to a Crest server. Private Spaces use temporary website storage and do not join ordinary history, restoration, archive, or synchronization.
02
iCloud is optional.
If you enable Crest sync, Space identity, pinned and saved tabs, current tabs, history, and archive records can sync through your private CloudKit database. This is an Apple service associated with your iCloud account; Crest does not operate a parallel copy.
Password values never enter CloudKit. Each Space has a separate switch for syncing those encrypted Keychain items through iCloud Keychain. Cookies, website data, service workers, downloads, and active page state remain device-only.
About private CloudKit databases at Apple03
Requests go where you send them.
When you visit a website or search the web, Crest sends the request directly to that website or to your selected search provider. The recipient and the network carrying the request may receive ordinary connection information such as your IP address, browser details, and the page or search you requested. Their policies—not Crest's—govern what they do with it.
When content blocking is on, Crest blocks ads and trackers on your device, on Chromium and WebKit pages, using public filter lists such as EasyList and uBlock Origin’s. Crest downloads each list you use directly from its maintainer, with no cookies and nothing about the pages you visit; like any website, the maintainer receives ordinary connection information such as your IP address. The same applies to a list you add by its address, which Crest downloads from that address, and to the small scripts some lists use to fix sites that fight ad blockers, which Crest downloads from its own GitHub releases and checks against a fingerprint built into the app before using. The lists you add and the filters you write stay on your device and are not synced.
On Mac, Crest’s Chromium engine is Chromium with Crest’s privacy changes. It sends Google none of your browsing, form, account or usage data. It contacts Google’s update service only to keep certificate revocation lists, trusted root certificates, the file types download warnings use, the Widevine module for protected video, and your extensions up to date. Those requests name each component or extension and its version, and carry no identifier for you or your device. When you install an extension from the Chrome Web Store, Crest downloads it from the same service. Extensions you add can see and send data according to their own permissions and policies.
Chromium does not include a site or download reputation service or remote Web Push. Read the engine protection and notification details for the controls and limits.
04
This website and TestFlight.
This product site is static. It has no Crest analytics, tracking pixels, advertising, cookies, account forms, or embedded third-party media. It is hosted by GitHub Pages; GitHub says it logs visitor IP addresses for security and may collect ordinary website usage information under its own policy.
Apple handles TestFlight enrollment and beta delivery. While you use a TestFlight build, Apple may provide Crest's developer with crash reports. Testers can also choose to send screenshots, comments, or other feedback through TestFlight. Crest adds no separate telemetry to those builds.
05
Your data remains under your control.
You can clear site data and history, remove saved credentials, delete a Space, disable iCloud sync, or turn off iCloud Keychain syncing for an individual Space. Data kept on your devices remains until you clear it, remove the app and its data, or the operating system removes it. Synced data remains in your iCloud account until it is deleted through Crest or your Apple account.
If this policy changes, the new version will be posted here with a revised effective date. A future feature that changes what Crest collects would require this policy to change first.
Reach the developer through the Crest community on Reddit or the Crest Discord. Both are public, so do not include passwords, account details, private URLs, or other sensitive information.