Sales and marketing / Sales engagement
Reply
What Reply publishes on reply.io, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.
Transparency 35/100 EBand E
Rank 8 of 12 in Sales engagementcategory median 45.5checked 2026-09-02
9 gaps found: 9 criteria not found at the addresses we checked. 3 found9 not found0 not measured
Public transparency score, not a product or security rating.
Transparency labelsaas-ranking.com
Reply
- A
- B
- C
- D
- E
- F
Published commitments3 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour0 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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
Reply
- A
- B
- C
- D
- E
- F
Published commitments3 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour0 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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 3No subprocessor list found.
Checked 7 addresses on 2026-09-02.
Show the 7 addresses we checked
https://reply.io/legal/subprocessors– reached, no match (HTTP 404)https://reply.io/subprocessors– reached, no match (HTTP 404)https://reply.io/sub-processors– reached, no match (HTTP 404)https://reply.io/legal/sub-processors– reached, no match (HTTP 404)https://reply.io/trust/subprocessors– reached, no match (HTTP 404)https://reply.io/privacy/subprocessors– reached, no match (HTTP 404)https://reply.io/legal/subprocessor-list– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-02.
Show the 3 addresses we checked
https://status.reply.io/– blocked or unavailable (HTTP 403)https://reply.io/status– reached, no match (HTTP 404)https://reply.io.statuspage.io/– Could not be fetched: fetch failed.
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-02.
Show the 2 addresses we checked
http://reply.io/– redirects to https://reply.io/https://reply.io/– no HSTS header
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-02.
Show the 1 address we checked
https://reply.io/– third-party requests before any interaction: code.jquery.com, static.cloudflareinsights.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-02.
Show the 8 addresses we checked
https://reply.io/legal/subprocessors– reached, no match (HTTP 404)https://reply.io/subprocessors– reached, no match (HTTP 404)https://reply.io/sub-processors– reached, no match (HTTP 404)https://reply.io/legal/dpa– reached, no match (HTTP 404)https://reply.io/dpa– reached, no match (HTTP 404)https://reply.io/legal/data-processing-agreement– reached, no match (HTTP 404)https://reply.io/trust/subprocessors– reached, no match (HTTP 404)https://reply.io/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-02.
Show the 6 addresses we checked
https://reply.io/security– reached, no match (HTTP 404)https://reply.io/trust– reached, no match (HTTP 404)https://reply.io/trust-center– reached, no match (HTTP 404)https://reply.io/compliance– reached, no match (HTTP 404)https://reply.io/legal/security– reached, no match (HTTP 404)https://trust.reply.io/– The name "trust.reply.io" could not be resolved.
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-02.
Show the 6 addresses we checked
https://reply.io/legal/sla– reached, no match (HTTP 404)https://reply.io/sla– reached, no match (HTTP 404)https://reply.io/legal/service-level-agreement– reached, no match (HTTP 404)https://reply.io/trust/sla– reached, no match (HTTP 404)https://reply.io/uptime– reached, no match (HTTP 404)https://reply.io/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-02.
Show the 1 address we checked
https://reply.io/.well-known/security.txt– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-02.
Show the 7 addresses we checked
https://reply.io/legal/privacy– reached, no match (HTTP 404)https://reply.io/privacy– reached, no match (HTTP 404)https://reply.io/privacy-policy– reached, no match (HTTP 200)https://reply.io/legal/privacy-policy– reached, no match (HTTP 404)https://reply.io/legal/privacy-notice– reached, no match (HTTP 404)https://reply.io/trust/privacy– reached, no match (HTTP 404)https://reply.io/datenschutz– reached, no match (HTTP 404)
Published evidence 3
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://reply.io/data-processing-agreement/ · checked 2026-09-02
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://reply.io/privacy-policy/ · checked 2026-09-02
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://reply.io/pricing/ · checked 2026-09-02