Hushwire

compliance

Answering the AI section of a SOC 2 vendor questionnaire

How to answer “Do you use AI tools that process our data?” on a client security questionnaire.

Security questionnaires now ask which AI tools touch client data, where data goes, how long it is retained and whether it trains models. Answer each with the tool’s written policy, not a general reassurance.

Hushwire is not SOC 2 audited. What it gives you is a precise, checkable description of its data flow: request bodies are never written to a database or log, metadata is kept 30 days, and requests only reach open-weight models.

Checklist

  • □Name the tool and the models it calls.
  • □State retention for prompts and outputs (Hushwire: none) and for metadata (30 days).
  • □State whether data trains models (Hushwire: no).
  • □Describe the data flow, or attach the data-flow diagram.
  • □Do not claim certifications the vendor does not hold.

This is practical guidance, not legal advice. Check your contracts with the client or a lawyer.

What Hushwire gives you

A backend for coding agents that stores no prompts, code or completions, never routes to OpenAI or Anthropic, and gives you a downloadable security summary to attach to the client’s questionnaire.

Try it before you configure anything

The playground runs the same open coding models. No sign-up, 20 messages a day, and nothing you type is stored.