Transparency alternatives to MetaLocator
Other GIS and mapping vendors we measure, sorted by how much they publish that MetaLocator does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 53 that differ from MetaLocator on at least one criterion we measured for both. Public transparency score, not a product or security rating.
MetaLocator has 7 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, security.txt (RFC 9116). The column “publishes and MetaLocator does not” is the one that closes them.
| Vendor | Score | Publishes, and MetaLocator does not | MetaLocator publishes, and they do not | |
|---|---|---|---|---|
| Mapboxmapbox.com | 61/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 Data processing agreement | Compare |
| Planetplanet.com | 57/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 1 Data processing agreement | Compare |
| Safe Software FMEsafe.com | 52/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 Public pricing, Notice before subprocessors change | Compare |
| Bentley Systemsbentley.com | 43/100 | 4 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Public pricing, Notice before subprocessors change | Compare |
| GIS Cloudgiscloud.com | 55/100 | 3 Subprocessor list, Data location stated, Certifications named | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Pointlypointly.ai | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | Compare |
| eSpatialespatial.com | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Skyfiskyfi.com | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| CARTOcarto.com | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | Compare |
| Feltfelt.com | 30/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Geocortexvertigis.com | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Alteryx Spatialalteryx.com | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.