whats-best.ai

Whistleblowing Portals

Hintbox

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by lawcode GmbH · www.hintbox.de

Compare with EQS Integrity Line → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Skeptic

Weighted verdict

Assumes "audit-proof" and "100% anonymous" are marketing until the evidence says otherwise. Hunts certification claims without certificates, anonymity claims next to analytics scripts, per-report pricing traps and legal-update promises with no named lawyer. Exists to keep the rest of the bench honest.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Skeptic

Reporting channels & reporter experience

How this is scored

The intake side: how a reporter actually submits — web form, anonymous dialog, phone/voice, languages, accessibility — and whether anonymity survives first contact.

0 — A web form that is an email in disguise: no anonymous route, no way to reach the reporter afterwards.

3 — An anonymous form exists but the dialogue ends there — no secured mailbox for follow-up questions, few languages, desktop-only.

5 — Anonymous two-way dialog via a protected mailbox, a usable set of languages, mobile-friendly; voice or phone intake missing or an add-on.

8 — Multiple channels (web, voice message or hotline, QR entry points), broad language coverage with translation support, accessibility considered, and the anonymous dialog is first-class rather than bolted on.

10 — Intake engineered around the frightened reporter: every channel anonymous-capable, dozens of languages, WCAG-conscious, no app install or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.

Report an error

The Skeptic

Anonymous two-way dialog is first-class: post-submission generated login lets the reporter come back, message and upload files anonymously, with 24–30 languages plus AI translation — though the site can't keep its own language count straight (30 in vs 24 in). Voice intake exists only as a paid add-on, and there is zero evidence on accessibility, mobile behavior or QR entry, so it stays short of the 8 anchor. 2 3 5

Report an error

Case management & deadline discipline

How this is scored

The case worker's side: triage, statutory deadlines (7-day acknowledgment, 3-month feedback), role separation, audit-proof documentation.

0 — Reports land in an inbox; deadlines, roles and history live in a spreadsheet next door.

3 — A case list with status fields, but deadlines are manual, permissions are all-or-nothing, and the record of who did what is thin.

5 — Deadline tracking with reminders for the statutory clocks, case notes and attachments, basic role separation between case handlers; reporting on the caseload is limited.

8 — Automated statutory clocks, conflict-of-interest handling (excluding implicated case handlers), complete tamper-evident case history, retention and deletion rules applied per case, and management reporting.

10 — A case system an external investigator can rely on: enforced workflows, full audit trail, legally aware retention/deletion automation, evidence handling, and statistics that survive a regulator's questions.

Report an error

The Skeptic

Triage with automatic prioritization, deadline support explicitly including the feedback-to-reporter clock, receipt confirmation, a claimed tamper-proof ('revisionssicher') history and granular per-company/per-case permissions clear the 5 anchor. But conflict-of-interest exclusion of implicated handlers is nowhere, retention/deletion is a manual 'can be deleted' capability, not automation, and management reporting goes no further than export formats — that keeps it off 8. 3 4 5

Report an error

Legal compliance alignment

How this is scored

How specifically the product implements EU Directive 2019/1937 and national transpositions (HinSchG et al.) — not whether the marketing mentions them.

0 — Generic feedback software wearing a whistleblowing label; no reference to the legal obligations it claims to satisfy.

3 — The directive is invoked in marketing but the mapping is vague; deadline rules, documentation duties and retention periods are the customer's problem.

5 — The statutory duties are implemented as product features — acknowledgment and feedback clocks, documentation, deletion after the retention period — for at least one national law, with guidance for the rest.

8 — Multiple national transpositions supported with their differing details, legal templates and process guidance maintained by named counsel or documented review, and updates when the law moves.

10 — The product is a legal instrument: per-country rule sets kept current, documented legal review, guidance for edge cases (group-wide channels, external ombudsman setups), and the vendor shows its homework in public.

Report an error

The Skeptic

Directive 2019/1937 is not just marketing here: acknowledgment, feedback deadlines, tamper-proof documentation and deletion per the directive are named as product features. But the overall claim 'wir erfüllen sämtliche Anforderungen' is a blanket assertion — HinSchG is never named, there is no named counsel, no legal review documented, and no per-country rule sets, so it's one German implementation with guidance for nothing else. 4 4 5

Report an error

Security & anonymity assurance

How this is scored

Whether the confidentiality promise is engineered and evidenced: encryption, metadata handling, penetration tests, certifications.

0 — Security is a paragraph of adjectives; no certificates, no test reports, no statement on metadata.

3 — TLS and encryption at rest asserted, but nothing audited: no ISO 27001 or equivalent, no published pentest, silence on IP and metadata logging.

5 — A current ISO 27001 (or equivalent) certificate for vendor or hosting, end-to-end encryption of report content claimed with some technical detail, an explicit no-IP-logging statement.

8 — Certified ISMS covering the product, regular third-party penetration tests attested, documented end-to-end encryption architecture, metadata minimization explained, security contact and disclosure policy published.

10 — Assurance a hostile auditor accepts: current certificates with visible scope, recurring pentest summaries public, cryptographic architecture documented, anonymity analysed against the operator itself — the vendor can answer "how would you unmask a reporter?" with "we cannot, and here is why".

Report an error

The Skeptic

The architecture story is genuinely good: data 'arrives already encrypted on our servers' so neither vendor nor third parties can read it, explicit no-IP/MAC/location-logging, metadata stripped before encryption, TLS and separate database encryption. But 'ISO 27001 zertifiziert' and 'regelmäßige Penetrationstests, positiv auditiert' are exactly the certification claims without certificates, scope statements, tester names or dates that I treat as marketing until shown — no security contact or disclosure policy either. 1 3 4

Report an error

Group & multi-entity capability

How this is scored

Whether one contract can serve a corporate group: separate channels per legal entity, central oversight, ombudsman access, white-labeling.

0 — One company, one channel; a group buys and administers N separate instances.

3 — Multiple channels under one account, but no separation of case access per entity and no consolidated view.

5 — Per-entity channels with separated case handlers and a group-level overview; branding per entity is basic; external counsel access possible.

8 — Real multi-tenant group structure: per-entity channels, languages and branding, delegated administration, external ombudsman roles, group reporting that respects entity boundaries.

10 — Group compliance as architecture: hundreds of entities manageable centrally, per-country legal rule assignment per entity, white-label reporting pages, and access separation strong enough to satisfy each subsidiary's works council.

Report an error

The Skeptic

Groups can create additional entities, reporters pick the entity at intake, and access rights are controllable per company and case, with external persons invitable per case and a white-label partner program — that earns the 5 anchor. But there is no evidence of a consolidated group-level view or reporting, no delegated administration, and the 'Ombudslösung' is one marketing sentence with no functional detail; group contracts are custom quotes anyway. 3 6 5

Report an error

European sovereignty

How this is scored

Where reports about people actually live and under whose law — entity, hosting, subprocessors, DPA. In this category the data is by definition the most sensitive a company holds.

0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for whistleblowing data.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.

5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.

8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.

10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors for report content and metadata, on-premises or sovereign-cloud options, and the whole chain documented publicly.

Report an error

The Skeptic

The imprint settles what the evidence's attributes call 'unknown': lawcode GmbH, Amtsgericht Koblenz HRB 28116, German seat and VAT ID, with hosting exclusively at Hetzner in a German ISO 27001 data center and an explicit no-third-country-transfer statement. That is jurisdictionally clean but short of the 8 anchor: no published DPA document, no TOMs, no subprocessor list, and ownership is undocumented — for whistleblowing data I want that chain in public, not implied. 1 4 7

Report an error

Pricing transparency

How this is scored

Whether an obligated company can compute the real invoice — per entity, per employee band, per year — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — An entry price exists, but the tiers most obligated companies need are unpriced, or the maths is obscured by employee bands, per-report fees or mandatory setup charges.

5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability — extra entities, extra languages, phone intake — hides in an unpriced add-on.

8 — Every tier priced publicly with employee-band boundaries, entity rules and setup fees stated; only genuine corporate-group contracts are custom.

10 — Complete price computability: every tier, band, add-on and renewal rule public, so the invoice for a 60-employee company and a 5-entity group is a two-minute exercise.

Report an error

The Skeptic

A single-entity invoice is fully computable: €99/month net plus 19% VAT, seat-independent, with every add-on priced on the page (voice bot €49, email and domain €29) and setup costs explicit (onboarding €390, training €199/hour). What keeps it off 8: the €149 Premium tier appears only in the FAQ with no published feature boundary against Basis, and multi-entity groups are pushed into custom quotes. 1 2 5

Report an error

European sovereignty — proven facts

2 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency EU only ⚠ unverified 3/3 pts 4 Report an error
Subprocessors EU only ⚠ unverified 2/2 pts 1 Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (9)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.hintbox.de Checked 15 Sep 2026 Details →
  2. 2 Pricing page www.hintbox.de Checked 15 Sep 2026 Details →
  3. 3 Features page www.hintbox.de Checked 15 Sep 2026 Details →
  4. 4 Security & privacy page www.hintbox.de Checked 15 Sep 2026 +1 earlier capture: 15 Sep 2026 Details →
  5. 5 FAQ www.hintbox.de Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
  6. 6 About / vendor entity www.hintbox.de Checked 15 Sep 2026 Details →
  7. 7 Imprint www.hintbox.de Checked 15 Sep 2026 Details →
  8. 8 Reporting channels & reporter experience — found from sitemap www.hintbox.de Checked 1 Oct 2026 Details →
  9. 9 Reporting channels & reporter experience — found from sitemap www.hintbox.de Checked 1 Oct 2026 Details →