Re:amaze
reamaze.com · Helpdesk · checked 2026-09-03
Rank 9 of 22 in Helpdesk, where the median is 39.5.
- 5 found
- 7 not found
- 0 not measured
We measured 12 of 12 criteria for Re:amaze on 2026-09-03. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 43 out of 100, band D.
Overview
Transparency labelsaas-ranking.com
Re:amaze
- A
- B
- C
- D
- E
- F
Published commitments4 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.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 Re:amaze has no such document.
Gaps, heaviest first
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://reamaze.com/legal/subprocessors– reached, no match (HTTP 200)https://reamaze.com/subprocessors– reached, no match (HTTP 200)https://reamaze.com/sub-processors– reached, no match (HTTP 200)https://reamaze.com/legal/sub-processors– reached, no match (HTTP 200)https://reamaze.com/trust/subprocessors– reached, no match (HTTP 200)https://reamaze.com/privacy/subprocessors– reached, no match (HTTP 200)https://reamaze.com/legal/subprocessor-list– reached, no match (HTTP 200)
Data location stated
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://reamaze.com/security– reached, no match (HTTP 200)https://reamaze.com/trust– reached, no match (HTTP 200)https://reamaze.com/legal/privacy– reached, no match (HTTP 200)https://reamaze.com/privacy– reached, no match (HTTP 200)https://reamaze.com/privacy-policy– reached, no match (HTTP 200)https://reamaze.com/compliance– reached, no match (HTTP 200)https://reamaze.com/legal/privacy-policy– reached, no match (HTTP 200)
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.reamaze.com/– reached, no match (HTTP 404)https://reamaze.com/status– reached, no match (HTTP 200)https://reamaze.com.statuspage.io/– Could not be fetched: fetch failed.
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://reamaze.com/– third-party requests before any interaction: assets.calendly.com, cdnjs.cloudflare.com, csp.secureserver.net, googleads.g.doubleclick.net, img1.wsimg.com, maxcdn.bootstrapcdn.com, play.google.com, player.vimeo.com, region1.analytics.google.com, stats.g.doubleclick.net, tracking-api.g2.com, tracking.g2crowd.com, www.google-analytics.com, www.google.de, www.googleadservices.com, www.googletagmanager.com
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://reamaze.com/security– reached, no match (HTTP 200)https://reamaze.com/trust– reached, no match (HTTP 200)https://reamaze.com/trust-center– reached, no match (HTTP 200)https://reamaze.com/compliance– reached, no match (HTTP 200)https://reamaze.com/legal/security– reached, no match (HTTP 200)https://trust.reamaze.com/– 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://reamaze.com/legal/sla– reached, no match (HTTP 200)https://reamaze.com/sla– reached, no match (HTTP 200)https://reamaze.com/legal/service-level-agreement– reached, no match (HTTP 200)https://reamaze.com/trust/sla– reached, no match (HTTP 200)https://reamaze.com/uptime– reached, no match (HTTP 200)https://reamaze.com/legal/uptime-sla– reached, no match (HTTP 200)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://reamaze.com/.well-known/security.txt– reached, no match (HTTP 406)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 5
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://www.reamaze.com/dpa · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.reamaze.com/pricing · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://reamaze.com/ · checked 2026-09-03
Notice before subprocessors change
weight 2 of 3The vendor commits publicly to giving notice before the list changes.
Source: https://www.reamaze.com/dpa · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.reamaze.com/privacy · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.