The agreement, short enough that you might finish it.

The name on the contract

Buying here puts you in an agreement with Fortify 24x7. Cyb3rs3cur1ty is a trading brand of that company. The invoice, the descriptor printed on your statement and the legal counterparty are all one and the same.

What a line actually is

Every line buys a vendor platform, licensed by us and driven by our engineers on your behalf. Module pages describe the reach of each one, and their scope blocks describe the limits. Both halves count.

The licenses for those platforms are held by us. You are not purchasing something portable, and moving elsewhere means taking out your own license with the vendor involved.

How the money moves

• Rates are per unit and per month, exactly as the catalog displayed them at checkout.
• Money is collected when a monthly period opens, in advance, from whichever card Stripe holds.
• Subscriptions roll on month by month until cancelled.
• FORTIFY 24X7 is what a receipt or a statement will say.

A declined card does not switch protection off that day. We get in touch, the card is retried, and only after that does suspension enter the conversation.

Changing a subscription

Raise or lower a quantity, add a line, drop a line: the portal does all of it, and so does mailing us. An increase gets charged from the moment it applies. A reduction waits for the next period, since the current one has been paid already.

Cancelling

Cancel at any point, through the portal or over mail. Whatever you paid for keeps running until that period expires, and no part of the month comes back as days. There is no notice requirement and no exit fee.

When a subscription ends, agents come off and data inside the vendor platforms is deleted on that vendor's own timetable. Ask us before cancelling if copies of anything are needed first.

What we need from you

• Contact details that work, and a named person reachable when something is on fire.
• Permission and the access needed to install agents and connect tenants.
• Sensible cooperation through rollout and tuning, since that is where most delays begin.
• Quick answers whenever an alert requires a call that only your side can make.

Cover follows enrollment. A device nobody enrolls, or a tenant nobody connects, is not protected whatever an invoice happens to say.

What we are responsible for

Running your platforms competently and carefully, honoring the response arrangements printed on the module pages, and telling you promptly and plainly whenever the fault turns out to be ours.

What we are not responsible for

• Outcomes we did not cause. No security service prevents every incident. Running the controls properly is the commitment. Guaranteeing that nothing ever happens is not.
• Vendor platform outages. When a platform falls over we work the problem and keep you posted, but their infrastructure is not ours to control.
• Anything outside enrollment. Devices, tenants and systems nobody asked us to cover sit outside this agreement.
• Decisions you make. Where you ask us to permit something and harm follows, that request stands as your decision.

Ending the agreement

You may end it at any point, as described above. We may end it where invoices go unpaid after chasing, where the service is put to unlawful use, or where we are asked to work in a way that is unsafe or dishonest. Notice is always given, and the reason is always stated.

Changes to these terms

Terms can change. A change moves the date printed at the head of the page, and anything materially affecting what you bought reaches the account address before it starts to apply.