Transparency alternatives to NICE
Other Contact centre vendors we measure, sorted by how much we found at them and not at NICE. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from NICE on at least one criterion we measured for both. Public transparency score, not a product or security rating.
NICE has 7 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at NICE” is the one that closes them.
| Vendor | Score | Found there, not found at NICE | Found at NICE, not found there | |
|---|---|---|---|---|
| Aircallaircall.ioSee also Transparency alternatives to Aircall | 70/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| CloudTalkcloudtalk.ioSee also Transparency alternatives to CloudTalk | 61/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Puzzelpuzzel.comSee also Transparency alternatives to Puzzel | 47/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Public pricing, Certifications named | Compare |
| JustCalljustcall.ioSee also Transparency alternatives to JustCall | 43/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Nextivanextiva.comSee also Transparency alternatives to Nextiva | 43/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Enreachenreach.comSee also Transparency alternatives to Enreach | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Talkdesktalkdesk.comSee also Transparency alternatives to Talkdesk | 35/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| FreeClimbfreeclimb.comSee also Transparency alternatives to FreeClimb | 26/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Sipgatesipgate.deSee also Transparency alternatives to Sipgate | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Public pricing, Certifications named, +2 | Compare |
| CallHippocallhippo.comSee also Transparency alternatives to CallHippo | 59/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Call Handling VCCcallhandling.co.ukSee also Transparency alternatives to Call Handling VCC | 43/100 | 2 Subprocessor list, Status page with history | 2 Data processing agreement, Certifications named | Compare |
| CallMinercallminer.comSee also Transparency alternatives to CallMiner | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.