Terms of Service

Section IWhat is being bought

Managed security work, sold one unit at a time and run by us on the platforms that each Article page identifies by name. The available lines cover detection and response, application allowlisting, mail defense together with awareness training, management of endpoints and mobile devices, the discovery and encryption of regulated records, and backup with recovery testing.

Whatever cadence, retention, storage allowance, and platform coverage the Article page carried on the day you subscribed is what governs your line. Where an Article states a boundary, the boundary is part of this agreement. It is not softening language, and we will not later argue that it meant something looser.

Section IICharges, and when they fall due

Each line bills once a month, up front, at the rate published beside it, against the unit printed next to that rate: one mailbox, one endpoint, one tenant, one licensed user, one company file, one cluster agent. Stripe collects the money. The line on your statement will read FORTIFY 24X7.

The subscription rolls forward monthly until you end it. A change of quantity reaches the invoice after it, never the one already settled, and we do not re-bill a period you have paid for.

Section IIIBringing it to an end

Cancel whenever you decide to. The billing portal will do it, and so will a letter or an email sent from the account address. What cancellation does is stop the renewal that would otherwise follow; anything already paid for runs on to its expiry, then lapses. Money already taken is dealt with under Refunds and cancellation.

Section IVCustody of what we hold

Material in our keeping is sealed with 256-bit AES where it rests, protected while it moves, and stored on infrastructure separate from the estate it covers. Ownership does not travel to us at any point. Our people go into it in exactly three cases: running or restoring the service requires it, you have told us to, or a law compels us with no room left to refuse. The detail sits in the Privacy document.

Section VWhat is required of you

• Placing our agents on each machine, or granting the platform connectors their consent, so that a protection has something to attach itself to.
• Keeping a working card on file and a monitored mailbox on the account. Failure notices, security findings, and sign-in links all land there.
• Checking that the quantities you entered describe the estate you intended to cover. We bill what was entered, and no Article defends a machine or a tenant that never made it into scope.
• Warning us ahead of a change that breaks the arrangement: a tenant migration, a fleet reimage, a switch of identity provider.

Section VIStandard of care, and its limits

We perform with the commercial skill and care you would expect of people who do this for a living. A good deal of what security and recovery depend upon lies beyond our reach: your links to the outside world, whether the covered systems are up at all, what the platform vendors expose through their interfaces, and the choices your own people make at a keyboard.

Within whatever limits the law allows, what we can owe on one claim is bounded by the fees taken from you in the three months preceding the claim, and consequential or indirect loss falls outside. Liability that cannot lawfully be excluded is not excluded here.

Section VIIAmendment

These terms may be amended. Anything material reaches the account address 30 days or more ahead of the day it takes hold. Remaining on the service beyond that day accepts it; if you would rather not, cancel before the date and your final period runs under the terms originally agreed.

Section VIIIWhere to write

Fortify 24x7 · support@constitutioncomputing.com