GIS Cloud
giscloud.com · GIS and mapping · checked 2026-09-03
Rank 2 of 18 in GIS and mapping, where the median is 30.
- 6 found
- 5 not found
- 1 not measured
We measured 11 of 12 criteria for GIS Cloud on 2026-09-03. We found 6 with a source and did not find 5 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 55 out of 100, band C.
Overview
Transparency labelsaas-ranking.com
GIS Cloud
- A
- B
- C
- D
- E
- F
Published commitments5 of 9 found
- not foundData processing agreement×3
- foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 2 found, 1 not measured
- not foundHTTPS enforced with HSTS×2
- foundNo third-party tracking before consent×2
- not measuredsecurity.txt (RFC 9116)×1
Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that GIS Cloud has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://giscloud.com/legal/dpa– reached, no match (HTTP 404)https://giscloud.com/dpa– reached, no match (HTTP 404)https://giscloud.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://giscloud.com/data-processing-agreement– reached, no match (HTTP 404)https://giscloud.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://giscloud.com/legal/gdpr– reached, no match (HTTP 404)https://giscloud.com/trust/dpa– reached, no match (HTTP 404)https://giscloud.com/privacy/dpa– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-03.
Show the 3 addresses we checked
https://status.giscloud.com/– reached, no match (HTTP 200)https://giscloud.com/status– reached, no match (HTTP 404)https://giscloud.com.statuspage.io/– Could not be fetched: fetch failed.
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-03.
Show the 2 addresses we checked
http://giscloud.com/– redirects to https://giscloud.com/https://giscloud.com/– no HSTS header
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://giscloud.com/legal/subprocessors– reached, no match (HTTP 404)https://giscloud.com/subprocessors– reached, no match (HTTP 200)https://giscloud.com/sub-processors– reached, no match (HTTP 404)https://giscloud.com/legal/dpa– reached, no match (HTTP 404)https://giscloud.com/dpa– reached, no match (HTTP 404)https://giscloud.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://giscloud.com/trust/subprocessors– reached, no match (HTTP 404)https://giscloud.com/legal/sub-processors– reached, no match (HTTP 404)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://giscloud.com/legal/sla– reached, no match (HTTP 404)https://giscloud.com/sla– reached, no match (HTTP 404)https://giscloud.com/legal/service-level-agreement– reached, no match (HTTP 404)https://giscloud.com/trust/sla– reached, no match (HTTP 404)https://giscloud.com/uptime– reached, no match (HTTP 404)https://giscloud.com/legal/uptime-sla– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 6
Subprocessor list
weight 3 of 3The actual list is published, not just a promise to keep one.
Source: https://www.giscloud.com/subprocessors/ · checked 2026-09-03
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://www.giscloud.com/privacy-policy/ · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.giscloud.com/pricing/ · checked 2026-09-03
No third-party tracking before consent
weight 2 of 3No third-party requests before any interaction.
Source: https://giscloud.com/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://www.giscloud.com/security/ · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.giscloud.com/privacy-policy/ · checked 2026-09-03
Not measured by us 1
security.txt (RFC 9116)
weight 1 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 1 address we checked
https://giscloud.com/.well-known/security.txt– blocked or unavailable (HTTP 403)
History
Not enough completed runs yet to draw a line. The next runs fill this in.