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