SaaS Ranking

Navattic

navattic.com · Customer success and onboarding · checked 2026-09-03

57/100CBand C

Rank 3 of 20 in Customer success and onboarding, where the median is 41.

We measured 12 of 12 criteria for Navattic on 2026-09-03. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 57 out of 100, band C.

Overview

Transparency labelsaas-ranking.com

Navattic

navattic.com · Customer success and onboarding

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

Published commitments5 of 9 found

Measured behaviour1 of 3 found

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

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 Navattic has no such document.

Gaps, heaviest first

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://navattic.com/security – reached, no match (HTTP 200)
  2. https://navattic.com/trust – reached, no match (HTTP 404)
  3. https://navattic.com/legal/privacy – reached, no match (HTTP 200)
  4. https://navattic.com/privacy – reached, no match (HTTP 404)
  5. https://navattic.com/privacy-policy – reached, no match (HTTP 404)
  6. https://navattic.com/compliance – reached, no match (HTTP 404)
  7. https://navattic.com/legal/privacy-policy – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-03.

Show the 3 addresses we checked
  1. https://status.navattic.com/ – reached, no match (HTTP 200)
  2. https://navattic.com/status – reached, no match (HTTP 404)
  3. https://navattic.com.statuspage.io/ – Could not be fetched: fetch failed.

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

Show the 1 address we checked
  1. https://navattic.com/ – third-party requests before any interaction: analytics.sayprimer.com, api.vector.co, cdn.dreamdata.cloud, cdn.sanity.io, cdn.vector.co, client-registry.mutinycdn.com, js-na2.hs-scripts.com, js.hs-scripts.com, ob.esnlocco.com, reveal.clearbit.com, sc.lfeeder.com, snap.licdn.com, tag.clearbitscripts.com, tag.unifyintent.com, tracking-api.g2.com, www.googletagmanager.com, x.clearbitjs.com

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://navattic.com/security – reached, no match (HTTP 200)
  2. https://navattic.com/trust – reached, no match (HTTP 404)
  3. https://navattic.com/trust-center – reached, no match (HTTP 404)
  4. https://navattic.com/compliance – reached, no match (HTTP 404)
  5. https://navattic.com/legal/security – reached, no match (HTTP 200)
  6. https://trust.navattic.com/ – reached, no match (HTTP 200)

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

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

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

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

Is this wrong? Send us the URL

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

weight 3 of 3

Published and readable without a login.

Source: https://www.navattic.com/legal/data-processing-agreement · checked 2026-09-03

Subprocessor list

weight 3 of 3

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

Source: https://www.navattic.com/legal/subprocessors · checked 2026-09-03

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.navattic.com/pricing · checked 2026-09-03

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://navattic.com/ · checked 2026-09-03

Notice before subprocessors change

weight 2 of 3

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

Source: https://www.navattic.com/legal/subprocessors · checked 2026-09-03

Named privacy contact

weight 1 of 3

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

Source: https://www.navattic.com/legal/privacy · checked 2026-09-03

History

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

Compare