SaaS Ranking

Mapme

mapme.com · GIS and mapping · checked 2026-09-04

26/100EBand E

Rank 16 of 26 in GIS and mapping, where the median is 30.

We measured 12 of 12 criteria for Mapme on 2026-09-04. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 26 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Mapme

mapme.com · GIS and mapping

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 26of 100 Rank 16 of 26

Published commitments3 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-04. 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 Mapme has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://mapme.com/legal/dpa – reached, no match (HTTP 404)
  2. https://mapme.com/dpa – reached, no match (HTTP 404)
  3. https://mapme.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://mapme.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://mapme.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://mapme.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://mapme.com/trust/dpa – reached, no match (HTTP 404)
  8. https://mapme.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://mapme.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://mapme.com/subprocessors – reached, no match (HTTP 404)
  3. https://mapme.com/sub-processors – reached, no match (HTTP 404)
  4. https://mapme.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://mapme.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://mapme.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://mapme.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-04.

Show the 3 addresses we checked
  1. https://status.mapme.com/ – reached, no match (HTTP 200)
  2. https://mapme.com/status – reached, no match (HTTP 404)
  3. https://mapme.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-04.

Show the 2 addresses we checked
  1. http://mapme.com/ – redirects to https://mapme.com/
  2. https://mapme.com/ – no HSTS header

Is this wrong? Send us the URL

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://mapme.com/ – third-party requests before any interaction: ad.doubleclick.net, ajax.googleapis.com, fonts.gstatic.com, region1.analytics.google.com, stats.g.doubleclick.net, widget.intercom.io, www.google.com, www.google.de, www.googletagmanager.com

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://mapme.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://mapme.com/subprocessors – reached, no match (HTTP 404)
  3. https://mapme.com/sub-processors – reached, no match (HTTP 404)
  4. https://mapme.com/legal/dpa – reached, no match (HTTP 404)
  5. https://mapme.com/dpa – reached, no match (HTTP 404)
  6. https://mapme.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://mapme.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://mapme.com/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://mapme.com/security – reached, no match (HTTP 404)
  2. https://mapme.com/trust – reached, no match (HTTP 404)
  3. https://mapme.com/trust-center – reached, no match (HTTP 404)
  4. https://mapme.com/compliance – reached, no match (HTTP 404)
  5. https://mapme.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.mapme.com/ – The name "trust.mapme.com" could not be resolved.

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://mapme.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://mapme.com/legal/privacy – reached, no match (HTTP 404)
  2. https://mapme.com/privacy – reached, no match (HTTP 404)
  3. https://mapme.com/privacy-policy – reached, no match (HTTP 200)
  4. https://mapme.com/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://mapme.com/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://mapme.com/trust/privacy – reached, no match (HTTP 404)
  7. https://mapme.com/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 3

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording United States.
    Show the exact wording

    Data Hosting and service providers ‘Mapme Users’ personal Information is maintained, processed, and stored by Mapme and our authorized affiliates in the United States of America using secured cloud st...

    Read at https://mapme.com/privacy-policy/

Source: https://mapme.com/privacy-policy/ · checked 2026-09-04

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://mapme.com/pricing/ · checked 2026-09-04

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 100 %.
    Show the exact wording

    ual fee divided by 12, as follows: Total Available Uptime (across all APIs) per month Credit Amount 100% – 99.9% 0% 99.89% – 99% 10% Less than 99% 20% To receive a credit, you must contact Mapme withi...

    Read at https://mapme.com/sla/

Source: https://mapme.com/sla/ · checked 2026-09-04

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare