Transparency alternatives to Justpark
Other Parking management vendors we measure, sorted by how much we found at them and not at Justpark. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Justpark on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Justpark has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Justpark” is the one that closes them.
| Vendor | Score | Found there, not found at Justpark | Found at Justpark, not found there | |
|---|---|---|---|---|
| Parkalotparkalot.ioSee also Transparency alternatives to Parkalot | 22/100 | 2 Data location stated, Public pricing | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Parkableparkable.comSee also Transparency alternatives to Parkable | 35/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Designadesigna.comSee also Transparency alternatives to Designa | 26/100 | 1 Data location stated | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Parkmobileparkmobile.ioSee also Transparency alternatives to Parkmobile | 26/100 | 1 Data location stated | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Skidataskidata.comSee also Transparency alternatives to Skidata | 22/100 | 1 Subprocessor list | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Parqueryparquery.comSee also Transparency alternatives to Parquery | 19/100 | 1 Data location stated | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Scheidt Bachmannscheidt-bachmann.deSee also Transparency alternatives to Scheidt Bachmann | 17/100 | 1 No third-party tracking before consent | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Spotherospothero.comSee also Transparency alternatives to Spothero | 14/100 | 1 Data location stated | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Easyparkeasypark.netSee also Transparency alternatives to Easypark | 19/100 | nothing we found there and not here | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Parkwhizparkwhiz.comSee also Transparency alternatives to Parkwhiz | 17/100 | nothing we found there and not here | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Paybyphonepaybyphone.comSee also Transparency alternatives to Paybyphone | 17/100 | nothing we found there and not here | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Wemolowemolo.comSee also Transparency alternatives to Wemolo | 17/100 | nothing we found there and not here | 1 Certifications named | 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.