SaaS Ranking
Menu

Locus

locus.sh · Shipping and logistics · checked 2026-09-04

30/100EBand E

Rank 10 of 30 in Shipping and logistics, where the median is 22.

We measured 12 of 12 criteria for Locus on 2026-09-04. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 30 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Locus

locus.sh · Shipping and logistics

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

Published commitments4 of 9 found

Measured behaviour0 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.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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 Locus 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://locus.sh/legal/dpa – reached, no match (HTTP 200)
  2. https://locus.sh/dpa – reached, no match (HTTP 200)
  3. https://locus.sh/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://locus.sh/data-processing-agreement – reached, no match (HTTP 200)
  5. https://locus.sh/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://locus.sh/legal/gdpr – reached, no match (HTTP 200)
  7. https://locus.sh/trust/dpa – reached, no match (HTTP 200)
  8. https://locus.sh/privacy/dpa – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://locus.sh/legal/subprocessors – reached, no match (HTTP 200)
  2. https://locus.sh/subprocessors – reached, no match (HTTP 200)
  3. https://locus.sh/sub-processors – reached, no match (HTTP 200)
  4. https://locus.sh/legal/sub-processors – reached, no match (HTTP 200)
  5. https://locus.sh/trust/subprocessors – reached, no match (HTTP 200)
  6. https://locus.sh/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://locus.sh/legal/subprocessor-list – 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-04.

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

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

  • HSTS max-age 300 seconds.
    Show the exact wording

    max-age=300; includeSubdomains; preload

    Read at https://locus.sh/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=300; includeSubdomains; preload

    Read at https://locus.sh/

    max-age=300; includeSubdomains; preload

    Read at https://locus.sh/

Checked 2 addresses on 2026-09-04.

Show the 2 addresses we checked
  1. http://locus.sh/ – redirects to https://locus.sh/
  2. https://locus.sh/ – HSTS max-age=300

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://locus.sh/ – third-party requests before any interaction: ad.doubleclick.net, ads-api.kwanzoo.com, ads.kwanzoo.com, analytics.twitter.com, api.factors.ai, api.hubapi.com, api.ipify.org, app.factors.ai, b2synctagtrackingapi.bamboobox.ai, c.ba.contentsquare.net, cdnjs.cloudflare.com, clearout.io, d.bablic.com, fonts.googleapis.com, fonts.gstatic.com, forms-na1.hsforms.com, forms.hscollectedforms.net, forms.hsforms.com, g1584674684.co, hpshortner-559903420586.us-central1.run.app, js-na1.hs-scripts.com, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hscollectedforms.net, js.hsforms.net, js.hubspot.com, locus.report-uri.com, ml314.com, px.ads.linkedin.com, region1.analytics.google.com, s3-us-west-2.amazonaws.com, sc.lfeeder.com, scripts.clarity.ms, snap.licdn.com, static.ads-twitter.com, stats.g.doubleclick.net, t.co, t.contentsquare.net, tr.capterra.com, tr.lfeeder.com, tracking-api.g2.com, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://locus.sh/legal/subprocessors – reached, no match (HTTP 200)
  2. https://locus.sh/subprocessors – reached, no match (HTTP 200)
  3. https://locus.sh/sub-processors – reached, no match (HTTP 200)
  4. https://locus.sh/legal/dpa – reached, no match (HTTP 200)
  5. https://locus.sh/dpa – reached, no match (HTTP 200)
  6. https://locus.sh/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://locus.sh/trust/subprocessors – reached, no match (HTTP 200)
  8. https://locus.sh/legal/sub-processors – 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-04.

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

Show the 1 address we checked
  1. https://locus.sh/.well-known/security.txt – reached, no match (HTTP 200)

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 4
✓

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, United States.
    Show the 2 exact wordings

    For example, we transfer your PHI or personal data to the United States and EEA, where our servers are located.

    Read at https://locus.sh/privacy-policy/

    For example, we transfer your PHI or personal data to the United States and EEA, where our servers are located.

    Read at https://locus.sh/privacy-policy/

Source: https://locus.sh/privacy-policy/ · checked 2026-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://locus.sh/ · checked 2026-09-04

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA, ISO/IEC 27001, ISO/IEC 27701, SOC 2 Type II.
    Show the 4 exact wordings

    HIPAA Compliant Locus is fully compliant with the Health Insurance Portability and Accountability Act (HI

    Read at https://locus.sh/trust/

    C754492 ISO 27001:2022 Locus is certified for ISO 27001:2022, demonstrating a robust Information Security Management

    Read at https://locus.sh/trust/

    C754493 ISO 27701:2019 Locus is ISO 27701:2019 certified, helping us to demonstrate our capability to protect custome

    Read at https://locus.sh/trust/

    SOC 2 Type II Locus is SOC 2 Type II compliant, helping us to provide assurance to customers and stakehol

    Read at https://locus.sh/trust/

Source: https://locus.sh/trust/ · checked 2026-09-04

✓

Named privacy contact

weight 1 of 3

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

Source: https://locus.sh/privacy-policy/ · checked 2026-09-04

History

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

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.