SaaS Ranking
Menu

Endorsal

endorsal.io · Customer reviews and testimonials · checked 2026-09-03

13/100FBand F

Rank 8 of 14 in Customer reviews and testimonials, where the median is 13.

We measured 12 of 12 criteria for Endorsal on 2026-09-03. We found 2 with a source and did not find 10 at the addresses we checked. That is a transparency score of 13 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Endorsal

endorsal.io · Customer reviews and testimonials

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

Published commitments2 of 9 found

Measured behaviour0 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 Endorsal 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://endorsal.io/legal/dpa – reached, no match (HTTP 404)
  2. https://endorsal.io/dpa – reached, no match (HTTP 404)
  3. https://endorsal.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://endorsal.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://endorsal.io/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://endorsal.io/legal/gdpr – reached, no match (HTTP 404)
  7. https://endorsal.io/trust/dpa – reached, no match (HTTP 404)
  8. https://endorsal.io/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://endorsal.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://endorsal.io/subprocessors – reached, no match (HTTP 404)
  3. https://endorsal.io/sub-processors – reached, no match (HTTP 404)
  4. https://endorsal.io/legal/sub-processors – reached, no match (HTTP 404)
  5. https://endorsal.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://endorsal.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://endorsal.io/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://endorsal.io/security – reached, no match (HTTP 404)
  2. https://endorsal.io/trust – reached, no match (HTTP 404)
  3. https://endorsal.io/legal/privacy – reached, no match (HTTP 404)
  4. https://endorsal.io/privacy – reached, no match (HTTP 200)
  5. https://endorsal.io/privacy-policy – reached, no match (HTTP 404)
  6. https://endorsal.io/compliance – reached, no match (HTTP 404)
  7. https://endorsal.io/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.endorsal.io/ – The name "status.endorsal.io" could not be resolved.
  2. https://endorsal.io/status – reached, no match (HTTP 404)
  3. https://endorsal.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-03.

Show the 2 addresses we checked
  1. http://endorsal.io/ – redirects to https://endorsal.io/
  2. https://endorsal.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-03.

Show the 1 address we checked
  1. https://endorsal.io/ – third-party requests before any interaction: a.quora.com, ad.doubleclick.net, analytics.twitter.com, app.ewebinar.com, cdn.buttercms.com, cdn.firstpromoter.com, cdn.loom.com, code.jquery.com, connect.facebook.net, d2oeplw15jeq9j.cloudfront.net, d2umh4u76e9b4y.cloudfront.net, d3gciqzneb4vr5.cloudfront.net, dxnrs23s9bsky.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, px.ads.linkedin.com, q.quora.com, region1.analytics.google.com, res.cloudinary.com, snap.licdn.com, static.ads-twitter.com, stats.g.doubleclick.net, t.co, www.facebook.com, www.google-analytics.com, www.google.com, www.google.de, www.googleoptimize.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://endorsal.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://endorsal.io/subprocessors – reached, no match (HTTP 404)
  3. https://endorsal.io/sub-processors – reached, no match (HTTP 404)
  4. https://endorsal.io/legal/dpa – reached, no match (HTTP 404)
  5. https://endorsal.io/dpa – reached, no match (HTTP 404)
  6. https://endorsal.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://endorsal.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://endorsal.io/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://endorsal.io/security – reached, no match (HTTP 404)
  2. https://endorsal.io/trust – reached, no match (HTTP 404)
  3. https://endorsal.io/trust-center – reached, no match (HTTP 404)
  4. https://endorsal.io/compliance – reached, no match (HTTP 404)
  5. https://endorsal.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.endorsal.io/ – The name "trust.endorsal.io" could not be resolved.

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

Show the 1 address we checked
  1. https://endorsal.io/.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 2
✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://endorsal.io/pricing · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

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

Source: https://endorsal.io/privacy · checked 2026-09-03

History

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

Compare