Privacy Policy
Last updated: 30 October 2026
Peak Browser (“Peak,” “we,” “our,” or “us”) is designed as a local-first browser workspace for Apple platforms. This Privacy Policy explains how information is handled when you use Peak, and how this website is handled separately.
Our Privacy Model
Peak does not run a built-in analytics pipeline, advertising tracker, or user-account service. We do not sell your data, and we do not operate servers that store your browsing history, notes, tasks, chats, whiteboards, bookmarks, or workspace data.
Most Peak data is stored locally on your device. If iCloud sync is enabled, that data may sync through your private Apple iCloud account using CloudKit.
Some optional features do reach outside your device: cloud AI models, the websites you browse, things you share with other people, your mail account, Telegram and Siri if you turn them on, servers and banks you connect, and Lineup's weather, map, and country data. Each is described below, and none of them is required to use Peak.
Information Stored On Your Device
Peak may store the following data locally so the app can function:
- Browsing history and search/activity logs
- Bookmarks and bookmark groups
- Saved sessions and workspaces
- Notes, note images, and attachments
- Kanban task boards
- AI chat history
- Whiteboards and whiteboard assets
- Mesh messages and peer/workspace metadata
- Arcade/game state where applicable
- Bots: their instructions, memories, reference files, look and voice settings, and the threads they answer
- Peak Hours: timesheets, projects, clients, invoices, expenses and their receipts
- Finance: accounts, transactions, budgets and goals
- Drawings, developed photos, PDFs, songs, voices, and the rest of your media library
- App settings, workspace profiles, and preferences
This data is stored in app-local storage such as Core Data, app support files, UserDefaults, and Apple Keychain where appropriate.
iCloud Sync
Peak can sync workspace data through your private iCloud account using Apple CloudKit. We do not have access to your private iCloud database. iCloud data is handled by Apple under Apple's privacy and iCloud terms.
Sharing With Other People
You can share a board, whiteboard, note, calendar, project, site, drawing, deck, Finance accounts you choose, a Social or ASO Studio, or a Peak Hours team with other people. Shared things are kept in your own iCloud account, in a space Apple's CloudKit shares with the people who join through the link you send, and are end-to-end encrypted. Peak runs no server in between and cannot read them.
Everyone in a shared thing can see and change what is in it, and sees your name beside what you changed. Members of a Peak Hours team send the weeks, time off and expenses they hand in to the team's approvers. When people are near each other, changes can also travel directly over Peak Mesh, readable only by devices in that shared thing. If you leave, or stop sharing, each person keeps the copy they have.
Mail is optional. If you connect an account with an app password, Peak talks directly to your mail provider's servers over encrypted connections; nothing passes through a Peak server. The app password is stored in Apple Keychain on your device. Drafts are saved in your account's own Drafts folder.
Peak AI can search and read your mail and write drafts, asking you each time. When it does, the mail it reads is part of the request sent to the AI model you use — on your device, or to the cloud provider you chose. Peak AI cannot send mail; only you can.
Telegram And Siri
Telegram is off until you turn it on. If you connect a Telegram bot you made, messages between you and that bot — and anything an agent sends you there, after asking — pass through Telegram's servers under Telegram's privacy policy. The bot's token is kept in Apple Keychain, and Peak answers only the accounts you pair with a code. When a Telegram conversation asks Peak to change something, the request and its Allow buttons are sent to that chat; saving a key, invoices, handed-in weeks and your bank details can be approved only on the Mac.
Asking Peak through Siri is off until you turn it on. Siri hears and transcribes your words under Apple's privacy policy, then hands them to Peak AI, which treats them as any other message — on your device, or to the provider you chose.
Connected Servers And Your Other Devices
If you add a server that speaks the Model Context Protocol, Peak AI may send it the requests needed to use its tools, under that server's own terms. A tool that would change something asks you first unless you say otherwise. Your own devices can also use each other's tools over the encrypted Mesh; each device decides once what the others may do, and every device starts as read only.
On the Mac, Peak can itself act as an MCP server for AI apps on that Mac. It is off until you turn it on, only apps holding its token can connect, it is read only until you allow changes, and what each app does is recorded in a chat.
Bank And App Store Connections
Finance can follow your bank accounts through open banking with an Enable Banking application you register yourself. Your bank's own sign-in runs inside Peak, the application's key stays in Apple Keychain, and transactions come straight to your device. Peak AI never moves money.
ASO Studio can use an App Store Connect key you add. It is kept in Apple Keychain and used only to sign requests to Apple's App Store Connect API.
Peak Hours' connections are off until you turn each on in Setup → Connections. App Store reads your financial reports from App Store Connect with that key, and fetches the European Central Bank's public exchange rates to estimate them in your currency. Receipts in Mail searches the mail accounts Peak already reads, on your device, for receipts, and keeps one you record as a PDF beside the expense. Toggl Track uses an API token you add, kept in Keychain, to read your recent time entries from Toggl. Public holidays outside Norway come from the open Nager.Date service, which is sent only a country and a year. Nothing from these connections is recorded until you record it.
Watches And Web Search
Web searches that Peak AI, bots, watches and connected apps make go to DuckDuckGo, or to the Brave Search API if you choose it and add a key of your own; the search words are then sent to Brave under Brave's privacy policy. The address bar's search engine is separate, and is whichever you choose.
Watches are off until you make one. A watch fetches the page, feed or listing you gave it, or asks its search of the sources you chose — the web search above, Reddit, Hacker News through Algolia's search, GitHub, or Apple's App Store reviews — from a Mac of yours, identifying itself as Peak and following each site's robots.txt. If you write what you are looking for and turn judging on, the titles of new finds and that sentence are judged by Apple's model on the Mac, on the device, or, where it is not available, sent to a fast model on your OpenRouter key; the editor says which. Watches and their finds sync end-to-end encrypted through your iCloud. If you choose to be told on Telegram, the new finds and their links are sent to your paired Telegram account.
API Keys And Secrets
If you add an API key for an AI provider — OpenRouter, Anthropic, OpenAI, Google, xAI, Mistral, Groq, ElevenLabs, fal.ai, OpenCode, Moonshot, Kimi Code, or Ollama Cloud — Peak stores it securely in Apple Keychain on your device. Each key is used only to make requests to the provider it belongs to, when you choose to use cloud AI features. Open-Meteo and optional future flight-provider credentials are stored in Keychain too; flight-provider keys are not transmitted while real-fare integration remains unavailable. Keys are never sent to our servers.
Mesh passphrases and related encryption material are also stored using Keychain-backed storage where applicable.
AI Features
AI features are optional.
If you use local Ollama models, requests are sent to your local Ollama service on your device or local machine.
If you use a cloud provider, your prompts, chat messages, selected context, and any attached content needed for the request may be sent to that provider. Those providers process the request according to their own terms and privacy policies.
Image, video, music, speech, and transcription go to OpenRouter or, where you have added that provider's own key, directly to it: Google, OpenAI, or xAI for pictures and video; fal.ai for video; ElevenLabs for music, voices, and transcription; Groq and Mistral for transcription. Settings → AI chooses which is tried first. If one is refused or unavailable, Peak tries the next one you have a key for, so a request can reach a second provider you set up. Nothing goes to a provider you have not given a key.
When you add an OpenRouter key, Peak asks OpenRouter what is left on that key and your account, to show it in Settings → Keys. Only the key is sent. When you start typing to a cloud model, Peak opens the connection to that provider early so the reply starts sooner; that carries no prompt and nothing about you.
Keep requests in the EU. With this switch on (Settings → Keys), each provider is asked at its European address where it has one: OpenRouter's (on its Business plan), OpenAI's (for a key from a project made with Europe as its region), and ElevenLabs' EU data-residency server (for accounts that have it). Mistral is a French company serving from the EU, and models on your own devices never leave them. A provider with no European address — Anthropic, Google, xAI, Groq, fal.ai, Moonshot, OpenCode, Ollama Cloud — is not asked at all while the switch is on; Peak never falls back to a global address instead. Where data goes after it reaches a provider's European address is set by that provider's own terms.
Semantic search over your own library is off until you turn it on, and how it is built depends on the embedding source you choose. With Peak Local, the index is built by a model on your own device and nothing is sent anywhere. With a cloud embedding provider, building the index sends the titles and text of your bookmarks and notes — and your history, if you include it — to that provider to be turned into embeddings. Either way the embeddings are stored in one file on your device and the search runs locally; nothing is sent again unless you rebuild the index.
If you use a model running on your own device — Peak's own engine, Apple Intelligence, or Ollama — the prompt, the context, and the reply stay on the device. No request is made to any provider.
Peak does not use your AI chats for our own training, analytics, or advertising.
Speech On Your Device
Peak can transcribe speech without sending audio anywhere, using a model that runs on your Mac or iPhone. It is off until you turn it on in Settings → Local Models.
On macOS 26 and iOS 26, live dictation uses Apple's speech recogniser on your device instead: the words appear as you speak, and nothing is recorded or uploaded.
Voices you make in Understudy are made on your device, after Peak asks whose voice it is; that answer is kept with the voice, and the clip is not. If you choose a cloud voice for Peak or a bot, the text being read aloud is sent to the provider of that voice — OpenRouter, Google, OpenAI, or ElevenLabs — to be spoken.
Turning it on downloads that model once, from Hugging Face. The request carries nothing about you beyond what any file download does — no account, no identifier, and none of your text or audio. Nothing is sent there again unless you remove the model and download it afresh, and you can delete it at any time in the same place.
After the download, everything happens on your device. Recordings you transcribe are read locally and never uploaded. When you dictate a message, the recording is transcribed and then deleted immediately; it is not kept, and it is never sent to us or to anyone else.
Reading a response aloud uses the speech voices built into your operating system. Nothing leaves the device for that either.
Transcription through a cloud provider remains available and is what Peak uses when the on-device model is switched off, or for languages it does not cover. In that case the audio is sent to the provider you configured, under their terms.
Filtering And Reporting Generated Content
Before a picture or a video is asked for, Peak checks the request on your device and does not send sexual content, nudity — including undressing someone in a photo — or anything suggestive involving children. A request it declines is not sent to any provider, and Peak keeps no record of it beyond the conversation it was typed in.
Generated pictures, clips, and recordings have a Report… action. It opens your own mail app with a message to us that names the item, when it was made, the model where Peak knows it, and your version of Peak; nothing is sent until you send it, and only what is in that message reaches us. The item itself is not attached. We use reports only to answer them and to improve Peak's safeguards, and delete them once they are resolved.
Markings On Generated Media
Images, audio, and video generated in Peak carry metadata recording that an AI model produced them, which model, and when. This is written into the file itself and travels with it when you export or share it. It identifies the model, never you — no account, device, or personal identifier is included.
From Peak 1.9, generated media also carries an invisible watermark holding only that it came from Peak and the day it was made, and signed Content Credentials (C2PA). The signing key is made on your device and never leaves it; its certificate names Peak, not you. To date a signature, Peak sends a fingerprint of the credentials — never the file — to DigiCert's public timestamp service; offline, the file is signed without a date. Text written by a model on your device carries a watermark in its choice of words and nothing else.
AI Check, in Tools, reads these markings on your device; nothing you check is uploaded. The checker on this website runs in your browser in the same way.
Reading Public Code Repositories
If you ask Peak's assistant about a public GitHub repository, Peak requests the file listing and the specific files needed to answer from GitHub's API. Nothing is cloned, and the fetched text is held in memory for that conversation only — never written to disk. If you have added a GitHub token for publishing, it is sent with those requests so private repositories you own can be read and so rate limits apply to your account rather than anonymously.
Web Browsing And Search
Peak uses WebKit for browsing. When you visit websites or use a search engine, your device connects directly to those websites or services. Those third-party websites may collect information according to their own privacy policies.
Peak does not control the privacy practices of websites you visit.
Lineup: Waves, Weather, Maps, And Country Data
Lineup, formerly Peak Surf, is optional. It contacts the third-party data services described below only when you use the relevant features.
Waves are simulated on your device. By default, Peak generates swell height, period, and direction locally using its own model. These figures are a plausible simulation, not a forecast. They are labelled “Simulated” wherever they appear, nothing about them is sent anywhere, and they must never be used to judge whether it is safe to enter the water.
Weather comes from Apple Weather. To show wind, cloud, precipitation, and sunrise and sunset times for a surf spot, the coordinates of that spot are sent to Apple's WeatherKit service. WeatherKit provides no ocean swell, which is why wave data comes from a separate source. Apple handles this data under Apple's own privacy policy.
Open-Meteo is opt-in and needs your own API key. Peak does not contact Open-Meteo unless you add your own Open-Meteo API key under Settings → About → Surf Data Sources. Their free endpoint is licensed for non-commercial use only and Peak does not use it. If you add a key, the coordinates of spots you view are sent to Open-Meteo to fetch weather, marine conditions, and sunrise and sunset times, and Peak shows the attribution “Weather data by Open-Meteo.com” that their CC BY 4.0 licence requires. Open-Meteo states that their server logs may retain information such as IP addresses, requested URLs, and the coordinates within them for up to 90 days. Your key is stored on your device.
Country summaries come from Wikipedia. When you open a country in the surf travel passport, its name is sent to Wikipedia's API to fetch a summary. That text is contributed by Wikipedia's volunteer editors and reused under CC BY-SA 4.0; Peak links to the specific article it quotes. Requests are handled by the Wikimedia Foundation under the Wikimedia privacy policy.
Country indicators come from World Bank Open Data. Population, GDP per person, fertility, and life expectancy figures are fetched by sending a country code to the World Bank API. This data is licensed CC BY 4.0.
Maps come from Apple. Maps, satellite imagery, and geographic presentation are provided by Apple Maps through MapKit, which displays its own attribution on the map itself.
Forecast and country information may be cached on your device so Peak does not repeatedly re-request it. Peak does not sell any of this information, and does not use it for advertising or tracking.
Microphone
Peak uses the microphone only while you are actively dictating — when you press the microphone button and until you press stop. It is never used in the background, and Peak does not listen for a wake word.
The recording exists only long enough to be turned into text, and is deleted as soon as that is done. Where on-device transcription is switched on, that recording never leaves your device at all.
Location
Peak does not use your device's location and does not ask for permission to. Where a feature needs a place — a home break in Lineup, a spot on the surf map, a flight's distance — you type it, and the place name is looked up with Apple's geocoder. Only the coordinates of the places you look at are sent on, to Apple Weather and, if you have added your own key, to Open-Meteo, as described above.
Local Mesh Collaboration
Peak Mesh is an optional peer-to-peer feature built on Apple's Network framework. When enabled, Peak may share selected data with the peers you are connected to, depending on your mesh settings. This can include chat messages, tab shares, workspace signals, note/task/whiteboard updates, AI chat sync, Site Builder tab presence, game invites, and gameplay state. You control which workspace categories participate.
Peak operates no relay and no server in the middle: a mesh connection is always directly between your devices, encrypted, and authenticated with the room secret you set. Peak cannot read what passes over it.
Peers are found in three ways. Nearby devices are discovered on the local network. Devices can also connect over Apple's peer-to-peer Wi-Fi with no network at all. And you can write down a peer's address yourself, which dials that device directly — including one on a different network, over the internet. A written-down peer is a deliberate act: nothing is dialled that you have not entered.
Sharing a Site Builder tab shares that the editor is open and which project it is. On your own devices that opens the copy already synced through iCloud. On another person's device, opening that tab asks your device to send the project — its files and source — and only projects you currently have open and shared can be asked for. Send to Peer, inside a project, sends one deliberately at any time. No project leaves your device unless you share the tab or send it.
A Mac can lend its local models to your other devices. It is off until you turn on Lend this Mac's local models; then a peer in your mesh can send that Mac a prompt and get the reply, both over the same encrypted connection, and the Mac spends its own processing time answering. Anyone who holds your mesh passphrase counts as such a peer, so lend only on a passphrase you give your own devices.
Analytics And Tracking In The App
The Peak app does not include built-in third-party analytics, advertising SDKs, or cross-app tracking. We do not sell personal information.
This Website
This section covers www.peakbrowser.app only, and describes something the app itself does not do.
This site runs no analytics at all. There is no Google Analytics, no tag manager, no advertising pixel, and no third-party script of any kind. Nothing is loaded from another company when you read these pages.
Because nothing is collected, there is nothing to consent to, and no cookie banner to dismiss. The site sets no cookies and writes nothing to your browser's storage.
Until August 2026 this site offered Google Analytics behind an opt-in banner. It was removed: a page about a local-first browser was asking to be allowed to watch you read it, and the question was better answered by not asking. Any consent recorded under the old banner is now unused, and the code that read it is gone.
The site is hosted on Vercel, which keeps standard server request logs. Search engines report their own aggregate figures — how often a page appeared in results and how often it was clicked — which we can see for this site without anything being added to it.
None of this touches the app. Installing Peak does not carry any website analytics with it.
Data Deletion
You can delete Peak data from inside Settings. Depending on your configuration, deleting synced data may also remove it from your private iCloud-synced workspace.
You may also remove the app from your device to delete local app data, subject to Apple platform behavior and any iCloud sync settings.
Children's Privacy
Peak is not directed to children under 13. We do not knowingly collect personal information from children.
Changes To This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated “Last updated” date.
Contact
If you have questions about this Privacy Policy, contact us at Designr.pros@gmail.com.