/ 9

What's your privacy problem actually costing you?

Answer 9 questions. Get a brutally honest dollar figure.
Takes about 3 minutes.

DSAR handling cost
Data Subject Access Requests — formal requests to access or delete personal data — are a legal obligation. Every one handled manually is hours of developer time you're not recovering.
Sprint capacity lost
See how many sprints per year your team is burning on reactive privacy work — and how many features that displaces.
Breach liability exposure
A risk-adjusted figure for what a reportable incident would cost based on your data types, encryption posture, and customer scale.
Cost of building it in
Model what you'd recover annually by making privacy a product feature instead of a fire to put out.
Currency:
Question 1 of 9

Is your product primarily B2B or B2C?

This drives how many Data Subject Access Requests you're likely fielding — and how expensive each one is to process.

Question 2 of 9

Which privacy jurisdictions apply to your organisation?

Select all that apply. If you operate under multiple frameworks, the calculator will use the most stringent to determine your DSAR obligations and penalty exposure.

Question 3 of 9

How many end-users have personal data in your systems?

A ballpark is fine. This affects your breach exposure and Data Subject Access Request (DSAR) volume.

Question 4 of 9

How would you describe your current dev backlog?

Be honest. Nobody's watching. This affects how quickly your team can respond to privacy issues.

Question 5 of 9

What types of personal data do you store?

Select all that apply. Higher-sensitivity data = higher breach cost multiplier.

Question 6 of 9

What encryption do you have in place?

Select all that apply. Encryption gaps directly increase your breach probability score.

Question 7 of 9

Which privacy processes do you have?

Select all that exist in some shape or form — they don't need to be fully formalised. Gaps here = compliance overhead hours. Leaving this blank is a valid (and expensive) answer.

Question 8 of 9

How many privacy-related issues in the last 12 months?

Bugs, incidents, near-misses, Data Subject Access Request (DSAR) bottlenecks — anything that touched privacy. Round up if unsure.

Zero? Lucky you. Or you're not counting them yet.

25+ incidents/year is a systemic pattern, not bad luck.

Question 9 of 9

Once identified, how long does a privacy issue typically take to resolve?

Not the time to notice it — the time from "we know about this" to "it's fixed."

Annual privacy pipeline cost
Book a free call
Pipeline cost breakdown
Visualisations
Dev capacity lost to privacy
Cost by category
What if you built it in?
Toggle features below to see what you'd recover annually. The chart updates in real time. Individual savings assume each feature is the only one active — combined total accounts for compounding.
Baseline vs optimised annual cost
Total recoverable per year
Let's talk →
Based on IBM Cost of a Data Breach Report (2023), PIPEDA/CPRA frameworks, and industry-standard DSAR benchmarks. These are estimates. Your actual numbers may be worse. How we calculate this → Save your results first to view the methodology. Privacy Notice · About Ross · Terms of Use
© 2026 Ross G Saunders Consulting. All rights reserved.