Privacy Policy
Effective September 25, 2026
Breeze Mobile keeps browser data on your device by default. This policy explains what the app stores, what it sends for features you use, and how to manage your account data.
Data stored on your device
Breeze stores browser history, bookmarks, open tabs, settings, reminders, and Nav chat history locally by default. App state and the account session are protected with Android Keystore-backed encryption. Cookies and other website storage are kept in the browser profile. The password vault uses a separate encrypted store that requires device authentication; saved website passwords are never included in cloud sync.
Websites and permissions
Websites you visit receive ordinary connection data and anything you choose to enter or share with them. They may store cookies and other site data in the browser. A site may request access to your camera, microphone, or location; Android and Breeze let you decide whether to allow it. Sites may offer passkeys through Android and the credential provider selected on your device; those credentials are handled by that provider, not Breeze cloud sync.
Breeze account
You can sign in with email and password or Google. Supabase Auth receives the sign-in details needed to operate your account. When you choose Google sign-in, Google shares basic account identity such as your email address. Breeze does not receive your Google password. Your Breeze session is stored encrypted on this device.
Optional cloud sync
Bookmarks, open tab URLs and titles, browsing history, Nav text and source links, and reminders each have a separate sync switch and start off. When you turn on a category, its data is sent over HTTPS to your account in Supabase. Synced data is not end-to-end encrypted by Breeze. Turning a category off stops future syncing but does not delete the existing cloud copy. Signing out removes synced data from this device, not from the cloud. Deleting your account removes its synced data.
Nav, images, and voice
When you send Nav a request, Breeze sends your prompt and relevant chat context to the Breeze Cloud service on Cloudflare, which may send it to OpenAI to generate a response. When page context is attached, the page title, URL, and readable text may be included. An image is sent only when you submit it with a request. Voice recordings are sent to Breeze Cloud for transcription, and the resulting text is used as your prompt. These providers process data under their own terms and privacy policies.
Reminders and notifications
Reminders are stored and scheduled on your device. If you sign in, enable Reminders sync, and allow notifications, Breeze can register this app installation with Firebase Cloud Messaging for reminder alerts. Firebase receives the app installation identifier and an opaque reminder identifier and due time; the reminder text is not included in the push and is fetched from the Breeze account after delivery. Delivery depends on Android notification settings, Google Play services, and network access. A local reminder notification can work without cloud push.
Export, deletion, and retention
Use Export my data to save a copy of browser data. Signing out clears synced copies from this device but leaves account data in the cloud and keeps the local password vault. Turning off a sync category does not remove its cloud copy. Deleting your account permanently deletes the account and its synced data. You can clear local browsing data from Breeze settings. Data sent to third-party providers is handled under their retention rules.
Use and sharing
Breeze does not sell personal data or use it for advertising. Firebase Analytics is disabled. Breeze shares information with Google, Supabase, Cloudflare, Firebase, OpenAI, or the website you choose to visit only as needed for the feature or connection you use. Breeze does not sync cookies, site storage, or the password vault.
Updates and contact
Breeze may check GitHub for app updates; this check does not include your browsing history or password vault. Questions or privacy requests: jake@winthenight.info.