Transparency alternatives to Mapme
Other GIS and mapping vendors we measure, sorted by how much we found at them and not at Mapme. This is a comparison of disclosure, not of features or fitness.
12 shown of 52 that differ from Mapme on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Mapme has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Mapme” is the one that closes them.
| Vendor | Score | Found there, not found at Mapme | Found at Mapme, not found there | |
|---|---|---|---|---|
| Mapboxmapbox.comSee also Transparency alternatives to Mapbox | 61/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | nothing | Compare |
| Safe Software FMEsafe.comSee also Transparency alternatives to Safe Software FME | 52/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 2 Public pricing, Uptime SLA with a figure | Compare |
| GIS Cloudgiscloud.comSee also Transparency alternatives to GIS Cloud | 55/100 | 5 Subprocessor list, Data location stated, Certifications named, +2 | 1 Uptime SLA with a figure | Compare |
| Planetplanet.comSee also Transparency alternatives to Planet | 48/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 1 Uptime SLA with a figure | Compare |
| Bentley Systemsbentley.comSee also Transparency alternatives to Bentley Systems | 43/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| LightBoxlightboxre.comSee also Transparency alternatives to LightBox | 48/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| Feltfelt.comSee also Transparency alternatives to Felt | 39/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 Uptime SLA with a figure | Compare |
| Pointlypointly.aiSee also Transparency alternatives to Pointly | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Uptime SLA with a figure | Compare |
| CARTOcarto.comSee also Transparency alternatives to CARTO | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| Geocortexvertigis.comSee also Transparency alternatives to Geocortex | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| MetaLocatormetalocator.comSee also Transparency alternatives to MetaLocator | 38/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| UP42up42.comSee also Transparency alternatives to UP42 | 38/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Uptime SLA with a figure | 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.