SaaS Ranking

Moqo

moqo.de · Car rental and fleet sharing · checked 2026-09-04

22/100FBand F

Rank 3 of 17 in Car rental and fleet sharing, where the median is 9.

We measured 12 of 12 criteria for Moqo on 2026-09-04. We found 2 with a source and did not find 10 at the addresses we checked. That is a transparency score of 22 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Moqo

moqo.de · Car rental and fleet sharing

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

Published commitments1 of 9 found

Measured behaviour1 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 Moqo 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://moqo.de/legal/dpa – reached, no match (HTTP 404)
  2. https://moqo.de/dpa – reached, no match (HTTP 404)
  3. https://moqo.de/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://moqo.de/data-processing-agreement – reached, no match (HTTP 404)
  5. https://moqo.de/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://moqo.de/legal/gdpr – reached, no match (HTTP 404)
  7. https://moqo.de/trust/dpa – reached, no match (HTTP 404)
  8. https://moqo.de/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://moqo.de/legal/subprocessors – reached, no match (HTTP 404)
  2. https://moqo.de/subprocessors – reached, no match (HTTP 404)
  3. https://moqo.de/sub-processors – reached, no match (HTTP 404)
  4. https://moqo.de/legal/sub-processors – reached, no match (HTTP 404)
  5. https://moqo.de/trust/subprocessors – reached, no match (HTTP 404)
  6. https://moqo.de/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://moqo.de/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.moqo.de/ – reached, no match (HTTP 200)
  2. https://moqo.de/status – reached, no match (HTTP 404)
  3. https://moqo.de.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-04.

Show the 5 addresses we checked
  1. https://moqo.de/pricing – reached, no match (HTTP 404)
  2. https://moqo.de/pricing/ – reached, no match (HTTP 404)
  3. https://moqo.de/plans – reached and rendered, no match
  4. https://moqo.de/en/pricing – reached, no match (HTTP 404)
  5. https://moqo.de/pricing-plans – reached, no match (HTTP 404)

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://moqo.de/ – third-party requests before any interaction: accounts.finsweet.com, ad.doubleclick.net, cdn.jsdelivr.net, cdn.prod.website-files.com, d3e54v103j8qbb.cloudfront.net, googleads.g.doubleclick.net, region1.analytics.google.com, stats.g.doubleclick.net, www.google.com, www.google.de, www.googleadservices.com, www.googletagmanager.com, www.gstatic.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://moqo.de/legal/subprocessors – reached, no match (HTTP 404)
  2. https://moqo.de/subprocessors – reached, no match (HTTP 404)
  3. https://moqo.de/sub-processors – reached, no match (HTTP 404)
  4. https://moqo.de/legal/dpa – reached, no match (HTTP 404)
  5. https://moqo.de/dpa – reached, no match (HTTP 404)
  6. https://moqo.de/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://moqo.de/trust/subprocessors – reached, no match (HTTP 404)
  8. https://moqo.de/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://moqo.de/security – reached, no match (HTTP 404)
  2. https://moqo.de/trust – reached, no match (HTTP 404)
  3. https://moqo.de/trust-center – reached, no match (HTTP 404)
  4. https://moqo.de/compliance – reached, no match (HTTP 404)
  5. https://moqo.de/legal/security – reached, no match (HTTP 404)
  6. https://trust.moqo.de/ – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://moqo.de/legal/sla – reached, no match (HTTP 404)
  2. https://moqo.de/sla – reached, no match (HTTP 404)
  3. https://moqo.de/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://moqo.de/trust/sla – reached, no match (HTTP 404)
  5. https://moqo.de/uptime – reached, no match (HTTP 404)
  6. https://moqo.de/legal/uptime-sla – reached, no match (HTTP 404)

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://moqo.de/.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://moqo.de/legal/privacy – reached, no match (HTTP 404)
  2. https://moqo.de/privacy – reached, no match (HTTP 404)
  3. https://moqo.de/privacy-policy – reached, no match (HTTP 200)
  4. https://moqo.de/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://moqo.de/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://moqo.de/trust/privacy – reached, no match (HTTP 404)
  7. https://moqo.de/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 2

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Belgium, Frankfurt, United States.
    Show the 3 exact wordings

    al Clauses) Website and customer data processing … Odoo S.A.Chaussée de Namur, 401367 Grand-Rosière Belgium Enterprise Resource Planning The storage period depends on legal retention obligations or ne...

    Read at https://moqo.de/privacy-policy

    Kennedy, L-1855 Luxembourg Server and hosting services, primarily email sending, SMS for 2FA (Frankfurt server region) Customer service and communication services walter services GmbH Eduard-Rhein-Str...

    Read at https://moqo.de/privacy-policy

    The information generated by the cookies is usually transferred to a Google server in the USA and stored there.

    Read at https://moqo.de/privacy-policy

Source: https://moqo.de/privacy-policy · checked 2026-09-04

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

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

    max-age=31536000; includeSubDomains; preload

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

    max-age=31536000; includeSubDomains; preload

    Read at https://moqo.de/

    max-age=31536000; includeSubDomains; preload

    Read at https://moqo.de/

Source: https://moqo.de/ · checked 2026-09-04

History

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

Compare