Terms of service

What you are buying, and what you are not

This is a warning system, not a guarantee. It can miss an outage, report one late, or report one that is not happening.

Silent Outage watches signals you give it access to and tells you when they stop looking normal. It cannot see everything, the third-party status pages it reads are sometimes wrong, and a dollar figure on an incident is an estimate with a stated confidence and never an accounting record.

Nothing here is an availability commitment, and there is no service credit, because we would rather not offer one than offer one we cannot honour. If that is not enough for your situation, the software is open source and you can run it yourself.

The account, and the people in it

You sign in with an email address, by a link we send to it. There is no password, so there is nothing to reset and nothing for us to lose.

An account can hold more than one person. Whoever creates it is its owner, and an account always has at least one. An owner or an admin can invite somebody else by email address, choose the role they hold, change that role later and remove them again; removing somebody ends their sessions immediately and takes their own alert destinations with them.

What each role may do is the list below, and it is the same list the product itself enforces — a refusal you meet on a screen is this list, not a second one.

The account owner is responsible for everything done under the account: what they do themselves, what anybody they invited does for as long as that access lasts, and what any key, ping URL or other credential connected to the account does. Where an account has more than one owner, that responsibility is shared between them.

Keep the ping URLs private: anybody holding one can report your job as healthy, whether or not they are in your account.

• Owner — may read this account; acknowledge or resolve incidents; manage their own alert destination; change what this account monitors; invite or remove people; and change the plan, the sign-in address or delete the account.
• Admin — may read this account; acknowledge or resolve incidents; manage their own alert destination; change what this account monitors; and invite or remove people.
• Responder — may read this account; acknowledge or resolve incidents; and manage their own alert destination.

Payment credentials

If you connect a payment processor, you give us a read-only restricted key with the narrowest scopes that can answer the question, and we check the scopes ourselves before accepting it. We cannot move money, issue a refund, or read your customers.

Revoke it at any time from your payment processor. Revenue monitoring stops working; the rest of your account is unaffected.

Ending it

An account owner can delete the account from the account settings screen at any time, which deletes it for everybody in it. The privacy notice says what that removes and what it does not.

Anybody else can be removed from an account by an owner or an admin, which ends their access and leaves the account itself running.

We can close an account that is being used to attack somebody, to send traffic we did not agree to carry, or to break the law. We will say why.

The licence

Silent Outage is open source under the AGPL-3.0, and this hosted service runs that same code.

The client libraries are permissively licensed on purpose, so installing one places no obligation on the application you install it into.

• Source for this deployment: https://github.com/nmartinovic/revguard

Changes

If these terms change in a way that matters, the addresses already signed in to the account are where you will hear about it. We do not have another way to reach you, which is deliberate.