Privacy Policy
Effective and last updated: November 14, 2026.
1. Scope#
This policy applies to the Breeze Push app, the push.breezelabs.dev and official staging push-stg.breezelabs.dev websites and the hosted push API. This policy explains how these services handle information. Our privacy and support email is sudoku42game@gmail.com.
Self-hosted servers, other Bark-compatible servers you choose and third-party automation tools are the responsibility of their respective operators; this policy does not replace their policies. The hosted service currently enables Apple APNs delivery. Android / Firebase Cloud Messaging (FCM) is available only when expressly enabled on the server; availability is determined by the capabilities API and current product information.
2. Information we handle#
Device registration and credentials#
When connecting to a server, the app sends a randomly generated installation_id, management_secret, Webhook key, APNs device_token, platform and push environment. We store the installation identifier, delivery token, platform, environment, enabled status, and registration/update times. Management credentials and Webhook keys are stored as hashes in the database. If you create shared channels or specialized push targets, we also store their identifiers, device associations, target tokens and types. Hashes and random identifiers can still be associated with an installation; they are not necessarily anonymous.
When you register an Android installation, we handle its Firebase Installation ID (fid), provider, Firebase project and application identifier (package name) to route delivery through Google to the correct app. Ordinary push-device registration does not require your name, phone number or email address.
Push and network data#
We receive the title, body, group, links, image/sound URLs, custom data and other supported parameters supplied by the sender for validation and forwarding. The current application database does not maintain push-body or delivery-history tables. However, the server and its infrastructure handle this content during request processing, and Apple, or Google where applicable, processes the payload submitted to it. This does not mean that the server cannot see plaintext or that every copy disappears immediately.
When you visit the website or API, Cloudflare processes IP addresses, request times, URLs, and network and HTTP technical information. The service uses source IP addresses and Webhook hashes for rate limiting. Keys or messages included in URLs may appear in browser history, calling tools, proxies or infrastructure records. For private content, prefer HTTPS POST with credentials in the Authorization header.
Local data and information you send us#
The app stores server addresses and Webhook links, settings, received-message history and media caches on your device. On iOS, management identity is stored in the system Keychain. On Android, management credentials are encrypted with a non-exportable AES-GCM key in Android Keystore and stored in the app’s private SharedPreferences. On iOS, encryption configuration is stored in local settings shared by the app and notification extension. Copying or sharing passes your selected content to the clipboard or system share destination.
If you send support email or voluntarily supply diagnostics, we handle your email address, message and attachments to respond and troubleshoot. Do not send private keys, management credentials or complete Webhooks.
3. Purposes#
We use this information to register and identify installations, authenticate sending and management permissions, route pushes, provide channels and local history, answer support requests, limit abuse, maintain security and availability, and meet applicable legal obligations. We do not sell user information or use notification content for advertising targeting. The current app and documentation site do not integrate advertising SDKs or product-behavior analytics SDKs.
4. Encryption, local history and backups#
The client communicates with the official service over HTTPS. Ordinary push content passes through us, Cloudflare and the platform’s Apple APNs or Google FCM before reaching your device. HTTPS is not end-to-end encryption.
The iOS app offers optional ciphertext / iv compatibility; the current Android app does not support this feature. Content placed inside ciphertext passes through the server in encrypted form only when the sender correctly encrypts it before uploading and manages the key appropriately. Unencrypted fields, routing information, timing and traffic characteristics remain visible. Enabling encryption settings in the iOS app does not automatically encrypt plaintext sent by other scripts. This feature is not a promise of end-to-end protection for every message, every mode or data stored on the device.
On iOS, decrypted messages may be stored in device history according to your settings. The current iOS app does not implement cross-device iCloud history synchronization. However, local files, settings and some system credentials may be handled by iOS backups, device migration or your system settings. Backup coverage depends on the platform and device settings; we do not guarantee that all local data on either iOS or Android is excluded from backups. Manage lock-screen previews, backups and access to your device accordingly.
5. Providers, third parties and international processing#
We use Cloudflare Workers and D1 for the API, website, registration records and service-authentication cache, and Apple APNs for Apple-device delivery. The service’s own push-authentication tokens may also be cached in the database; these are not your Apple account password. Google / Firebase handles the relevant push processing and delivery when Android functionality expressly enabled on the server is used.
These providers’ networks, processing facilities and support teams may be located in the United States, Japan and other countries or regions. Processing is not guaranteed to remain in your location. Where applicable law requires it, we will use the required oversight, contractual arrangements, disclosures or consent procedures. This policy does not replace any separate international-transfer consent required by law.
Your device may fetch remote notification images, icons or sounds directly from their hosts, revealing information such as its IP address, request time and URL to those hosts. Opening notification links, using external automation platforms or connecting to self-hosted servers is also subject to the relevant third party’s terms and privacy policy.
Provider information: Cloudflare Privacy Policy, Apple Privacy Policy and Firebase privacy and security information. Beyond processing needed for these services, we disclose relevant information only on your instructions or authorization, where legally required, or where necessary to investigate abuse or protect legitimate rights, limited to what is needed.
6. Website storage and operational records#
The documentation website uses browser localStorage to remember your light/dark theme preference. The current site does not use advertising-tracking cookies. Its send tool submits the credentials and content you enter to the API only when you initiate sending; it does not save Webhook credentials in that theme storage.
Current backend code does not intentionally write request bodies or credentials to application logs, and the hosted configuration disables Workers observability. However, Cloudflare, security services, push providers, your calling tools or operating system may generate network, security, error or delivery records. We therefore make no “no logs” guarantee. Manual diagnostics, support email and legally retained records may also contain information you voluntarily provide.
7. Retention and deletion#
- Server registration records: Kept while maintaining registration and delivery relationships. There is currently no automatic deletion based on installation inactivity. A token declared invalid by the provider may be disabled before its record is deleted. You can use the iOS app’s remove-server feature or the deletion API with management credentials to delete that installation and its associated Webhooks, channel memberships and specialized targets from the official server. The current Android app does not yet provide a server-removal interface. You may also request deletion at the contact email below; we verify control before processing it. Removing a device does not automatically delete an independently existing shared channel.
- Message bodies: Not retained as a message archive in the current application database. Request memory, upstream offline-delivery queues, network records and copies you keep follow their own processing lifecycles; deleting registration cannot recall all of them.
- Device history: You can delete individual or all history entries, disable default archiving or choose a retention period. Cleanup runs when the relevant functionality executes, and history is also subject to a local item limit. Clearing history does not guarantee removal of media/sound caches, system Notification Center entries, system backups or copies on other devices. Uninstalling the app does not delete server registration.
- Authentication caches, infrastructure and support records: Service-authentication tokens expire and are refreshed; expired database entries are not guaranteed to be physically deleted immediately. Infrastructure backups and logs rotate according to their configuration and provider rules. Support and security records are kept only as needed to handle requests, investigate incidents or satisfy legal obligations. Deletion does not mean immediate erasure from every backup; any legally required retained portion will have its use restricted.
8. Your choices and rights#
You can disable notifications in system settings, rotate Webhooks and manage local history in the app, and stop sending from your calling tools. iOS also provides server removal and encryption configuration; Android users can request deletion of server registration records at the contact email below. Disabling notifications does not automatically unregister server records; rotating a Webhook does not recall delivered messages.
To the extent provided by applicable law, you may request an explanation of processing purposes, access or correction, deletion, cessation of use or disclosure, withdrawal of consent-based processing, and lodge a complaint with the competent authority. Contact us at the email below with the server used, your request and non-sensitive information sufficient to locate the installation. We will verify control appropriately and respond as required by law. Do not include management or private keys in your initial email. If we cannot safely verify identity, the data no longer exists or the law limits a request, we will explain the applicable reason. Withdrawing consent does not affect the lawfulness of prior processing.
9. Security#
We use measures including encrypted transport, credential hashing, separation of sending and management permissions, input validation and rate limiting. Delivery tokens and some operational credentials must remain readable by controlled infrastructure; hashing does not replace keeping secrets confidential. No system can guarantee absolute security. Protect your device, sending scripts and Webhooks, and rotate exposed credentials promptly. We will handle and report data incidents as required by applicable law.
10. Children#
The service is intended for users able to configure pushes and automation and is not designed specifically for children. If you are below the local age for independently consenting to the service or personal-information processing, a guardian must participate as legally required. We do not knowingly collect personal information from children without required consent. Please contact us if you become aware of such a situation so that we can take appropriate restriction or deletion measures.
11. Changes and contact#
We publish the update date on this page. If purposes, data categories or sharing practices change materially, we will give appropriate notice and obtain prior consent where required by law. Descriptions of future features do not mean those features are already available.
Provider: Byte2020 Inc. Privacy, data-rights requests and support: sudoku42game@gmail.com. You may also use this email to request operator information, data-handling details and request procedures that must be made available under applicable law. The Terms of Service also apply to use of the service.