Disclaimer

BreachCostLab publishes calculators, data tables and guides on the cost and economic risk of a data breach for small and mid-sized businesses. Everything on the site is general information for planning and education. It does not take your organisation's facts into account and it is not legal, financial, insurance, tax or compliance advice.

Estimates built on averages, not a forecast of your incident

The breach-cost tools (cost estimator, cost per record, cost by industry and by company size, ransomware cost) start from published industry benchmarks such as the IBM/Ponemon Cost of a Data Breach report and the Verizon DBIR, with the formula shown on each page. Those benchmarks are averages across many organisations and countries. The coefficients that adapt them to size, data type and security posture are documented modelling choices, not measured facts about your business. A result is a planning range, not a prediction of what a specific incident will cost.

Penalty figures are ceilings, not likely fines

The GDPR fine estimator applies the Article 83 caps (EUR 10 million or 2% of worldwide turnover, EUR 20 million or 4%): the actual amount, if any, is set by a supervisory authority weighing the factors of Article 83(2). The HIPAA estimator uses the civil money penalty tiers published by HHS OCR, which are adjusted for inflation; the CCPA/CPRA calculator uses the statutory damages range of Cal. Civ. Code §1798.150, which a court applies case by case. PCI DSS non-compliance fees are set by card brands and acquiring banks under private contracts, so the site can only show widely reported ranges, not published thresholds. Breach-notification costs depend on the state, country and sector rules that apply to you.

Risk, ROI and insurance tools

Annual Loss Expectancy, breach probability, downtime, detection delay and security-control ROI are standard risk formulas fed by your inputs and by indicative sector rates. They are only as good as the figures you enter. The cyber insurance calculator compares expected costs; it is not a quote, and only the policy wording decides what is covered. The ransomware calculator shows costs with and without paying: it is not a recommendation to pay or not to pay, which is a decision for you, your counsel and law enforcement.

Whom to ask instead

  • For notification duties, penalties and regulator contacts: a data-protection or privacy lawyer, and the guidance of the competent authority.
  • For an incident in progress: a professional incident-response provider and, where appropriate, law enforcement.
  • For PCI DSS: your acquiring bank and a Qualified Security Assessor (QSA).
  • For cover and premiums: a licensed insurance broker or the insurer.

Sources and dates

Benchmarks are refreshed roughly once a year and statutory amounts change. Each tool and table shows the date its figures were checked, and every source is listed on the Sources page; the formulas are explained in the Methodology. Every key figure is an editable input: confirm the current value with the primary source before relying on a result.

Your inputs

The calculators run in your browser: the figures you type are not sent to our server and are not stored. Wrong or incomplete inputs give wrong results.

Use of artificial intelligence

The texts are drafted and updated by an artificial intelligence agent and published without systematic human review; the calculators are deterministic code checked by automated tests. Details on the AI transparency page.

Advertising and third-party sites

The site currently shows no advertising and contains no affiliate or sponsored links. Links to reports, statutes and regulators are there as sources; we do not control those sites and are not responsible for their content.

Liability

To the extent permitted by law, Redbit S.r.l.s. is not liable for decisions made on the basis of this site without the checks described above. This does not limit liability for wilful misconduct or gross negligence, nor the rights that the law grants to consumers. The full conditions are in the Terms; publisher details are in the Legal notice.

Report an error

If you find a wrong or outdated figure, write to [email protected] naming the page: the figure is checked against its source and corrected on the page.

Last updated: 17 November 2026.