Privacyboard

How to answer a customer's privacy questionnaire without stalling the deal

By the Privacyboard teamPublished 20 November 20269 min read
Short answer

Customers send a privacy questionnaire because the GDPR makes them use only processors that give sufficient guarantees, and the EDPB names questionnaires as one way to check. Answer from your own records (vendors, hosting, security measures, breach process), give evidence where you have it, write "no" or "not yet" when that is the truth, and keep the approved answers for the next one.

A privacy questionnaire is the customer checking that you can be trusted with their data before they sign. Most of the answers already exist somewhere in your company: in your hosting setup, your list of tools, your contracts and your habits. The job is to gather them once, answer honestly, and keep them so the next questionnaire takes an hour instead of a week.

This guide is for small B2B SaaS teams with no lawyer on staff. It explains why the questionnaire arrives, what it usually asks, how to answer it in a day or two, and what to keep. It reflects the texts and guidance as of 20 November 2026. It is general information, not legal advice.

#Why do customers send privacy questionnaires?

When your product stores or handles your customer's personal data (their users, their employees, their contacts), you are usually their processor under the GDPR. Article 28(1) says a controller "shall use only processors providing sufficient guarantees to implement appropriate technical and organisational measures". Your customer is the controller, so the law asks them to check you before they use you.

The European Data Protection Board (EDPB) explained how in Opinion 22/2024, adopted on 7 October 2024. To verify those guarantees, a controller "may choose to draw a questionnaire as a means to gather information from its processor", ask for documentation, rely on public information, certifications or third-party audit reports, or carry out audits (paragraph 41). The same opinion says the check applies "regardless of the risk", that only its depth varies with the risk, and that it is a continuous obligation, repeated at appropriate intervals.

Your side of the deal is in the contract too. Article 28(3)(h) says the processor "makes available to the controller all information necessary to demonstrate compliance" and allows for and contributes to audits. A questionnaire is the lightest form of that audit. Answering it well is part of what your data processing agreement already promises (see our guide to data processing agreements).

There is a commercial side as well: procurement and security teams use the answers to rank vendors. A slow or vague reply delays the deal more often than a plain "not yet".

#What do privacy questionnaires usually ask?

The wording changes from one customer to the next, but the topics repeat. This table maps each one to where the answer lives and the text that makes it matter.

TopicTypical questionWhere your answer comes fromWhy it is asked
Data and purposeWhat personal data do you process for us, and why?Your record of processing (processor side)GDPR Article 28(3), Article 30(2)
Hosting and locationWhere is our data stored? Any transfer outside the EEA?Your hosting provider's region, your vendor listGDPR Chapter V transfers
Sub-processorsWho are your sub-processors? How do you tell us about changes?Your vendor list and your DPAGDPR Article 28(2) and (4)
Security measuresDo you encrypt data at rest and in transit? How do you control access? Do you test your measures?Your security practicesGDPR Article 32(1)
StaffAre staff bound by confidentiality? Are they trained?Employment contracts, onboardingGDPR Article 28(3)(b), Article 32(4)
IncidentsHave you had a breach? How fast will you tell us?Your incident register and breach processGDPR Article 33(2)
Data subject rightsHow will you help us answer access or deletion requests?Your request processGDPR Article 28(3)(e)
End of contractDo you delete or return our data at the end?Your retention and deletion processGDPR Article 28(3)(g)
CertificationsDo you hold ISO/IEC 27001 or a SOC 2 report?Your actual certificates, if anyGDPR Article 28(5), Article 32(3)
AI featuresDo you send our data to AI models? Are they trained on it?Your vendor list and product settingsCustomer policy, the EU AI Act for some uses

Two of these deserve care. On breaches, the GDPR asks the processor to notify the controller "without undue delay after becoming aware" of a personal data breach (Article 33(2)). It sets no hour count for you, so if a customer asks for 24 or 48 hours, that is a contract term to agree, not a legal default. On certifications, Article 28(5) says an approved code of conduct or certification "may be used as an element" to show sufficient guarantees. It helps; it is not required.

#How do you answer one in a day or two?

Take Acme, a 6-person SaaS selling a scheduling tool to HR teams. A prospect sends a 120-row spreadsheet on a Tuesday. Here is a workable routine.

  1. Read the whole file first (20 minutes). Note the deadline, the format (their spreadsheet, a portal, a PDF) and any question that needs someone else, such as a contract term or an insurance certificate.
  2. Collect your sources once (1 to 2 hours the first time). Your list of vendors with their regions, your hosting setup, your security measures (encryption, access control, backups, logging), your breach process, your DPA and your privacy policy. If you keep a record of processing activities, most of it is already there.
  3. Answer the easy 70% first (2 to 3 hours). Hosting, sub-processors, encryption, deletion and rights are facts. Write short, specific answers: "Data is hosted on AWS in eu-west-3 (Paris). Backups stay in the same region." Not: "We use industry-leading security."
  4. Mark what you do not do. "No, we do not hold ISO/IEC 27001. Our measures are described in our security overview." A clear no reads better than a vague yes, and a false yes can come back to you once the answers are attached to the contract.
  5. Attach evidence where it exists (30 minutes). Your DPA, your sub-processor list, a link to your public privacy page, a security overview. The EDPB lists documentation and audit reports among the ways a controller checks a processor.
  6. Have one person read everything before it goes out (30 minutes). Check that the answers agree with your DPA, your privacy policy and your sub-processor list. Customers compare them.
  7. Save the approved answers (10 minutes). Put them in one place with the date. The next questionnaire will ask 80% of the same things.

Day one is the heaviest. With a saved answer set, later questionnaires usually come down to adapting wording and the few new questions.

#What should you never write in a questionnaire?

  • A certification, test or policy you do not have. If you have no penetration test, say so and describe what you do instead.
  • "N/A" for a question that applies. "Do you have a breach process?" is never not applicable to a processor.
  • Promises your contract does not make. "We will notify you within 1 hour" in a questionnaire can be read as a commitment. Keep timings in the DPA, and quote them.
  • Personal or incident details. Say whether you had a reportable breach and what changed, not who was affected.
  • Different answers to the same question. Hosting region, sub-processors and retention must match across the questionnaire, the DPA and your public pages.

#What if you have no SOC 2 or ISO 27001 yet?

Many small SaaS companies do not, and many customers still sign. A SOC 2 report is an auditor's examination of a service organisation's controls relevant to security, availability, processing integrity, confidentiality or privacy, under AICPA criteria. ISO/IEC 27001 is a certifiable standard for an information security management system. Both take months and a budget.

Without them, answer with what you can show: the certifications of your hosting provider (most large cloud providers publish theirs), your own written measures, your sub-processor list, your DPA, and when you plan to start a certification if that is decided. Do not imply that your host's certificate covers your own company.

#What about standard questionnaires like the CAIQ?

Some customers send a standard form instead of their own. The best known for cloud services is the Consensus Assessments Initiative Questionnaire (CAIQ) from the Cloud Security Alliance. When version 4 was announced on 7 June 2021, the CSA described it as 261 questions, down from 310 in the previous version, mapped to its Cloud Controls Matrix. Providers can publish a completed CAIQ in the CSA's STAR registry, which the CSA says can help reduce the number of customer questionnaires to fill in.

For a small team, a full CAIQ is a big job. It can be worth it if your customers keep asking for it. Otherwise, answer their own form and reuse your saved answers.

#How do you make the next questionnaire faster?

Keep one answer set, dated and owned by one person. Update it when a fact changes: a new sub-processor, a new hosting region, a new security measure, a breach. Publish what you can, such as your sub-processor list and your privacy documents, on a public page; a privacy center answers part of the questionnaire before it is sent.

Review the answer set at least once a year. The EDPB treats the customer's check as continuous, so some customers will send the same questionnaire again at renewal.

In Privacyboard, the Customers page (Security questionnaires, Business plan) imports a customer's Excel or PDF questionnaire, suggests answers only from your records and the answers you approved before, and returns their own file once a person has approved each answer (how it works).

#What to do this week

  • Write down your hosting provider and region, and every tool that touches customer data.
  • Check that your public sub-processor list and your DPA name the same vendors.
  • Write one paragraph each on encryption, access control, backups and how you test them.
  • Write your breach process in five lines, including how fast you tell customers.
  • Decide who reads and approves every questionnaire before it goes out.
  • Save the answers of your last questionnaire in one dated file, so the next one starts from them.
  • If you buy tools too, use our vendor due diligence checklist for the other side of the same exercise.

#FAQ

#Is a customer allowed to require a questionnaire?

Yes. The GDPR asks controllers to use only processors that give sufficient guarantees, and Article 28(3)(h) asks processors to make the information available and contribute to audits. The EDPB names questionnaires as one way to verify. The format and the deadline are a matter between you and the customer.

#Do I have to answer every question?

You should answer the questions that relate to how you handle their data. For questions outside that, such as financial statements or insurance, you can say what you share and under which conditions, for example under a non-disclosure agreement.

#Can I send my security overview instead of filling in their file?

Sometimes. Some customers accept a standard document or a completed CAIQ; many procurement teams need their own file filled in to score vendors. Ask, and offer the document as evidence alongside your answers.

#How long should answering take?

The first one often takes one to two days of someone's time, mostly spent gathering facts. With a saved, up-to-date answer set, later ones usually take a few hours.

#Is a questionnaire enough for the customer to meet the GDPR?

Not on its own in every case. The EDPB says the controller may rely on the processor's information but should ask for more or verify it when it seems incomplete or raises questions, and that contract clauses alone do not show that guarantees are implemented.

#Should I mention AI in my answers?

Yes, if your product sends customer data to AI models. Say which provider, where it runs, and whether the data is used for training. Customers increasingly ask, and the answer must match your sub-processor list.

#Sources

Privacyboard is a guidance tool, not legal advice. This article explains general rules in plain language and was accurate on the date above; laws and guidance change. For an unusual situation, ask a qualified professional. Spotted a mistake? Write to hello@privacyboard.io.

Keep reading