SaaS Ranking

Matomo: what they publish

matomo.org · Web analytics · checked 2026-10-09

52/100DBand D

Rank 11 of 33 in Web analytics, where the median is 39.

Public transparency score, not a product or security rating. Latest check: 2026-10-09. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

7 days since the newest dated result, 7 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Matomo

matomo.org · Web analytics

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
D 52of 100 Rank 11 of 33

Published commitments5 of 9 found

Measured behaviour1 of 3 found

Checked 2026-10-09. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Matomo has no such document.

Where Matomo sits in Web analytics

  1. A0 0%
  2. B3 9%
  3. C5 15%
  4. D7 21%
  5. E11 33%
  6. F7 21%
33 vendors with a score. Bands have fixed thresholds, see how the score works.

The band of Matomo is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Matomo states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Subprocessors: the published list

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://matomo.org/matomo-cloud-dpa/subprocessors/ · checked 2026-10-09

Show the 7 addresses we checked
  1. https://matomo.org/legal/subprocessors – found, but behind a sign-in
  2. https://matomo.org/subprocessors – found, but behind a sign-in
  3. https://matomo.org/sub-processors – reached, no match (HTTP 404)
  4. https://matomo.org/legal/sub-processors – reached, no match (HTTP 404)
  5. https://matomo.org/trust/subprocessors – found, but behind a sign-in
  6. https://matomo.org/privacy/subprocessors – found, but behind a sign-in
  7. https://matomo.org/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Subprocessor list in Web analytics: 6 of 33 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-09.

Show the 3 addresses we checked
  1. https://status.matomo.org/ – The name "status.matomo.org" could not be resolved.
  2. https://matomo.org/status – reached, no match (HTTP 404)
  3. https://matomo.org.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Web analytics: 9 of 33 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

  • Third-party hosts we saw on the first load 2 m-img.org, usercentrics.eu.
    Show the 2 exact wordings

    m-img.org

    Read at https://matomo.org/

    app.usercentrics.eu, consent-api.service.consent.usercentrics.eu, privacy-proxy.usercentrics.eu, uct.service.usercentrics.eu, v1.api.service.cmp.usercentrics.eu, web.cmp.usercentrics.eu

    Read at https://matomo.org/

Checked 1 address on 2026-10-09.

Show the 1 address we checked
  1. https://matomo.org/ – third-party requests before any interaction: app.usercentrics.eu, consent-api.service.consent.usercentrics.eu, m-img.org, privacy-proxy.usercentrics.eu, uct.service.usercentrics.eu, v1.api.service.cmp.usercentrics.eu, web.cmp.usercentrics.eu

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Web analytics: 6 of 33 companies

✗

Notice before subprocessors change

weight 2 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://matomo.org/matomo-cloud-dpa/subprocessors/ · checked 2026-10-09

Show the 8 addresses we checked
  1. https://matomo.org/legal/subprocessors – found, but behind a sign-in
  2. https://matomo.org/subprocessors – found, but behind a sign-in
  3. https://matomo.org/sub-processors – reached, no match (HTTP 404)
  4. https://matomo.org/legal/dpa – reached, no match (HTTP 200)
  5. https://matomo.org/dpa – reached, no match (HTTP 200)
  6. https://matomo.org/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://matomo.org/trust/subprocessors – found, but behind a sign-in
  8. https://matomo.org/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Web analytics: 12 of 33 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-09.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Web analytics: 2 of 33 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-09.

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

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Web analytics: 9 of 33 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 6
✓

Data processing agreement (DPA)

weight 3 of 3

Published and readable without a login.

Source: https://matomo.org/blog/2023/10/dpa-gdpr/ · checked 2026-10-09

Across the market: Data processing agreement in Web analytics: 14 of 33 companies

✓

Data location: where they say data is hosted

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording European Union, France, Germany, United States. This does not establish the company’s headquarters.
    Show the 4 exact wordings

    rvice requested by the user Legitimate interest: website security Worldwide; Visitors are sent to a server closest to their region (traffic from the EU stays in the EU).

    Read at https://matomo.org/privacy-policy/

    ntract (customers, potential customers) Legitimate interest (other data subjects): security Europe, France IP address (stored for 30 days for security reasons), contact information provided via forms,...

    Read at https://matomo.org/privacy-policy/

    by InnoCraft Consent (where required); or Legitimate interest (where permitted): website analytics hosting Germany Matomo Analytics usage data relating to our websites (see section “Usage Data”) Proce...

    Read at https://matomo.org/privacy-policy/

    nar registration and attendance management Consent: for marketing follow-up where required EU (data hosting); USA (support, reporting and analytics) Webinar participant and user data: First name / las...

    Read at https://matomo.org/privacy-policy/

Source: https://matomo.org/privacy-policy/ · checked 2026-10-09

Across the market: Data location stated in Web analytics: 22 of 33 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://matomo.org/pricing/ · checked 2026-10-09

Across the market: Public pricing in Web analytics: 20 of 33 companies

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000;

    Read at https://matomo.org/

Source: https://matomo.org/ · checked 2026-10-09

Across the market: HTTPS enforced with HSTS in Web analytics: 23 of 33 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001.
    Show the exact wording

    Certified ISO 27001:2022 Your analytics data is protected by globally recognised security standards.

    Read at https://matomo.org/security/

Source: https://matomo.org/security/ · checked 2026-10-09

Across the market: Certifications named in Web analytics: 12 of 33 companies

✓

Named privacy contact (DPO or privacy address)

weight 1 of 3

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

Source: https://matomo.org/privacy-policy/ · checked 2026-10-09

Across the market: Named privacy contact in Web analytics: 12 of 33 companies

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Matomo

6 found · 6 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-09.

Investigate 6 open evidence questions
  1. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  2. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  3. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  4. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  5. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  6. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.

Compared with

Each comparison lists only the criteria where the two differ, with the source for every one. All comparisons.