Haufe
haufe.de · HR and payroll · checked 2026-09-03
Rank 13 of 13 in HR and payroll, where the median is 35.
- 1 found
- 10 not found
- 1 not measured
We measured 11 of 12 criteria for Haufe on 2026-09-03. We found 1 with a source and did not find 10 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 5 out of 100, band F.
Overview
Transparency labelsaas-ranking.com
Haufe
- A
- B
- C
- D
- E
- F
Published commitments1 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour0 of 2 found, 1 not measured
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not measuredsecurity.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 Haufe has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://haufe.de/legal/dpa– reached, no match (HTTP 404)https://haufe.de/dpa– reached, no match (HTTP 404)https://haufe.de/legal/data-processing-agreement– reached, no match (HTTP 404)https://haufe.de/data-processing-agreement– reached, no match (HTTP 404)https://haufe.de/legal/data-processing-addendum– reached, no match (HTTP 404)https://haufe.de/legal/gdpr– reached, no match (HTTP 404)https://haufe.de/trust/dpa– reached, no match (HTTP 404)https://haufe.de/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://haufe.de/legal/subprocessors– reached, no match (HTTP 404)https://haufe.de/subprocessors– reached, no match (HTTP 404)https://haufe.de/sub-processors– reached, no match (HTTP 404)https://haufe.de/legal/sub-processors– reached, no match (HTTP 404)https://haufe.de/trust/subprocessors– reached, no match (HTTP 404)https://haufe.de/privacy/subprocessors– reached, no match (HTTP 404)https://haufe.de/legal/subprocessor-list– reached, no match (HTTP 404)
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://haufe.de/security– reached, no match (HTTP 404)https://haufe.de/trust– reached, no match (HTTP 404)https://haufe.de/legal/privacy– reached, no match (HTTP 404)https://haufe.de/privacy– reached, no match (HTTP 404)https://haufe.de/privacy-policy– reached, no match (HTTP 404)https://haufe.de/compliance– reached, no match (HTTP 410)https://haufe.de/legal/privacy-policy– reached, no match (HTTP 404)
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.haufe.de/– The name "status.haufe.de" could not be resolved.https://haufe.de/status– reached, no match (HTTP 404)https://haufe.de.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-03.
Show the 5 addresses we checked
https://haufe.de/pricing– reached, no match (HTTP 404)https://haufe.de/pricing/– reached, no match (HTTP 404)https://haufe.de/plans– reached, no match (HTTP 404)https://haufe.de/en/pricing– reached, no match (HTTP 404)https://haufe.de/pricing-plans– reached, no match (HTTP 404)
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-03.
Show the 2 addresses we checked
http://haufe.de/– redirects to https://haufe.de:443/https://haufe.de/– no HSTS header
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://haufe.de/– third-party requests before any interaction: api.usercentrics.eu, app.usercentrics.eu, cdn.prod.website-files.com, consent-api.service.consent.usercentrics.eu, d3e54v103j8qbb.cloudfront.net, www.googletagmanager.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://haufe.de/legal/subprocessors– reached, no match (HTTP 404)https://haufe.de/subprocessors– reached, no match (HTTP 404)https://haufe.de/sub-processors– reached, no match (HTTP 404)https://haufe.de/legal/dpa– reached, no match (HTTP 404)https://haufe.de/dpa– reached, no match (HTTP 404)https://haufe.de/legal/data-processing-agreement– reached, no match (HTTP 404)https://haufe.de/trust/subprocessors– reached, no match (HTTP 404)https://haufe.de/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://haufe.de/security– reached, no match (HTTP 404)https://haufe.de/trust– reached, no match (HTTP 404)https://haufe.de/trust-center– reached, no match (HTTP 404)https://haufe.de/compliance– reached, no match (HTTP 410)https://haufe.de/legal/security– reached, no match (HTTP 404)https://trust.haufe.de/– The name "trust.haufe.de" 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://haufe.de/legal/sla– reached, no match (HTTP 404)https://haufe.de/sla– reached, no match (HTTP 404)https://haufe.de/legal/service-level-agreement– reached, no match (HTTP 404)https://haufe.de/trust/sla– reached, no match (HTTP 404)https://haufe.de/uptime– reached, no match (HTTP 404)https://haufe.de/legal/uptime-sla– 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 1
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.haufe.de/datenschutzerklaerung_24_534492.html · checked 2026-09-03
Not measured by us 1
security.txt (RFC 9116)
weight 1 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 1 address we checked
https://haufe.de/.well-known/security.txt– blocked or unavailable (HTTP 403)
History
Not enough completed runs yet to draw a line. The next runs fill this in.