Privacy Policy
Effective June 23, 2026
Breeze is a native macOS browser. This policy explains what stays on your Mac, what is sent when you use Nav, and how Breeze Cloud makes cloud AI work without exposing provider credentials in the app.
Short Version
- Breeze does not run ad-tech telemetry. We do not build browsing profiles, sell browsing data, or track you across sites.
- Normal browsing data stays on your Mac. History, bookmarks, pins, generated image files, settings, and local chat history are stored locally unless you delete them.
- Nav uses Breeze Cloud. When you ask Nav for help, Breeze sends your prompt and relevant context through Breeze Cloud to supported AI services.
- No provider credential is stored in the app. Provider credentials are held server-side, not inside the browser app.
- Daily fair-use limits apply. Breeze Cloud currently allows 30 chat requests and 10 image generation/edit requests per client per day.
Data Stored Locally by Breeze
Breeze stores browser state in your macOS user account, including settings, history, bookmarks, pins, tab metadata, chat history, reminders, usage estimates, and generated images. Passwords and passkeys are handled through Apple Passwords/iCloud Keychain rather than a Breeze-hosted password service.
Incognito tabs are designed to wipe browsing state for that session when closed. Website cookies, caches, and local storage are still controlled by WebKit and macOS storage rules while a session is active.
What Nav Sends to Breeze Cloud
Nav needs cloud processing to answer, act, generate images, and edit images. Depending on the request, Breeze may send:
- Your typed prompt and recent chat turns.
- Text from the current page, selected text, or @-mentioned tabs when relevant.
- Recent history/bookmark/open-tab context used to make the answer useful.
- Attached image data and local Vision/OCR descriptions when you ask for image edits or image-aware help.
- A client identifier and request identifier used for daily quota and duplicate-request handling.
Breeze Cloud forwards AI payloads to supported AI service providers and returns the response to the app. Breeze Cloud does not intentionally store prompts, replies, images, or generated outputs in a database.
Cloudflare Worker Processing
Breeze Cloud currently runs on Cloudflare Workers. Cloudflare may process request metadata and Worker observability/logging data as part of operating the service. Breeze uses a Durable Object to store per-client daily quota counters and recent request IDs so limits can reset daily and duplicate requests are not double counted.
AI Service Provider Processing
Depending on the feature and request, Breeze Cloud may connect to third-party AI service providers such as OpenAI, Google, Anthropic, or similar providers. Those providers may process request content and request metadata under their own API terms and data-control policies. Breeze selects providers server-side and may change them over time to improve quality, reliability, cost, or feature support.
Generated Images
Generated images are saved locally on your Mac so they can appear in History → Images. Downloading an image copies it to your Downloads folder. If you attach images for editing, those image files are sent through Breeze Cloud to an AI service provider for that request.
Website Data and Third-Party Sites
Breeze is a browser. Websites you visit may collect data according to their own policies. Breeze’s ad blocker can reduce trackers, but it cannot guarantee every third-party script or server request is blocked.
Children, Sensitive Data, and AI Limits
Breeze is not intended for children under 13. Do not send highly sensitive personal, medical, financial, legal, or confidential information to Nav unless you are comfortable with that information being processed by Breeze Cloud and its AI service providers.
Changes
This policy may change as Breeze changes. Material changes will be reflected on this page and may also appear in Breeze’s What’s New page.
Contact
Breeze is published by Win The Night Productions / Froydinger Design Systems. Use the project’s GitHub repository for issues and public questions.