Privacy software checklist for buyers

This privacy software checklist scores one vendor across seven sections and lists the must-have items the vendor has not yet shown you. Tick a box only when the vendor has shown the feature working or has committed to it in the contract.

Opsware designs and implements data pipelines, integrations and deletion jobs as part of its engineering services.

The checklist covers data privacy management tools for data discovery and mapping, data subject requests (DSRs), consent and cookie management, and suites that combine them. The full buying process is described in How to evaluate and choose privacy management software, which covers build or buy, scripted demos, the proof of concept and total cost. Nothing you tick leaves your browser.

How the scoring works

  • Each section shows how many of its items you ticked.
  • The overall score is the percentage of ticked items across all sections, except sections you mark "Not relevant to us".
  • Items marked Must-have are the ones you should not buy without. The overall score box lists every unticked must-have, whatever the percentage.
  • Score one vendor at a time. Print the page or save it as a PDF, then click "Clear all" and score the next vendor.
The score updates as you tick. Sections marked "Not relevant to us" are left out.
Tick items below to start scoring.

1. Data discovery and mapping

"Discovery" can mean scanning column names, or it can mean reading the values inside files and classifying them. Ask the vendor which one the product does. Data mapping and discovery and Record of processing activities (ROPA): fields and template describe what a usable map contains.

0 of 7 ticked
Questions to ask in the demo
  • Connect to one of our real systems, or a copy, during the trial. How long does the first scan take, and what does it miss?
  • Show us a false positive and correct it in front of us.
  • Does classification run inside our environment, or do you send sampled values to your cloud? Which fields do you send?
  • What happens to the map when we rename a table or add a new SaaS app?
  • Export the ROPA now. Which fields come out empty and need a person to fill them in?

2. Data subject request automation

A DSR tool takes in a request, verifies the person, finds their data across systems, acts on it, and records what it did. GDPR gives one month to respond, extendable by two further months (Art. 12(3)). The CCPA gives 45 calendar days, extendable once by 45 more (Civil Code §1798.130). Many products automate intake and routing well and leave the search and deletion to people. DSAR automation: building the data subject request workflow and DSAR software: how privacy request automation tools work describe the steps.

0 of 8 ticked
Questions to ask in the demo
  • Submit a deletion request as a test user and follow it to the end. Which steps ran automatically, and which needed a person?
  • What happens when an API call to a connected system fails halfway through a deletion?
  • How do you match a requester to records when the email address differs between systems?
  • How do you handle a burst of requests from an agent service that arrive without individual verification?
  • Show the audit log for a closed request. Could we give it to a regulator unchanged?

A consent tool runs on your website and apps, so it affects page speed, which tags fire, and what marketing can measure. From 2024 to 2026, more US states started to require sites to honor opt-out signals such as Global Privacy Control. Website privacy audit: score your own site lists those states and their dates.

0 of 8 ticked
Questions to ask in the demo
  • Turn on GPC in a browser and load our staging site with your banner. What changes, and where is the opt-out logged?
  • What does the page do before your script finishes loading? Does any tag fire in that time?
  • How do consent choices reach our ad platforms and customer data platform? Is the sync real-time or batched?
  • Who assigns a category to a new tracker when one appears?
  • When IAB Europe publishes a new TCF version, who updates our banner, and by when?

4. Security and hosting

A privacy tool that indexes your personal data often holds a copy of your most sensitive fields. Ask for the same security evidence you would ask of any vendor that holds sensitive data, and read the data processing agreement alongside this section. See Data processing agreement (DPA): what it must contain and GDPR Article 32 and security controls for personal data.

0 of 8 ticked
Questions to ask in the demo
  • For each feature we would use, what personal data do you store, where, and for how long?
  • Who holds the encryption keys? If we revoke a customer-managed key, what stops working?
  • Can we have the full SOC 2 Type 2 report under NDA, instead of a bridge letter (a letter the vendor writes about the months since the audit period ended) or a logo on its trust page? What exceptions did the auditor find?
  • Which of your engineers can access our account, who approves that access, and can we see the log?
  • Which sub-processors process our data, and in which countries?

5. Integration effort

A vendor's connector list does not say what each connector can do. A connector may only read metadata, may need admin credentials you will not grant, or may need regular upkeep from your engineers. Ask to see the connector settings for your own systems.

0 of 6 ticked
Questions to ask in the demo
  • For our five most important systems, show the connector settings screen and the permissions each connector asks for.
  • Which integrations break most often after an upstream API change, and who fixes them?
  • What does a typical implementation look like week by week, and what usually causes delays?
  • Is implementation included, a fixed fee, or billed by the hour?

6. Pricing and total cost

Consent vendors that publish prices charge by different units: sessions, subpages, unique users, visitors or pageviews. Enterprise suites often do not publish prices, so ask what each quote counts. Two quotes with the same price today can cost very different amounts after your traffic or system count doubles. Data map cost estimate calculates what a data map costs when people build it by hand.

0 of 6 ticked
Questions to ask in the demo
  • What exactly do you count for billing, and who measures it?
  • Price the same scope for year three, assuming we double our data sources.
  • Which features in today's demo are add-ons?
  • What renewal cap will you put in the order form?

7. Exit and data export

Privacy vendors get acquired, merge products and shut down. For example, the backup company Veeam bought the privacy platform Securiti in December 2025, and the consent vendor Didomi bought its competitor Sourcepoint in July 2025. Your ROPA, consent records and DSR audit log are compliance records you must keep after the contract ends.

0 of 5 ticked
Questions to ask in the demo
  • Export everything from the trial account now. How long did the export take, and can we use it without your product?
  • After termination, how many days do we have to retrieve data, and how do you confirm deletion?
  • Has a customer switched from your product to another one? What did they take with them?

Overall result

Tick items above to start scoring.

Reading the score to compare privacy management tools

Use the percentage to compare vendors you tested the same way, not as a pass mark. Check the must-haves first, because a vendor at 70% with every must-have ticked is usually a safer choice than a vendor at 85% with one must-have missing.

ResultWhat it usually means
All must-haves ticked, 75% or more overallThe vendor meets your needs. Write the remaining gaps into the contract or the implementation plan.
All must-haves ticked, under 75%The vendor meets your minimum needs. Check whether you will need the unticked items in the next one or two years.
One or more must-haves missingAsk the vendor to commit in writing to a date for each missing must-have, or evaluate other vendors. A roadmap promise in a demo is not a commitment.

If several vendors score about the same, compare integration effort on your own systems, which only a proof of concept on real or realistic data shows. How to evaluate and choose privacy management software explains how to run one. The privacy tech stack: privacy technology by layer shows where each kind of tool fits and names example vendors.

Frequently asked questions

Can I add my own items?

Not on this page. Print it or save it as a PDF, and add your own must-haves by hand. Write them as tests the vendor must show, for example "deletes a test contact in our CRM sandbox".

Why does a section have a "Not relevant to us" box?

Data privacy management solutions range from consent-only tools to full suites. A consent-only tool has no discovery features, and a discovery tool has no banner. Marking a section not relevant removes it from the overall score, so a point tool is not scored on features it was never meant to have.

Does a SOC 2 report or ISO certificate prove the tool is compliant with privacy law?

No. A SOC 2 report and an ISO certificate cover the vendor's security controls but do not say that the tool meets GDPR or the CCPA. You still need a data processing agreement and your own review of how the tool processes data.

Is my data saved?

No. The scoring runs in your browser, and the page sends and stores nothing.

Need this built?

If no vendor covers your systems, we can build the missing connectors or the whole workflow. Tell us about your project and we will reply with questions or a rough plan.

Privacy engineering notes by email

When we publish a new guide on data mapping, DSR automation or AI privacy, we send it to this list. Nothing else.