A security-questionnaire question, answered without certification
Do you have a published privacy policy?
The honest answer pattern
Link the policy and make sure it names the same subprocessors and retention windows as your security answers — reviewers cross-check them. If the policy is out of date relative to your stack, fix it before sending the questionnaire back. Internal contradictions cost more credibility than any single missing control.
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):
- What categories of customer data do you store?
- Which subprocessors touch customer data?
- What is your product's website?
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.