SaaS Ranking
Menu

Plausible vs Fathom Analytics

Two privacy-first analytics tools that make the same promise; the details differ.

Plausibleplausible.io

Public transparency

48/100DBand D

Rank 14 of 33 in Web analytics

D

  1. Data processing agreement: found
  2. Subprocessor list: not found
  3. Data location stated: found
  4. Status page with history: not found
  5. Public pricing: not found
  6. Certifications named: not found
  7. Uptime SLA with a figure: not found
  8. HTTPS enforced with HSTS: not found
  9. No third-party tracking before consent: found
  10. security.txt (RFC 9116): not found
  11. Notice before subprocessors change: found
  12. Named privacy contact: found

Checked 2026-10-1412 checks

4point difference5differing criteria

Fathom Analyticsusefathom.com

Public transparency

52/100DBand D

Rank 9 of 33 in Web analytics

D

  1. Data processing agreement: found
  2. Subprocessor list: not found
  3. Data location stated: not found
  4. Status page with history: not found
  5. Public pricing: found
  6. Certifications named: found
  7. Uptime SLA with a figure: not found
  8. HTTPS enforced with HSTS: found
  9. No third-party tracking before consent: found
  10. security.txt (RFC 9116): not found
  11. Notice before subprocessors change: found
  12. Named privacy contact: not found

Checked 2026-10-1512 checks

5 differences out of 12 criteria we could measure for both, last measured 2026-10-15. They match on 7 of the 12 criteria we could measure for both.

No change recorded in these results since 2026-09-11. We compare every new measurement with the one before it; one that finds the same thing is not a change.

Public transparency score, not a product or security rating. This page compares what these two vendors publish, not what their products do.

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.

Plausible

5 found · 7 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-14.

Investigate 7 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. Public pricing

    Please confirm the total cost for our seats and usage, including minimum commitments, add-ons, overages and renewal terms.

    Inspect this check
  4. Certifications named

    Please share the current certificate or audit report and its scope, covered legal entity, products and validity period.

    Inspect this check
  5. 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
  6. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

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

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

    Inspect this check

Fathom Analytics

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-15.

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. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  3. 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
  4. 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
  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. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

Criterion by criterion

CriterionPlausibleFathom Analytics
Data location stated FoundChecked 2026-10-14
Source
  1. https://plausible.io/security
 Not found, 7 addresses checkedChecked 2026-10-15
7 addresses
  1. https://usefathom.com/security – reached, no match (HTTP 200)
  2. https://usefathom.com/trust – reached, no match (HTTP 404)
  3. https://usefathom.com/legal/privacy – reached, no match (HTTP 200)
  4. https://usefathom.com/privacy – reached, no match (HTTP 200)
  5. https://usefathom.com/privacy-policy – reached, no match (HTTP 404)
  6. https://usefathom.com/compliance – reached, no match (HTTP 200)
  7. https://usefathom.com/legal/privacy-policy – reached, no match (HTTP 404)
Public pricing Not found, 5 addresses checkedChecked 2026-10-14
5 addresses
  1. https://plausible.io/pricing – reached, no match (HTTP 404)
  2. https://plausible.io/pricing/ – reached, no match (HTTP 404)
  3. https://plausible.io/plans – reached, no match (HTTP 404)
  4. https://plausible.io/en/pricing – reached, no match (HTTP 404)
  5. https://plausible.io/pricing-plans – reached, no match (HTTP 404)
 FoundChecked 2026-10-15
Source
  1. https://usefathom.com/pricing
HTTPS enforced with HSTS Not found, 2 addresses checkedChecked 2026-10-14
2 addresses
  1. http://plausible.io/ – redirects to https://plausible.io/
  2. https://plausible.io/ – no HSTS header
 FoundChecked 2026-10-15
Source
  1. https://usefathom.com/
Certifications named Not found, 6 addresses checkedChecked 2026-10-14
6 addresses
  1. https://plausible.io/security – reached, no match (HTTP 200)
  2. https://plausible.io/trust – reached, no match (HTTP 404)
  3. https://plausible.io/trust-center – reached, no match (HTTP 404)
  4. https://plausible.io/compliance – reached, no match (HTTP 200)
  5. https://plausible.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.plausible.io/ – The name "trust.plausible.io" could not be resolved.
 FoundChecked 2026-10-15
Source
  1. https://usefathom.com/legal/security
Named privacy contact FoundChecked 2026-10-14
Source
  1. https://plausible.io/privacy
 Not found, 7 addresses checkedChecked 2026-10-15
7 addresses
  1. https://usefathom.com/legal/privacy – reached, no match (HTTP 200)
  2. https://usefathom.com/privacy – reached, no match (HTTP 200)
  3. https://usefathom.com/privacy-policy – reached, no match (HTTP 404)
  4. https://usefathom.com/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://usefathom.com/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://usefathom.com/trust/privacy – reached, no match (HTTP 404)
  7. https://usefathom.com/datenschutz – reached, no match (HTTP 404)
Data processing agreement FoundChecked 2026-10-14
Source
  1. https://plausible.io/dpa
 FoundChecked 2026-10-15
Source
  1. https://usefathom.com/legal/dpa
Subprocessor list Not found, 7 addresses checkedChecked 2026-10-14
7 addresses
  1. https://plausible.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://plausible.io/subprocessors – reached, no match (HTTP 404)
  3. https://plausible.io/sub-processors – reached, no match (HTTP 404)
  4. https://plausible.io/legal/sub-processors – reached, no match (HTTP 404)
  5. https://plausible.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://plausible.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://plausible.io/legal/subprocessor-list – reached, no match (HTTP 404)
 Not found, 7 addresses checkedChecked 2026-10-15
7 addresses
  1. https://usefathom.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://usefathom.com/subprocessors – reached, no match (HTTP 404)
  3. https://usefathom.com/sub-processors – reached, no match (HTTP 404)
  4. https://usefathom.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://usefathom.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://usefathom.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://usefathom.com/legal/subprocessor-list – reached, no match (HTTP 404)
Status page with history Not found, 3 addresses checkedChecked 2026-10-14
3 addresses
  1. https://status.plausible.io/ – reached, no match (HTTP 200)
  2. https://plausible.io/status – reached, no match (HTTP 200)
  3. https://plausible.io.statuspage.io/ – Could not be fetched: fetch failed.
 Not found, 3 addresses checkedChecked 2026-10-15
3 addresses
  1. https://status.usefathom.com/ – reached, no match (HTTP 200)
  2. https://usefathom.com/status – reached, no match (HTTP 200)
  3. https://usefathom.com.statuspage.io/ – Could not be fetched: fetch failed.
No third-party tracking before consent FoundChecked 2026-10-14
Source
  1. https://plausible.io/
 FoundChecked 2026-10-15
Source
  1. https://usefathom.com/
Notice before subprocessors change FoundChecked 2026-10-14
Source
  1. https://plausible.io/dpa
 FoundChecked 2026-10-15
Source
  1. https://usefathom.com/legal/dpa
Uptime SLA with a figure Not found, 6 addresses checkedChecked 2026-10-14
6 addresses
  1. https://plausible.io/legal/sla – reached, no match (HTTP 404)
  2. https://plausible.io/sla – reached, no match (HTTP 404)
  3. https://plausible.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://plausible.io/trust/sla – reached, no match (HTTP 404)
  5. https://plausible.io/uptime – reached, no match (HTTP 404)
  6. https://plausible.io/legal/uptime-sla – reached, no match (HTTP 404)
 Not found, 6 addresses checkedChecked 2026-10-15
6 addresses
  1. https://usefathom.com/legal/sla – reached, no match (HTTP 404)
  2. https://usefathom.com/sla – reached, no match (HTTP 404)
  3. https://usefathom.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://usefathom.com/trust/sla – reached, no match (HTTP 404)
  5. https://usefathom.com/uptime – reached, no match (HTTP 404)
  6. https://usefathom.com/legal/uptime-sla – reached, no match (HTTP 404)
security.txt (RFC 9116) Not found, 1 address checkedChecked 2026-10-14
1 address
  1. https://plausible.io/.well-known/security.txt – reached, no match (HTTP 404)
 Not found, 1 address checkedChecked 2026-10-15
1 address
  1. https://usefathom.com/.well-known/security.txt – reached, no match (HTTP 404)

Differences first, then by weight. A cross is what we found at the addresses we checked on that date, not a statement about what either vendor has.

The full labels

Every criterion with its weight, and the band each vendor lands in.

Transparency labelsaas-ranking.com

Plausible

plausible.io · Web analytics

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

Published commitments4 of 9 found

Measured behaviour1 of 3 found

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

Transparency labelsaas-ranking.com

Fathom Analytics

usefathom.com · Web analytics

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

Published commitments4 of 9 found

Measured behaviour2 of 3 found

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

Take it with you

Both vendors in one file, with every address we checked and every sentence we read, for a procurement file.

Use your current quotes in the SaaS cost calculator to add a cost comparison to this evidence review.

The address carries nothing but the two vendors: no filter, no sort order, nothing about you.

Keep going

The order of the two names is the order of our editorial list. It is not a ranking, and no vendor pays to appear here or to appear first. See how we measure.