SaaS Ranking
Menu

EQS Group

eqs.com · Whistleblowing systems · checked 2026-09-03

22/100FBand F

Rank 6 of 10 in Whistleblowing systems, where the median is 24.

We measured 12 of 12 criteria for EQS Group on 2026-09-03. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 22 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

EQS Group

eqs.com · Whistleblowing systems

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

Published commitments2 of 9 found

Measured behaviour2 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 EQS Group has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

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

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://eqs.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://eqs.com/subprocessors – reached, no match (HTTP 404)
  3. https://eqs.com/sub-processors – reached, no match (HTTP 404)
  4. https://eqs.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://eqs.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://eqs.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://eqs.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

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://eqs.com/security – reached, no match (HTTP 200)
  2. https://eqs.com/trust – reached, no match (HTTP 200)
  3. https://eqs.com/legal/privacy – Not the expected content type but "image/png".
  4. https://eqs.com/privacy – Not the expected content type but "image/png".
  5. https://eqs.com/privacy-policy – reached, no match (HTTP 404)
  6. https://eqs.com/compliance – reached, no match (HTTP 200)
  7. https://eqs.com/legal/privacy-policy – 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-03.

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

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-03.

Show the 5 addresses we checked
  1. https://eqs.com/pricing – reached, no match (HTTP 404)
  2. https://eqs.com/pricing/ – reached, no match (HTTP 404)
  3. https://eqs.com/plans – reached, no match (HTTP 404)
  4. https://eqs.com/en/pricing – reached, no match (HTTP 404)
  5. https://eqs.com/pricing-plans – reached, no match (HTTP 404)

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://eqs.com/ – third-party requests before any interaction: 145747460.fs1.hubspotusercontent-eu1.net, cdn1.hubspotusercontent-eu1.net, forms-eu1.hsforms.com, g10498469755.co, js-eu1.hsforms.net, sdk.privacy-center.org, static.hsappstatic.net

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

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

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

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

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

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.eqs.com/security/ · checked 2026-09-03

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://eqs.com/.well-known/security.txt · 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.eqs.com/about-eqs/data-protection/ · checked 2026-09-03

History

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

Compare