A security-questionnaire question, answered without certification
Which subprocessors process or have access to customer data?
The honest answer pattern
Name every third party that touches customer data and what each one does — hosting, payments, model inference, email. A short, complete list with purposes is one of the strongest trust signals a small vendor can give. Omitting a subprocessor a reviewer later finds in your DNS or invoices costs more than listing it ever would.
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):
- Which subprocessors touch customer data?
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.