Privacy and security
This page explains how Breeze handles your notifications. The formal terms are in the Privacy Policy.
What happens when you send#
Your script sends the key and the notification to Breeze over HTTPS. Breeze looks up the device for that key and hands the notification to Apple Push Notification service for iPhones or Firebase Cloud Messaging for Android phones. They deliver it to the device. Plain HTTP is refused.
What the service stores#
Breeze stores what it needs to reach your device: a random installation ID, the device's push token, and hashes of your keys. It doesn't store notification content and has no way to list your past notifications. History lives only on your phone.
Your key is a password for sending#
Anyone with your key can send notifications to your device, but can't read your history, see your device, or manage it. Managing the device uses a separate secret that stays in the app.
- Keep the key in your tool's secret settings, not in code repositories, screenshots, or public chats.
- For automations that run often, send the key in the
Authorizationheader so it doesn't appear in URL logs. - If a key may have leaked, reset the link in the app. The old key stops working immediately.
Shared links#
A shared link (bz_g_) sends to up to 20 devices that have joined it. Removing a device affects new requests only; a notification already on its way can't be recalled.
End-to-end encryption#
HTTPS protects the request on the way, but Breeze, Apple, and Google can still read normal notifications while delivering them. For sensitive content, encrypt it so that only your iPhone can read it.
Deleting your data#
You can delete single messages or all of History in the app. Uninstalling the app stops delivery but doesn't delete the registration on the service. The Privacy Policy explains how to have it deleted.