A customer sent a 90-question privacy questionnaire: how to answer it truthfully and on time
How a small vendor can answer a customer privacy questionnaire: what the questions are really asking, how to state gaps honestly, and what to build so the next one is faster.
Due in ten days
A 25-person software company is close to signing its largest customer. Procurement sends a spreadsheet: 90 questions about privacy and data protection, due in ten days, with the contract and a data processing agreement attached. Some questions are easy. Others ask for a record of processing activities, a list of sub-processors, retention periods, breach notification timelines and the legal basis for each use of personal data. The company has a privacy policy on its website and a security page. It does not have most of the rest written down.
Two bad answers are common. One is to answer “yes” to everything and hope nobody checks. The other is to stall until the deal goes cold. Questionnaire answers are often attached to the contract or relied on in it, so a wrong “yes” can come back as a breach of contract later. A careful, honest set of answers, with dates for the gaps, usually lands better than either.
What the questions are really asking
Long questionnaires repeat themselves. Most privacy questions fall into a few groups, and many of them trace back to what the law requires the customer to check about its vendors.
| Group | Typical questions | Why the customer asks |
|---|---|---|
| What you process | Categories of personal data, whose data, for what purpose, where it is stored | The customer must describe the processing in its contract with you |
| Who else touches it | Sub-processors, hosting providers, support vendors, countries | Under the GDPR, a processor needs the controller’s written authorization for sub-processors |
| How you protect it | Encryption, access control, staff confidentiality, testing | The customer must choose vendors capable of appropriate safeguards |
| What happens when things go wrong | Breach notification time, incident contacts, cooperation | The customer has its own notification deadlines |
| Individual rights | How you help with access and deletion requests | The customer must answer those requests on time |
| End of contract | Return or deletion of data, and proof of deletion | The customer must get its data back or have it destroyed |
The GDPR makes this concrete. Article 28 says a controller may use only processors that provide sufficient guarantees of appropriate technical and organisational measures, and the contract must cover, among other things, processing only on documented instructions, confidentiality of staff, security measures, conditions for sub-processors, help with data subject requests and breach obligations, deletion or return of data at the end, and the information needed to demonstrate compliance, including audits. If your customer has European data subjects, many of the 90 questions are that list, reworded.
In the United States the same pattern shows up in state law. New York’s SHIELD Act, as the New York Attorney General describes it, lists selecting service providers capable of maintaining appropriate safeguards, and requiring those safeguards by contract, among the reasonable administrative safeguards a business should have. A customer that holds New York residents’ private information is doing what that law expects of it when it asks you these questions.
Seeing the questions this way does two things. It tells you which answers matter most, and it shows that a single set of well-written documents can answer most of them.
A method for the next ten days
Day 1: triage
Read every question once and mark each one:
- Know and can show: you do it and have something to prove it.
- Do but not written down: true in practice, no document.
- Do not do: a real gap.
- Not applicable: and you can explain why.
Ask the customer early about anything ambiguous. A question on day 2 costs less than a wrong answer on day 10.
Days 2 to 4: write the short documents that answer the most questions
Four short documents answer a large share of most privacy questionnaires:
- A data inventory for this service. What personal data the product processes, whose, why, where it is stored, and how long it is kept.
- A sub-processor list. Every vendor that stores or can access customer personal data, what it does and in which country.
- An incident and breach procedure. Who decides, how fast you tell customers, and what the notice contains.
- A data subject request procedure. How you help a customer respond when one of their users asks for access or deletion.
Keep each one to a page or two, dated and owned. These are not paperwork for the questionnaire; they are the documents you will need anyway.
Days 5 to 8: answer, with evidence and honest gaps
For each question:
- Answer the question that was asked, in one or two sentences.
- Point to evidence where you have it: a document name, a screenshot, a setting.
- For a gap, say so and give a plan: “Not currently in place. Planned by March 31, 2027, owner: operations lead.” A dated plan is information the customer can work with; a false “yes” is a liability.
- For “not applicable,” give the reason in one line.
Answer as the company, not as a hopeful salesperson. Have the person who runs the system review the answer about that system.
Days 9 and 10: review the contract alongside the answers
Read the data processing agreement with the answers next to it. The contract terms on breach notice, sub-processor approval, audits and deletion must match what you said. If the contract promises a shorter notification window than your procedure allows, fix one or the other before signing. Have counsel review the agreement; the questionnaire is evidence, but the contract is what binds you.
Make the next questionnaire faster
The second large customer will send a different spreadsheet asking the same things. Build a small answer library:
- Keep your best answer to each common question in one shared document, with the evidence link and the date it was last confirmed.
- Review the library every six months and whenever you add a vendor or change where data is stored.
- Keep a short privacy and security summary you can send before a questionnaire arrives. Some customers accept it in place of part of their form.
Who does what
| Role | Responsibility |
|---|---|
| Owner or executive sponsor | Approves answers that commit the company, signs off on gap plans |
| Operations or IT lead | Writes the system answers, gathers evidence |
| Sales lead | Manages the timeline with the customer, does not write technical answers |
| Counsel | Reviews the data processing agreement against the answers |
When to get help
If the questionnaire is due soon and the four documents above do not exist yet, an outside privacy lead can help write them, answer the questionnaire with you and leave you with a library for the next one.
Want to talk it through? Book a free 30-minute call with Security Medic Consulting.
Sources
- GDPR, Article 28, Processor (accessed 2026-11-05).
- New York State Attorney General, SHIELD Act (accessed 2026-11-05).