Choosing a privacy platform without regret: the build-versus-buy question
Privacy software is sold on its feature list. Regret comes from the things the feature list does not say: whether it connects to your systems, who will run it, and whether the process it automates was a good one to automate.
Key points
- A privacy platform is software that carries parts of a privacy programme, such as data mapping, handling of requests from individuals, consent management and assessments, in one place.
- You are ready for a platform when the process works by hand and fails on volume or evidence tracking, not when nobody has decided who owns it.
- Building makes sense when your needs are narrow, your systems are few or unusual, and you have engineers who will maintain it for years; buying makes sense when the need is broad and the upkeep of connectors, forms and legal changes would otherwise fall on you.
- Test each shortlisted platform on your own systems and a real request, because a demonstration shows what a product can do, not whether it connects to your systems.
We sell, resell and host no platform, and nothing we earn depends on which you choose. This article makes no claim about any product’s features, price or customers.
Are you ready?
You are ready for a platform when the process works by hand and fails on volume or evidence tracking, not when nobody has decided who owns it.
Software automates a process, so a broken process is automated broken. Signs the process is ready: requests are handled by hand but take too long as volume grows; the data map exists but updating it is a chore; consent changes happen weekly and nobody can say what is live. Signs it is not: nobody owns privacy, requests arrive in four inboxes, and the record of processing has not been started. In that case the first investment is the process, in the order described in what a fractional DPO does in the first 90 days.
Build, buy or stay manual
Building makes sense when your needs are narrow, your systems are few or unusual, and you have engineers who will maintain it for years; buying makes sense when the need is broad and the upkeep of connectors, forms and legal changes would otherwise fall on you. A third answer is often right for a while: a well-run spreadsheet, a shared mailbox and a calendar. It is cheap, it is understood, and it is a sound basis for writing requirements.
Hidden costs run in both directions. A built tool needs an owner when its author leaves, and connector upkeep never ends. A bought tool needs configuration, training and a named administrator, and a contract term that outlives the project that justified it.
Write requirements before you meet a vendor
Requirements come from your own process and systems. Write them before any vendor is contacted, so the shortlist is judged against what you need, not what a demonstration happens to show. Useful headings are:
- Systems to connect. The databases, SaaS tools and files that hold personal data, from the data map.
- Laws and regions. Which regimes apply and whose text the tool must follow. Where the GDPR applies, the text is on EUR-Lex, and your counsel confirms what the tool must do about it.
- Request volume and type. A few a month, or many a week; access only, or deletion and opt-out too.
- Consent behaviour. What the site must do before a choice, after a rejection and on an opt-out signal. See testing what your consent banner really does.
- Who runs it. A named internal owner, and what they can administer without the vendor.
- Exit. How you export your records, configuration and logs if you leave.
- Security and data location. The tool holds personal data, so it is itself a vendor to review, covered in vendor privacy reviews that scale.
A shortlist, fairly built
Platforms such as OneTrust, DataGrail and Transcend are examples of the category buyers compare; naming them is not a recommendation or a partnership, and every shortlist is built from your own requirements.
A fair process has four properties. The same requirements go to each vendor. The same scenarios are scripted for each demonstration, taken from your own work: a request that needs a search across three systems, a consent rule that differs by region. Claims about connectors, regions and coverage are answered in writing, not on a call. And references are taken from customers of your size and shape, whom you reach yourself.
Score against the requirements with weights set before the demonstrations start. Record the reasoning, including for the vendors you drop.
Test on your own systems
Test each shortlisted platform on your own systems and a real request, because a demonstration shows what a product can do, not whether it connects to your systems. A proof of concept with real systems and a real, or realistic, request answers the question that matters: how many of your systems the tool actually reaches, and what a person has to do by hand after it has done its part.
After the contract
Most regret appears after signature. Plan for configuration, a named administrator, a review of the tool’s own settings, training for the people who handle requests, and a date to check that the tool is used as designed. Keep the manual process documented until the tool has been through a real cycle. Privacy tools often sit beside a governance, risk and compliance platform, and the selections are best coordinated: see choosing a GRC platform. The service is privacy tool selection and implementation.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What is a privacy platform?
A privacy platform is software that carries parts of a privacy programme, such as data mapping, handling of requests from individuals, consent management and assessments, in one place.
When are we ready for one?
You are ready for a platform when the process works by hand and fails on volume or evidence tracking, not when nobody has decided who owns it.
Should we build or buy?
Building makes sense when your needs are narrow, your systems are few or unusual, and you have engineers who will maintain it for years; buying makes sense when the need is broad and the upkeep of connectors, forms and legal changes would otherwise fall on you.
Which platforms should we look at?
Platforms such as OneTrust, DataGrail and Transcend are examples of the category buyers compare; naming them is not a recommendation or a partnership, and every shortlist is built from your own requirements.
How should we test a shortlist?
Test each shortlisted platform on your own systems and a real request, because a demonstration shows what a product can do, not whether it connects to your systems.
Check readiness first
Describe the process you run today and what is failing. The reply says whether a platform is the next step. The service is privacy tool selection and implementation; request handling is in data subject requests across jurisdictions.