"We email the affected accounts"
A weaker answer than a public URL. It means you decide what counts as an incident, and the customer finds out when you decide to tell them.
The security questionnaire asks how you notify customers during an incident. One link answers that — and a few of the questions after it.
An enterprise buying process has places where not having a status page costs weeks:
A weaker answer than a public URL. It means you decide what counts as an incident, and the customer finds out when you decide to tell them.
An internal dashboard proves nothing externally — and external is exactly what is being asked about.
They end up as questionnaire attachments and go stale the same week. A link does not.
A year of incidents and maintenance the buyer can read themselves. That is the answer to the questionnaire.
A page can be password-protected, restricted to your customer's email domain, or reachable only from their IP ranges.
Their team subscribes and gets the updates directly — no separate emails from you during an incident.
The data-residency question has a short answer: our servers, in Lithuania. The contract is Lithuanian and the invoice carries VAT.
From then on, the incident-communication question is a one-line answer.
Yes. A password, an email domain, or IP ranges — you choose who sees it.
Yes: one public and separate private ones for large accounts. How many depends on the plan.
Yes, there is a setting to keep it out of the index.