Transparency alternatives to Pepperi
Other Retail operations vendors we measure, sorted by how much we found at them and not at Pepperi. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Pepperi on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Pepperi has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Pepperi” is the one that closes them.
| Vendor | Score | Found there, not found at Pepperi | Found at Pepperi, not found there | |
|---|---|---|---|---|
| MangoAppsmangoapps.comSee also Transparency alternatives to MangoApps | 70/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 Notice before subprocessors change | Compare |
| Firstupfirstup.ioSee also Transparency alternatives to Firstup | 61/100 | 7 Data processing agreement, Subprocessor list, Status page with history, +4 | 1 Notice before subprocessors change | Compare |
| YOOBICyoobic.comSee also Transparency alternatives to YOOBIC | 70/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | nothing | Compare |
| Repslyrepsly.comSee also Transparency alternatives to Repsly | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| Axeroaxerosolutions.comSee also Transparency alternatives to Axero | 61/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | nothing | Compare |
| Simpplrsimpplr.comSee also Transparency alternatives to Simpplr | 61/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | nothing | Compare |
| Happeohappeo.comSee also Transparency alternatives to Happeo | 43/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Haiilohaiilo.comSee also Transparency alternatives to Haiilo | 39/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 1 Notice before subprocessors change | Compare |
| Interactinteractsoftware.comSee also Transparency alternatives to Interact | 39/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 1 Notice before subprocessors change | Compare |
| Legionlegion.coSee also Transparency alternatives to Legion | 39/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 Notice before subprocessors change | Compare |
| Flipgetflip.comSee also Transparency alternatives to Flip | 30/100 | 4 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Notice before subprocessors change | Compare |
| GoSpotCheckgospotcheck.comSee also Transparency alternatives to GoSpotCheck | 30/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 2 Certifications named, 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.