Effective date: September 4, 2026 · Version 1
These Terms of Service (the "Terms") are between Cloud Bedrock LLC ("Cloud Bedrock", "we", "us") and the customer that holds an AlertRoster account (the "Customer", "you"), and govern the AlertRoster hosted service — the accounts, alerting, escalation, scheduling, and synchronization service (the "Service"). The person who accepts these Terms on behalf of a Customer represents that they are authorized to bind that Customer, and "you" includes the organization they act for.
The AlertRoster desktop and mobile applications, and the receiver firmware the desktop application installs, are licensed separately under the End User License Agreement, which each person who installs them accepts for themselves. These Terms bind the account; the EULA binds the people using the software. Our Privacy Policy describes how we handle personal data under both.
1. The Service
AlertRoster is a call-out notification and escalation platform. It holds a roster of people who have agreed in advance to be reachable, alerts the ones who are on when an event needs them, escalates if nobody acknowledges, and records what happened. It can additionally drive on-premise audible and visual alerting hardware at a site, and can raise alerts from monitoring systems, heartbeats and absence detection, voicemail left on a managed switchboard, and check-ins that were missed.
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.
2. No life-safety use
You may not use the Service as a substitute for a fire alarm, a security alarm, a medical alert service, an alarm monitoring service, or an emergency service, and you may not represent it to anyone as any of those things. Nobody at Cloud Bedrock watches or responds to your alerts, and the Service never contacts emergency services on anyone's behalf. Where a failure to receive an alert could contribute to injury or loss — which includes the call-out work the Service is built for — the Service must be one path among your team's arrangements, never the only one, and you are responsible for maintaining and testing the others.
3. Delivery is best-effort
Alerts are delivered on a best-effort basis over infrastructure outside our control, including Apple Push Notification service, the public internet, carrier and telephone networks, your own network, your responders' devices and their settings, and any on-premise hardware you operate. Device settings — Do Not Disturb, Focus modes, silent mode, notification permissions, low power mode — can suppress or delay alerts. We make no representation that any alert will be delivered, or any output activated, at all or within any period of time.
4. No service-level agreement
The Service is offered without a service-level agreement. We publish no uptime or delivery commitment, and no credit or remedy attaches to an outage or a delayed alert. If we later offer an SLA it will be a written, signed addendum; nothing in marketing material, support conversation, or status reporting creates one.
5. Your responsibilities
- Keeping rosters, schedules, and contact methods accurate, and removing people who should no longer be reachable through your account.
- Ensuring your responders grant the notification permissions the Service asks for, and keeping their devices, your network, and any on-premise hardware powered and functional.
- Independently verifying, on your own schedule, that the Service works for your use case end to end — that a test alert reaches the people it should.
- The people you authorize: activity under your account's credentials and integration keys is yours, and you are responsible for keeping those credentials protected and for revoking them when compromised.
- Using the Service lawfully, including obtaining any consent your jurisdiction requires from the people you enroll as responders or reach through managed telephony.
6. On-premise hardware
The Service can command third-party hardware — receivers, relays, sirens, strobes, and similar equipment — at your site. We supply software that commands that hardware. We do not manufacture, install, certify, or maintain it. Selecting, installing, powering, maintaining, and lawfully and safely operating hardware and its outputs in your premises is your responsibility. If you source hardware through a reseller or integrator, that relationship and its warranties sit between you and them, outside these Terms.
7. Accounts and acceptable use
Accounts are provisioned by us — today on request, later also by purchase. You may not resell the Service, probe or disrupt it, attempt to reach another customer's data, or use it to deliver unlawful, deceptive, or harassing alerts. We may suspend an account that is doing any of those things, or whose traffic threatens the Service for others; where practical we will tell you first.
8. Fees
Where an account is on a paid plan, fees, billing period, and renewal are as stated at purchase. We may change pricing for a renewal with notice before it takes effect. Accounts granted without charge remain without charge until we and you agree otherwise; we may withdraw a granted account with thirty days' notice.
9. Your data
Incident content may include operational detail about your systems, phone numbers, recordings from managed voicemail, and the names and contact methods of your responders. You retain ownership of it. We use it to operate the Service — delivering and recording alerts, resolving schedules, and producing the timelines the Service exists to keep — and handle personal data as the Privacy Policy describes. We may retain records after account closure where the law requires it or where the record documents an agreement, such as the acceptance of these Terms.
10. Term, suspension, and termination
These Terms apply from the moment an authorized person accepts them and for as long as the account exists. You may close your account at any time. We may terminate for material breach; where practical we will give notice and thirty days to cure. On closure the Service stops delivering alerts for your account — plan the transition of your call-out arrangements before closing. Sections that by their nature should survive — the no-life-safety-use terms, the delivery representations, the disclaimer of warranty, the limitation of liability, and the data terms — survive termination.
11. Changes to these Terms
We may revise these Terms. When we do, we will post the revised version at this address with a new effective date and version number, and material revisions must be accepted again by an authorized person before the account's administrators continue using the web application. The version an account most recently accepted is the version that governs it until the new acceptance is recorded.
12. Disclaimer of warranty
THE SERVICE 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 SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT ANY ALERT WILL BE DELIVERED OR ANY OUTPUT ACTIVATED.
13. 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 SERVICE — INCLUDING, AND ESPECIALLY, DAMAGES ARISING FROM AN ALERT THAT WAS NOT DELIVERED, WAS DELAYED, OR WAS NOT ACTED ON, OR FROM AN OUTPUT THAT ACTIVATED, FAILED TO ACTIVATE, OR ACTIVATED AT THE WRONG TIME — EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. OUR TOTAL LIABILITY UNDER THESE TERMS WILL NOT EXCEED THE AMOUNTS YOU PAID US FOR THE SERVICE IN THE TWELVE MONTHS BEFORE THE CLAIM AROSE, OR ONE HUNDRED US DOLLARS IF YOU HAVE PAID US NOTHING. SOME JURISDICTIONS DO NOT ALLOW CERTAIN LIMITATIONS, SO PARTS OF THIS SECTION MAY NOT APPLY TO YOU.
14. Governing law and venue
These Terms are governed by the laws of the State of Michigan, without regard to its conflict-of-law rules, and any dispute under them 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 these Terms can be raised through support.