SaaS Ranking
Menu

Northbeam

northbeam.io · Marketing attribution · checked 2026-09-04

52/100DBand D

Rank 4 of 29 in Marketing attribution, where the median is 30.

We measured 12 of 12 criteria for Northbeam on 2026-09-04. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 52 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

Northbeam

northbeam.io · Marketing attribution

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

Published commitments4 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-04. 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 Northbeam has no such document.

What they state

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

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

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

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

Show the 3 addresses we checked
  1. https://status.northbeam.io/ – No answer within 10 seconds.
  2. https://northbeam.io/status – reached, no match (HTTP 404)
  3. https://northbeam.io.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-04.

Show the 1 address we checked
  1. https://northbeam.io/ – third-party requests before any interaction: ajax.googleapis.com, api.claydar.com, api.hubapi.com, app.revenuehero.io, cdn-cookieyes.com, cdn.claydar.com, cdn.jsdelivr.net, cdn.prod.website-files.com, connect.facebook.net, cta-service-cms2.hubspot.com, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, forms-na1.hsforms.com, forms.hscollectedforms.net, forms.hsforms.com, grsm.io, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.hsforms.net, js.hubspot.com, js.partnerstack.com, log.cookieyes.com, pagead2.googlesyndication.com, partnerlinks.io, perf-na1.hsforms.com, region1.google-analytics.com, sc.lfeeder.com, static.claydar.com, static.hotjar.com, t.vibe.co, tr.lfeeder.com, track.hubspot.com, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://northbeam.io/security – reached, no match (HTTP 404)
  2. https://northbeam.io/trust – reached, no match (HTTP 404)
  3. https://northbeam.io/trust-center – reached, no match (HTTP 404)
  4. https://northbeam.io/compliance – reached, no match (HTTP 404)
  5. https://northbeam.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.northbeam.io/ – The name "trust.northbeam.io" could not be resolved.

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

Show the 6 addresses we checked
  1. https://northbeam.io/legal/sla – reached, no match (HTTP 404)
  2. https://northbeam.io/sla – reached, no match (HTTP 404)
  3. https://northbeam.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://northbeam.io/trust/sla – reached, no match (HTTP 404)
  5. https://northbeam.io/uptime – reached, no match (HTTP 404)
  6. https://northbeam.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-04.

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

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

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

Seen at https://www.northbeam.io/privacy · checked 2026-09-04

Show the 7 addresses we checked
  1. https://northbeam.io/legal/privacy – reached, no match (HTTP 404)
  2. https://northbeam.io/privacy – found, but behind a sign-in
  3. https://northbeam.io/privacy-policy – found, but behind a sign-in
  4. https://northbeam.io/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://northbeam.io/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://northbeam.io/trust/privacy – reached, no match (HTTP 404)
  7. https://northbeam.io/datenschutz – 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 5
✓

Subprocessor list

weight 3 of 3

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

Source: https://www.northbeam.io/subprocessors · checked 2026-09-04

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording European Economic Area, European Union, Switzerland, United Kingdom, United States.
    Show the 5 exact wordings

    ny information, including personal information, on or to the Website, you consent to that transfer, storage, and processing. If you are a resident in the European Economic Area (EEA), United Kingdom (...

    Read at https://www.northbeam.io/privacy

    International Visitors The Website is hosted in the United States. If you choose to use the Website from the European Union or other regions of the world with laws governing data collection and use th...

    Read at https://www.northbeam.io/privacy

    ny information, including personal information, on or to the Website, you consent to that transfer, storage, and processing. If you are a resident in the European Economic Area (EEA), United Kingdom (...

    Read at https://www.northbeam.io/privacy

    ny information, including personal information, on or to the Website, you consent to that transfer, storage, and processing. If you are a resident in the European Economic Area (EEA), United Kingdom (...

    Read at https://www.northbeam.io/privacy

    Our servers are located in the United States.

    Read at https://www.northbeam.io/privacy

Source: https://www.northbeam.io/privacy · checked 2026-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.northbeam.io/pricing · checked 2026-09-04

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000

    Read at https://northbeam.io/

Source: https://northbeam.io/ · checked 2026-09-04

✓

Notice before subprocessors change

weight 2 of 3

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

Source: https://www.northbeam.io/subprocessors · checked 2026-09-04

History

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

Compare