Genesys
genesys.com · Contact centre · checked 2026-09-03
Rank 5 of 16 in Contact centre, where the median is 13.5.
- 4 found
- 8 not found
- 0 not measured
We measured 12 of 12 criteria for Genesys 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 26 out of 100, band E.
Overview
Transparency labelsaas-ranking.com
Genesys
- A
- B
- C
- D
- E
- F
Published commitments3 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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 Genesys has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://genesys.com/legal/dpa– reached, no match (HTTP 404)https://genesys.com/dpa– reached, no match (HTTP 404)https://genesys.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://genesys.com/data-processing-agreement– reached, no match (HTTP 404)https://genesys.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://genesys.com/legal/gdpr– reached, no match (HTTP 404)https://genesys.com/trust/dpa– reached, no match (HTTP 404)https://genesys.com/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://genesys.com/legal/subprocessors– reached, no match (HTTP 404)https://genesys.com/subprocessors– reached, no match (HTTP 404)https://genesys.com/sub-processors– reached, no match (HTTP 404)https://genesys.com/legal/sub-processors– reached, no match (HTTP 404)https://genesys.com/trust/subprocessors– reached, no match (HTTP 404)https://genesys.com/privacy/subprocessors– reached, no match (HTTP 404)https://genesys.com/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3We found this behind a sign-in, so it is not published openly.
Seen at https://www.genesys.com/company/legal/privacy-policy · checked 2026-09-03
Show the 7 addresses we checked
https://genesys.com/security– reached, no match (HTTP 200)https://genesys.com/trust– reached, no match (HTTP 404)https://genesys.com/legal/privacy– reached, no match (HTTP 404)https://genesys.com/privacy– reached, no match (HTTP 200)https://genesys.com/privacy-policy– found, but behind a sign-inhttps://genesys.com/compliance– reached, no match (HTTP 404)https://genesys.com/legal/privacy-policy– found, but behind a sign-in
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-03.
Show the 3 addresses we checked
https://status.genesys.com/– The name "status.genesys.com" could not be resolved.https://genesys.com/status– reached, no match (HTTP 404)https://genesys.com.statuspage.io/– Could not be fetched: fetch failed.
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://genesys.com/– third-party requests before any interaction: 117374425.intellimizeio.com, api.intellimize.co, cdn.intellimize.co, cdn.jsdelivr.net, log.intellimize.co
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://genesys.com/legal/subprocessors– reached, no match (HTTP 404)https://genesys.com/subprocessors– reached, no match (HTTP 404)https://genesys.com/sub-processors– reached, no match (HTTP 404)https://genesys.com/legal/dpa– reached, no match (HTTP 404)https://genesys.com/dpa– reached, no match (HTTP 404)https://genesys.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://genesys.com/trust/subprocessors– reached, no match (HTTP 404)https://genesys.com/legal/sub-processors– reached, no match (HTTP 404)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://genesys.com/legal/sla– reached, no match (HTTP 404)https://genesys.com/sla– reached, no match (HTTP 404)https://genesys.com/legal/service-level-agreement– reached, no match (HTTP 404)https://genesys.com/trust/sla– reached, no match (HTTP 404)https://genesys.com/uptime– reached, no match (HTTP 404)https://genesys.com/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-03.
Show the 1 address we checked
https://genesys.com/.well-known/security.txt– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 4
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.genesys.com/pricing · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://genesys.com/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://www.genesys.com/trust-center/security · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.genesys.com/trust-center/privacy · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.