SaaS Ranking

Measure

measure.com · Drone operations · checked 2026-09-04

Not enough data: 2 of 12 criteria measured, so no transparency score

We measured 2 of 12 criteria for Measure on 2026-09-04. We found 0 with a source and did not find 2 at the addresses we checked; 10 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.

Overview

Transparency labelsaas-ranking.com

Measure

measure.com · Drone operations

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data2 of 12 measured, no score

Published commitments9 not measured

Measured behaviour0 of 2 found, 1 not measured

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. We could measure 2 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Measure.

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 Measure 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

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://measure.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://measure.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://measure.com/

Checked 2 addresses on 2026-09-04.

Show the 2 addresses we checked
  1. http://measure.com/ – HTTP 200, no redirect to HTTPS
  2. https://measure.com/ – HSTS max-age=31536000

Is this wrong? Send us the URL

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

  • Third-party hosts we saw on the first load 2 spaceship-cdn.com, spaceship.com.
    Show the 2 exact wordings

    forsale.spaceship-cdn.com

    Read at https://measure.com/

    marketplacestats.service.spaceship.com

    Read at https://measure.com/

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://measure.com/ – third-party requests before any interaction: forsale.spaceship-cdn.com, marketplacestats.service.spaceship.com

Is this wrong? Send us the URL

Evidence

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

Not measured by us 10

Data processing agreement

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://measure.com/legal/dpa – Could not be fetched: fetch failed.
  2. https://measure.com/dpa – Could not be fetched: fetch failed.
  3. https://measure.com/legal/data-processing-agreement – Could not be fetched: fetch failed.
  4. https://measure.com/data-processing-agreement – Could not be fetched: fetch failed.
  5. https://measure.com/legal/data-processing-addendum – Could not be fetched: fetch failed.
  6. https://measure.com/legal/gdpr – Could not be fetched: fetch failed.
  7. https://measure.com/trust/dpa – Could not be fetched: fetch failed.
  8. https://measure.com/privacy/dpa – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://measure.com/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://measure.com/subprocessors – Could not be fetched: fetch failed.
  3. https://measure.com/sub-processors – Could not be fetched: fetch failed.
  4. https://measure.com/legal/sub-processors – Could not be fetched: fetch failed.
  5. https://measure.com/trust/subprocessors – Could not be fetched: fetch failed.
  6. https://measure.com/privacy/subprocessors – Could not be fetched: fetch failed.
  7. https://measure.com/legal/subprocessor-list – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Data location stated

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://measure.com/security – Could not be fetched: fetch failed.
  2. https://measure.com/trust – Could not be fetched: fetch failed.
  3. https://measure.com/legal/privacy – Could not be fetched: fetch failed.
  4. https://measure.com/privacy – Could not be fetched: fetch failed.
  5. https://measure.com/privacy-policy – Could not be fetched: fetch failed.
  6. https://measure.com/compliance – Could not be fetched: fetch failed.
  7. https://measure.com/legal/privacy-policy – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 3 addresses we checked
  1. https://status.measure.com/ – The name "status.measure.com" could not be resolved.
  2. https://measure.com/status – Could not be fetched: fetch failed.
  3. https://measure.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 5 addresses we checked
  1. https://measure.com/pricing – Could not be fetched: fetch failed.
  2. https://measure.com/pricing/ – Could not be fetched: fetch failed.
  3. https://measure.com/plans – Could not be fetched: fetch failed.
  4. https://measure.com/en/pricing – Could not be fetched: fetch failed.
  5. https://measure.com/pricing-plans – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://measure.com/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://measure.com/subprocessors – Could not be fetched: fetch failed.
  3. https://measure.com/sub-processors – Could not be fetched: fetch failed.
  4. https://measure.com/legal/dpa – Could not be fetched: fetch failed.
  5. https://measure.com/dpa – Could not be fetched: fetch failed.
  6. https://measure.com/legal/data-processing-agreement – Could not be fetched: fetch failed.
  7. https://measure.com/trust/subprocessors – Could not be fetched: fetch failed.
  8. https://measure.com/legal/sub-processors – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 6 addresses we checked
  1. https://measure.com/security – Could not be fetched: fetch failed.
  2. https://measure.com/trust – Could not be fetched: fetch failed.
  3. https://measure.com/trust-center – Could not be fetched: fetch failed.
  4. https://measure.com/compliance – Could not be fetched: fetch failed.
  5. https://measure.com/legal/security – Could not be fetched: fetch failed.
  6. https://trust.measure.com/ – The name "trust.measure.com" could not be resolved.

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 6 addresses we checked
  1. https://measure.com/legal/sla – Could not be fetched: fetch failed.
  2. https://measure.com/sla – Could not be fetched: fetch failed.
  3. https://measure.com/legal/service-level-agreement – Could not be fetched: fetch failed.
  4. https://measure.com/trust/sla – Could not be fetched: fetch failed.
  5. https://measure.com/uptime – Could not be fetched: fetch failed.
  6. https://measure.com/legal/uptime-sla – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 1 address we checked
  1. https://measure.com/.well-known/security.txt – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Named privacy contact

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://measure.com/legal/privacy – Could not be fetched: fetch failed.
  2. https://measure.com/privacy – Could not be fetched: fetch failed.
  3. https://measure.com/privacy-policy – Could not be fetched: fetch failed.
  4. https://measure.com/legal/privacy-policy – Could not be fetched: fetch failed.
  5. https://measure.com/legal/privacy-notice – Could not be fetched: fetch failed.
  6. https://measure.com/trust/privacy – Could not be fetched: fetch failed.
  7. https://measure.com/datenschutz – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

History

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

Compare