Effective date: September 2, 2026
This End User License Agreement (the "Agreement") is between you and Cloud Bedrock LLC ("Cloud Bedrock", "we", "us"), and governs your use of the AlertRoster desktop and mobile applications, the receiver firmware images the desktop application installs, and the documentation that accompanies them (together, the "Software"). By downloading, installing, or using the Software you agree to this Agreement. If you do not agree, do not install or use the Software.
The AlertRoster hosted service — the accounts, alerting, scheduling, and synchronization service the Software connects to — is a separate service governed by our Terms of Service. This Agreement licenses the Software itself.
1. License
We grant you a worldwide, royalty-free, non-exclusive, non-transferable, revocable license to install and use the Software for personal or commercial purposes. You may install the Software on any number of devices you own or control, and you may download and copy it as reasonably necessary to obtain it, install it, evaluate it, and keep backups.
2. Where the Software comes from
We distribute the desktop application as signed installers through our official channels, including the public releases repository at github.com/CloudBedrock/alertroster-desktop-releases, and the mobile application through Apple's App Store. Copies obtained anywhere else are not from us, and we make no representation about them.
3. What you may not do
- You may not modify, reverse engineer, decompile, or disassemble the Software, except to the extent applicable law permits it despite this limitation or an open-source license covering a component allows it.
- You may not remove or alter proprietary notices in the Software.
- You may not sell, rent, lease, or sublicense the Software itself. Passing along an unmodified installer from our official channels, free of charge, is permitted.
- You may not use the Software in violation of applicable law.
4. Updates
When we release updates to the Software, we make them available at no charge through the channels above. We are not obligated to provide updates or maintenance. This Agreement does not entitle you to the hosted service: features that depend on it, including paid subscription tiers, are provided under the Terms of Service and may require payment.
5. Firmware, hardware, and physical outputs
The desktop application can write firmware and configuration — including network credentials — to compatible receiver hardware over a local connection, and receivers it manages can drive physical outputs such as relays, sirens, strobes, and other attached equipment.
- You are responsible for selecting, installing, powering, and maintaining any hardware you use with the Software, and for operating its outputs lawfully and safely in your premises.
- Writing firmware to a device carries inherent risk. The Software includes safeguards — for example, it refuses a firmware write that fails validation — but safeguards are not a guarantee, and an interrupted or failed write can leave a device inoperable. To the maximum extent permitted by law, we are not liable for damage to hardware, including a device rendered inoperable by a firmware write.
- A physical output may activate, fail to activate, or activate at the wrong time, including because of hardware condition, wiring, power, network conditions, or configuration. Do not rely on any output as the only way an alert can reach anyone.
6. Life-safety exclusion
AlertRoster is a call-out notification and escalation tool. It notifies people who have agreed in advance to be notified, and records what happened. It is not an emergency service and does not contact one on your behalf. It is not a fire alarm, a security alarm, or an alarm monitoring service, and it holds no life-safety certification. It is not a replacement for your team's official paging arrangements, and it should not be the only way a call-out can reach your people.
Alerts and outputs depend on networks, devices, and infrastructure outside our control. We make no representation that any alert will be delivered, or any output activated, at all or within any period of time.
7. Third-party components
The Software includes and links against third-party components — among them the Qt framework and the third-party code Qt bundles (such as zlib, libpng, FreeType, HarfBuzz, Zstandard, and OpenSSL) and, on Linux, system libraries such as libsecret and libgpiod. Those components are and remain governed by their own license terms, which are acknowledged in the THIRD-PARTY-NOTICES file distributed with the Software. Nothing in this Agreement limits rights those licenses grant you, and nothing in this Agreement grants you rights in those components beyond them.
8. Your data and credentials
Our Privacy Policy describes how we handle personal data. The Software also stores credentials locally at your direction — for example, an integration key in your operating system's keychain, and Wi-Fi credentials written to a receiver during setup. Protect the computers and boards that hold those credentials as you would any credential store.
9. Term and termination
This Agreement is effective until terminated. You may terminate it at any time by uninstalling and deleting your copies of the Software. We may terminate it if you materially breach it; where practical we will give you notice — by posting on our website or through the Software — and thirty days to cure the breach. On termination the license ends and you must stop using, and delete, your copies of the Software. Sections that by their nature should survive termination — including the life-safety exclusion, the third-party component terms, the warranty disclaimer, and the limitation of liability — survive it.
10. Changes to this Agreement
We may revise this Agreement. When we do, we will post the revised version at this address with a new effective date. The version of this Agreement in effect on the date a release of the Software is published is the version that governs that release; a later revision governs later releases, not the copy you already installed. Installing or using a release published after a revision takes effect is acceptance of the revised Agreement for that release.
11. Disclaimer of warranty
THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT ANY ALERT WILL BE DELIVERED OR ANY OUTPUT ACTIVATED.
12. Limitation of liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, CLOUD BEDROCK WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, DATA, OR GOODWILL, ARISING OUT OF OR RELATED TO THE SOFTWARE — INCLUDING DAMAGES ARISING FROM AN ALERT THAT WAS NOT DELIVERED OR WAS DELAYED, AN OUTPUT THAT ACTIVATED, FAILED TO ACTIVATE, OR ACTIVATED AT THE WRONG TIME, OR HARDWARE DAMAGED DURING A FIRMWARE WRITE — EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. OUR TOTAL LIABILITY UNDER THIS AGREEMENT WILL NOT EXCEED THE AMOUNTS YOU PAID US FOR THE SOFTWARE IN THE TWELVE MONTHS BEFORE THE CLAIM AROSE. SOME JURISDICTIONS DO NOT ALLOW CERTAIN LIMITATIONS, SO PARTS OF THIS SECTION MAY NOT APPLY TO YOU.
13. Export compliance
You may not use or export the Software in violation of United States export laws and regulations, or of the export laws of the jurisdiction in which you obtained it.
14. Governing law and venue
This Agreement is governed by the laws of the State of Michigan, without regard to its conflict-of-law rules, and any dispute under it will be brought in the state or federal courts located in Michigan. Both parties consent to the jurisdiction of those courts.
15. Contact
Questions about this Agreement can be raised through support.