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