A security-questionnaire question, answered without certification
What uptime do you commit to? Is there an SLA?
The honest answer pattern
Only quote an uptime figure you actually measure, and only promise an SLA that exists in your contracts. A truthful alternative is to describe your hosting platform's availability model and your own monitoring, and to say plainly that no contractual SLA is offered at your current size. Mark a status page as planned if you intend one.
What a credible answer looks like
A credible answer is specific and current-tense only where it's true: it names your actual provider and systems, states what is in place today, and moves anything that isn't into a clearly labelled roadmap item instead of an aspirational “yes”. Reviewers read dozens of these a quarter — vague assurances are what get a vendor flagged, not missing certifications.
You can see this pattern applied end-to-end in the full sample security pack — a real trust page, three policies, and an answer bank generated by the same pipeline a paying customer uses, shown without any email gate.
The facts your answer needs (from the Trustpack intake):
- Do you publish uptime or status information?
- Where is your product hosted?
Answer the whole questionnaire, not one row
Trustpack turns your own attested answers into three security policies, a copy-paste answer bank covering the canonical questionnaire topics, and a live public trust page. Every document is vendor-attested and says so plainly — it never claims certification. Flat $49, one time.