SaaS Ranking
Menu

Efficy

efficy.com · CRM · checked 2026-09-03

26/100EBand E

Rank 13 of 20 in CRM, where the median is 37.

We measured 12 of 12 criteria for Efficy on 2026-09-03. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 26 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Efficy

efficy.com · CRM

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

Published commitments2 of 9 found

Measured behaviour1 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 Efficy 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://efficy.com/legal/dpa – blocked or unavailable (HTTP 403)
  2. https://efficy.com/dpa – blocked or unavailable (HTTP 403)
  3. https://efficy.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://efficy.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://efficy.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://efficy.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://efficy.com/trust/dpa – reached, no match (HTTP 404)
  8. https://efficy.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://efficy.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://efficy.com/subprocessors – reached, no match (HTTP 404)
  3. https://efficy.com/sub-processors – reached, no match (HTTP 404)
  4. https://efficy.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://efficy.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://efficy.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://efficy.com/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-03.

Show the 3 addresses we checked
  1. https://status.efficy.com/ – reached, no match (HTTP 200)
  2. https://efficy.com/status – reached, no match (HTTP 404)
  3. https://efficy.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://efficy.com/pricing – reached and rendered, no match
  2. https://efficy.com/pricing/ – blocked or unavailable (HTTP 403)
  3. https://efficy.com/plans – blocked or unavailable (HTTP 403)
  4. https://efficy.com/en/pricing – reached, no match (HTTP 404)
  5. https://efficy.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://efficy.com/ – third-party requests before any interaction: anl.leadoo.com, api.leadinfo.com, bot.leadoo.com, cdn.leadinfo.net, collector.leadinfo.net, collector4.leadinfo.net, consent.cookiebot.com, consentcdn.cookiebot.com, fonts.googleapis.com, fonts.gstatic.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-03.

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

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://efficy.com/security – reached, no match (HTTP 200)
  2. https://efficy.com/trust – reached, no match (HTTP 404)
  3. https://efficy.com/trust-center – reached, no match (HTTP 404)
  4. https://efficy.com/compliance – reached, no match (HTTP 404)
  5. https://efficy.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.efficy.com/ – blocked or unavailable (HTTP 403)

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://efficy.com/legal/sla – reached, no match (HTTP 404)
  2. https://efficy.com/sla – reached, no match (HTTP 404)
  3. https://efficy.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://efficy.com/trust/sla – reached, no match (HTTP 404)
  5. https://efficy.com/uptime – reached, no match (HTTP 404)
  6. https://efficy.com/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-03.

Show the 1 address we checked
  1. https://efficy.com/.well-known/security.txt – 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 3
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.efficy.com/group/security-hub/ · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://efficy.com/ · 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.efficy.com/privacy-policy/ · checked 2026-09-03

History

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

Compare