Voucherify
voucherify.io · Loyalty and rewards · checked 2026-09-03
Rank 1 of 22 in Loyalty and rewards, where the median is 24.5.
- 7 found
- 5 not found
- 0 not measured
We measured 12 of 12 criteria for Voucherify on 2026-09-03. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 65 out of 100, band C.
Overview
Transparency labelsaas-ranking.com
Voucherify
- A
- B
- C
- D
- E
- F
Published commitments6 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- 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 Voucherify 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://voucherify.io/legal/subprocessors– reached, no match (HTTP 404)https://voucherify.io/subprocessors– reached, no match (HTTP 404)https://voucherify.io/sub-processors– reached, no match (HTTP 404)https://voucherify.io/legal/sub-processors– reached, no match (HTTP 404)https://voucherify.io/trust/subprocessors– reached, no match (HTTP 404)https://voucherify.io/privacy/subprocessors– reached, no match (HTTP 404)https://voucherify.io/legal/subprocessor-list– reached, no match (HTTP 404)
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://voucherify.io/– third-party requests before any interaction: api.intellimize.co, cdn.intellimize.co, cdn.jsdelivr.net, cdn.prod.website-files.com, challenges.cloudflare.com, d3e54v103j8qbb.cloudfront.net, forms-eu1.hscollectedforms.net, forms-eu1.hsforms.com, hubspotv2.use1-marketplace-1p-apps-prod-red.if.webflow.services, js-eu1.hs-analytics.net, js-eu1.hs-banner.com, js-eu1.hs-scripts.com, js-eu1.hscollectedforms.net, js.hs-scripts.com, log.intellimize.co, track-eu1.hubspot.com
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://voucherify.io/security– reached, no match (HTTP 404)https://voucherify.io/trust– reached, no match (HTTP 404)https://voucherify.io/trust-center– reached, no match (HTTP 404)https://voucherify.io/compliance– reached, no match (HTTP 404)https://voucherify.io/legal/security– reached, no match (HTTP 404)https://trust.voucherify.io/– The name "trust.voucherify.io" could not be resolved.
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://voucherify.io/legal/sla– reached, no match (HTTP 404)https://voucherify.io/sla– reached, no match (HTTP 404)https://voucherify.io/legal/service-level-agreement– reached, no match (HTTP 404)https://voucherify.io/trust/sla– reached, no match (HTTP 404)https://voucherify.io/uptime– reached, no match (HTTP 404)https://voucherify.io/legal/uptime-sla– reached, no match (HTTP 404)
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://voucherify.io/.well-known/security.txt– 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 7
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://www.voucherify.io/legal/data-processing-agreement-v1-6 · checked 2026-09-03
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://www.voucherify.io/legal/privacy-policy-v1-8 · checked 2026-09-03
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://status.voucherify.io/ · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.voucherify.io/pricing · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://voucherify.io/ · 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.voucherify.io/legal/data-processing-agreement-v1-6 · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.voucherify.io/legal/privacy-policy-v1-8 · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.