SaaS Ranking
Menu

Finance and legal / Legal practice management

Amberlo

What Amberlo publishes on amberlo.io, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 43/100 DBand D

Rank 1 of 11 in Legal practice managementcategory median 22checked 2026-09-02

7 gaps found: 7 criteria not found at the addresses we checked. 5 found7 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Amberlo

amberlo.io · Legal practice management

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

Published commitments5 of 9 found

Measured behaviour0 of 3 found

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

Show the full transparency label

Transparency labelsaas-ranking.com

Amberlo

amberlo.io · Legal practice management

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

Published commitments5 of 9 found

Measured behaviour0 of 3 found

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

Not found, heaviest first

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-02.

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

Show the 3 addresses we checked
  1. https://status.amberlo.io/ – reached, no match (HTTP 200)
  2. https://amberlo.io/status – reached, no match (HTTP 404)
  3. https://amberlo.io.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.

Checked 2 addresses on 2026-09-02.

Show the 2 addresses we checked
  1. http://amberlo.io/ – redirects to https://amberlo.io/
  2. https://amberlo.io/ – no HSTS header

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

Show the 1 address we checked
  1. https://amberlo.io/ – third-party requests before any interaction: consent.cookiebot.com, consentcdn.cookiebot.com, js-eu1.hs-scripts.com, pagead2.googlesyndication.com, region1.google-analytics.com, tr.capterra.com, 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-02.

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

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

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

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

Is this wrong? Send us the URL

Published evidence 5
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.amberlo.io/data-processing-agreement/ · checked 2026-09-02

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.amberlo.io/security/ · checked 2026-09-02

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.amberlo.io/pricing/ · checked 2026-09-02

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.amberlo.io/security/ · checked 2026-09-02

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.amberlo.io/privacy-policy/ · checked 2026-09-02

Keep going