SaaS Ranking
Menu

Security and compliance / Privacy compliance

Didomi

What Didomi publishes on didomi.io, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 61/100 CBand C

Rank 3 of 12 in Privacy compliancecategory median 37checked 2026-09-02

5 gaps found: 5 criteria not found at the addresses we checked. 7 found5 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Didomi

didomi.io · Privacy compliance

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
C 61of 100 Rank 3 of 12

Published commitments6 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-02. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

Show the full transparency label

Transparency labelsaas-ranking.com

Didomi

didomi.io · Privacy compliance

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
C 61of 100 Rank 3 of 12

Published commitments6 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-02. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

Not found, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

Show the 8 addresses we checked
  1. https://didomi.io/legal/dpa – reached, no match (HTTP 404)
  2. https://didomi.io/dpa – reached, no match (HTTP 404)
  3. https://didomi.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://didomi.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://didomi.io/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://didomi.io/legal/gdpr – reached, no match (HTTP 404)
  7. https://didomi.io/trust/dpa – reached, no match (HTTP 404)
  8. https://didomi.io/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-02.

Show the 5 addresses we checked
  1. https://didomi.io/pricing – reached, no match (HTTP 404)
  2. https://didomi.io/pricing/ – reached, no match (HTTP 404)
  3. https://didomi.io/plans – reached, no match (HTTP 404)
  4. https://didomi.io/en/pricing – reached, no match (HTTP 404)
  5. https://didomi.io/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-02.

Show the 1 address we checked
  1. https://didomi.io/ – third-party requests before any interaction: api.privacy-center.org, c.navattic.com, capture.navattic.com, cdn.jsdelivr.net, cdn.prod.website-files.com, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, hubspotonwebflow.com, logo.navattic.com, sdk.privacy-center.org, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-02.

Show the 6 addresses we checked
  1. https://didomi.io/legal/sla – reached, no match (HTTP 404)
  2. https://didomi.io/sla – reached, no match (HTTP 404)
  3. https://didomi.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://didomi.io/trust/sla – reached, no match (HTTP 404)
  5. https://didomi.io/uptime – reached, no match (HTTP 404)
  6. https://didomi.io/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-02.

Show the 1 address we checked
  1. https://didomi.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Published evidence 7
✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.didomi.io/sub-processors · checked 2026-09-02

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.didomi.io/security · checked 2026-09-02

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.didomi.io/ · checked 2026-09-02

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://didomi.io/ · checked 2026-09-02

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.didomi.io/sub-processors · checked 2026-09-02

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.didomi.io/security · checked 2026-09-02

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.didomi.io/privacy-policy · checked 2026-09-02

Keep going