Transparency alternatives to Zeplug
Other EV charging software vendors we measure, sorted by how much we found at them and not at Zeplug. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Zeplug on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Zeplug has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Zeplug” is the one that closes them.
| Vendor | Score | Found there, not found at Zeplug | Found at Zeplug, not found there | |
|---|---|---|---|---|
| Chargepointchargepoint.comSee also Transparency alternatives to Chargepoint | 32/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Driivzdriivz.comSee also Transparency alternatives to Driivz | 35/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Reevreev.comSee also Transparency alternatives to Reev | 30/100 | 3 Data processing agreement, Data location stated, Named privacy contact | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Easeeeasee.comSee also Transparency alternatives to Easee | 26/100 | 3 Data location stated, Status page with history, Named privacy contact | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Virtavirta.globalSee also Transparency alternatives to Virta | 26/100 | 3 Status page with history, Certifications named, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Plugsurfingplugsurfing.comSee also Transparency alternatives to Plugsurfing | 22/100 | 2 Status page with history, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Zapteczaptec.comSee also Transparency alternatives to Zaptec | 22/100 | 2 Status page with history, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Hubjecthubject.comSee also Transparency alternatives to Hubject | 22/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Ellielli.ecoSee also Transparency alternatives to Elli | 17/100 | 1 Named privacy contact | 1 Public pricing | Compare |
| Go-ego-e.comSee also Transparency alternatives to Go-e | 17/100 | 1 No third-party tracking before consent | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Mennekesmennekes.deSee also Transparency alternatives to Mennekes | 14/100 | 1 Named privacy contact | 1 Public pricing | Compare |
| Ampecoampeco.comSee also Transparency alternatives to Ampeco | 13/100 | 1 Certifications named | 2 Public pricing, security.txt (RFC 9116) | 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.