Browse docs +

Terms of Service

Effective and last updated: November 14, 2026.

1. Scope and acceptance#

These terms apply to the Breeze Push app, the push.breezelabs.dev and official staging push-stg.breezelabs.dev websites and hosted API. Read these terms and the Privacy Policy before using the service. If you act for an organization, you must have authority to do so. Obtain guardian consent first where local law requires it.

Software you host yourself and third-party servers are managed by their respective operators and may have different rules. Rights to open-source code are granted by the applicable open-source licenses; these terms do not withdraw those rights. Apple’s applicable platform terms and licensing rules may also apply when you download the app through the App Store.

2. Service and availability of features#

Breeze Push lets you use registered Webhooks to send messages from scripts or automation tools to your own devices or devices whose recipients have expressly authorized delivery. The hosted service currently enables APNs alert / background by default. Critical Alerts is not enabled. Android / FCM is available only when expressly enabled on the server; availability is determined by the capabilities API and current product information. Specialized push types, broadcasts, Web Push and other capabilities can be used only when expressly enabled and supported by the required client, permissions and configuration. Future plans or parameter enumerations in code or documentation are not a promise that a feature is already available.

You are responsible for selecting the correct service environment, recipient devices, parameters and third-party integrations. The service may return accepted, rejected, partial-success or unknown-outcome states. Success generally means only that the upstream push provider accepted the request, not that a device received it, a person saw it or any action was performed.

3. Credentials and control of devices#

A Webhook URL and key are sending credentials. Anyone holding them may be able to send messages to the bound devices. The management_secret is a separate credential used to rotate, remove or manage associations. Treat these values as secrets. Do not expose them in repositories, screenshots, logs, webpages or untrusted tools, and do not give management credentials to someone who only needs to send messages.

Register only devices and tokens you control or are authorized to use, and obtain shared-channel recipients’ consent. Rotate exposed Webhooks immediately. Removing a device or channel, stopping third-party automation and disabling system notifications are distinct actions. If management credentials are lost, we may be unable to verify control safely or recover registration. Sending permission alone does not entitle anyone to management access or information about another person’s devices.

4. Permitted use and abuse#

You must have the right to submit and transmit your content and comply with applicable law, recipients’ preferences, platform rules and third-party terms. Do not use the service to:

  • Send unsolicited spam, persistent harassment, threats, fraud, hateful or unlawful content, or infringe privacy, intellectual property or other legal rights;
  • Impersonate others, steal or trade credentials, register others’ devices without permission, scan or guess Webhooks, or operate an open push proxy for arbitrary tokens, topics, projects or destinations;
  • Distribute malware, phishing links or unlawful surveillance content, or disrupt devices or services;
  • Evade authentication, quotas, rate limits, suspensions or upstream restrictions, cause denial-of-service attacks, or conduct unauthorized security testing against resources you do not control;
  • Send another person’s sensitive personal information without the required authority and safeguards, or claim emergency, medical, safety or system privileges the service has not obtained.

Report abuse or exposed credentials to the email below with the necessary details, without including secrets that remain usable. We may investigate complaints, request clarification and take necessary restriction measures.

5. Limits, suspension and termination#

Request sizes, sending rates, target counts, push types and platform permissions are subject to current configuration and upstream limits. Published documentation and API limit information are not a promise of unlimited capacity or permanent quotas. Respect 429, Retry-After and error states. Do not unconditionally replay requests with an unknown outcome, because doing so may duplicate notifications.

To address abuse, leaks, abnormal load, security incidents, legal requirements or maintenance, we may restrict requests, close registration, disable tokens/Webhooks, or suspend or terminate relevant services. We will provide reasons or notice where reasonable and practicable. Emergencies, legal restrictions and security investigations may require action first. You may stop using the service, delete local history and remove registrations using the available management functions at any time. Suspension or termination does not recall delivered messages; information remains subject to the Privacy Policy.

6. Availability, upstream services and non-emergency use#

Delivery may be affected by networks, APNs, FCM where applicable, battery and connectivity, system permissions, Focus/Do Not Disturb, platform throttling and operating-system scheduling. Background pushes in particular may be delayed, combined or dropped. We do not guarantee continuous availability, fixed latency, delivery of every message, strict ordering or exactly-once delivery, and do not provide a service-level commitment unless expressly agreed separately.

Do not use this service as the sole or primary notification channel for emergency response, life safety, medical decisions, fire protection, security or other high-risk situations. Future support for higher priority or Critical Alerts would not replace a dedicated system with independent safeguards. Important workflows need separate monitoring, acknowledgement and fallback channels.

7. Content, privacy and third-party services#

You retain your rights to your content. You authorize us and necessary service providers to process and transmit it only to operate, protect and provide the service as you instruct. This does not transfer ownership to us or authorize advertising use of notification content.

Choose suitable data and encryption methods in accordance with the Privacy Policy. Ordinary pushes pass through infrastructure and upstream providers. Optional ciphertext functionality requires correct implementation by the sender; enabling client settings does not establish that every message is protected. We are not responsible for keeping a recoverable message archive or key backup for you.

Third-party automation tools, image/sound hosts, external links, Apple, Cloudflare and Google when Android functionality is used have their own terms and policies. If you host or connect to other servers, you must also arrange permissions, certificates, data protection and operations and comply with applicable platform and open-source license requirements.

8. Intellectual property and open-source software#

Breeze Push code, design and other materials are protected by applicable intellectual-property law and their respective licenses. The app includes components derived from Bark and other open-source projects. Their copyrights and licenses are governed by the bundled LICENSE, NOTICE, third-party notices and corresponding source code. These terms do not limit rights granted by those licenses. Using the service grants no rights to Apple, Bark or other third-party trademarks and does not imply their endorsement.

9. Fees and future features#

These terms alone do not create a paid subscription, automatic renewal or obligation to purchase future features. If paid features are introduced, pricing, billing periods, applicable limits, renewal/cancellation arrangements and legally required refund information will be presented before purchase for you to choose separately. App stores, network operators, self-hosted infrastructure and third-party tools may charge their own fees.

10. Liability and statutory rights#

To the extent permitted by applicable law, the service is provided as currently available. Delivery, availability or fitness commitments are not guaranteed unless expressly agreed separately. For problems caused by your configuration errors, exposed credentials, third-party outages, system restrictions or other circumstances outside reasonable control, we remain responsible to the extent required by law.

These terms do not exclude or limit liability that cannot lawfully be excluded or limited, including applicable mandatory liability for intentional misconduct, gross negligence, personal injury and other protected matters. They do not remove consumers’ statutory remedies, refund rights, data-protection rights or other non-waivable rights. Liability and its extent depend on the facts and applicable law; use of free or test functionality does not itself remove liability.

11. Changes, disputes and contact#

We publish the update date on this page and provide appropriate notice of material changes, obtaining separate agreement where required by law. Changes do not retroactively remove accrued statutory rights. If a provision is unenforceable, the remaining provisions continue to apply to the extent they can be separated.

For questions, complaints or disputes, please contact us first so that we can investigate and seek a resolution. These terms do not require you to waive remedies before competent authorities or courts, or restrict your legal rights through an unconfirmed jurisdiction, mandatory arbitration or a language-precedence rule.

Provider: Byte2020 Inc. Support, abuse reports and legal inquiries: sudoku42game@gmail.com.