A security-questionnaire question, answered without certification
Which of your staff can see our data, and when would they?
The honest answer pattern
Name the roles with access and the circumstances — debugging and support with the customer's knowledge is the honest norm for small vendors. If access is unaudited today, pair the admission with the logging you do have. Specificity about who and when is what separates this answer from a worrying 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):
- Who can access production systems and customer data?
- Do you keep audit/access logs?
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.