SaaS Ranking
Menu

Locus: what they publish

locus.sh · Shipping and logistics · checked 2026-10-16

30/100EBand E

Rank 13 of 83 in Shipping and logistics, where the median is 13.

Public transparency score, not a product or security rating. Latest check: 2026-10-16. 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

3 days since the newest dated result, 3 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

Locus

locus.sh · Shipping and logistics

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

Published commitments4 of 9 found

Measured behaviour0 of 3 found

Checked 2026-10-16. 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 Locus has no such document.

Where Locus sits in Shipping and logistics

  1. A0 0%
  2. B2 2%
  3. C0 0%
  4. D6 7%
  5. E12 14%
  6. F63 76%
83 vendors with a score; 1 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Locus 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 Locus 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

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-16.

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

Across the market: Data processing agreement in Shipping and logistics: 8 of 83 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-16.

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

Across the market: Subprocessor list in Shipping and logistics: 1 of 83 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-16.

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

Across the market: Status page with history in Shipping and logistics: 22 of 84 companies

✗

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-10-16.

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

Across the market: HTTPS enforced with HSTS in Shipping and logistics: 51 of 84 companies

✗weight 2 of 3

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

Checked 1 address on 2026-10-16.

Show the 1 address we checked
  1. https://locus.sh/ – third-party requests before any interaction: 19520031.hs-sites.com, ad.doubleclick.net, ads-api.kwanzoo.com, ads.kwanzoo.com, analytics.twitter.com, api-us11.flostack.io, api.factors.ai, api.hubapi.com, api.ipify.org, app.factors.ai, assets-us11.flostack.io, b2synctagtrackingapi.bamboobox.ai, c.ba.contentsquare.net, cdnjs.cloudflare.com, clearout.io, cta-service-cms2.hubspot.com, 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, i.clarity.ms, 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, k.ba.contentsquare.net, locus.report-uri.com, ml314.com, perf-na1.hsforms.com, px.ads.linkedin.com, region1.analytics.google.com, s3-us-west-2.amazonaws.com, sc.lfeeder.com, scripts.clarity.ms, snap.licdn.com, srm.ba.contentsquare.net, static.ads-twitter.com, stats.g.doubleclick.net, t.co, t.contentsquare.net, tr.capterra.com, tr.lfeeder.com, track.clearout.io, track.hubspot.com, tracking-api.g2.com, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Shipping and logistics: 3 of 82 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-16.

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

Across the market: Notice before subprocessors change in Shipping and logistics: 8 of 83 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-16.

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

Across the market: Uptime SLA with a figure in Shipping and logistics: 1 of 82 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-16.

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

Across the market: security.txt (RFC 9116) in Shipping and logistics: 6 of 81 companies

Evidence

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

Published, with a source 4
✓

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 Economic Area, United States. This does not establish the company’s headquarters.
    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-10-16

Across the market: Data location stated in Shipping and logistics: 13 of 83 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://locus.sh/ · checked 2026-10-16

Across the market: Public pricing in Shipping and logistics: 26 of 83 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 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-10-16

Across the market: Certifications named in Shipping and logistics: 11 of 83 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://locus.sh/privacy-policy/ · checked 2026-10-16

Across the market: Named privacy contact in Shipping and logistics: 23 of 83 companies

History

100 0 2026-10-09: 30 of 1002026-10-16: 30 of 100 2026-10-09 2026-10-16
Score over the last 2 runs we measured Locus in: 30 (2026-10-09), 30 (2026-10-16).

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.

Locus

4 found · 8 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-16.

Investigate 8 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

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

    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. 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
  6. 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
  7. security.txt (RFC 9116)

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

    Inspect this check
  8. 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.