Whistleblowing Portals

otris Hinweisgebersystem

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

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

by otris software AG · www.otris.de

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Compliance Officer v1.0 · The Reporter's Advocate v1.0 · The SME Operator v1.2 · The Group Counsel v1.0 · The Security Auditor v1.0 · The Skeptic v1.2 · rubric v1 · evaluated 15 Sep 2026

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 SME Operator

Weighted verdict

Runs a 60-employee company that the law obligated, not convinced. Optimizes for compliance set up in an afternoon at a price the year-end review will not question, with the legal duties handled by the product. Rejects per-report fees, setup charges and anything that needs a compliance department to operate.

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

Scored by The SME Operator

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 SME Operator

The anonymous mailbox protected by password and ID gives me the two-way anonymous dialog the law requires, but the evidence is silent on languages, mobile and accessibility — and phone hotline and ombudsperson are framed as alternatives to the software, not channels in it. That clears rubric level 3 but cannot reach 5 without the language and mobile evidence. 2 6

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 SME Operator

Workflows, templates and automated warnings before processing deadlines are claimed, which is the statutory clock I would otherwise track by hand. But role separation, audit-proof history, retention automation and caseload reporting are all unevidenced, so it lands below the anchor where those appear. 6

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 SME Operator

Directive 2019/1937 shows up only in an educational wiki explainer, and the German-market orientation of the suite (Hinweisgebersystem, Rechtskataster) does not map the 7-day acknowledgment, 3-month feedback or retention periods to product features. The directive is invoked, not implemented-and-documented — the legal homework stays mine. 1 6

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 SME Operator

ISO 27001 for otris systems GmbH, the Oldenburg subsidiary that runs the cloud, is real certification, and end-to-end encryption is asserted — but with no technical architecture, no pentest, no no-IP-logging statement, and the site's cookie stack (GA4, LinkedIn, Cloudflare) unaddressed for the reporting platform, I cannot present this as anchor-5 assurance. 3 5 6

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 SME Operator

Nothing evidences per-entity channels, separated case access or a group overview for the Hinweisgebersystem; the ombudsperson is explicitly an alternative to the software and group-oriented modules like Konzerndatenschutz live in a different suite. For my single entity this is moot, but scored on evidence it sits near the bottom anchor. 1 6

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 SME Operator

A Dortmund AG running its cloud on its own Oldenburg subsidiary's servers, with an on-premises option and AI confined to a Swedish EWR datacenter with no training on data, is the posture I want for the most sensitive data we hold. It falls short of the top anchors because no product DPA, subprocessor list or TOMs are published, and US-reach processors (Cloudflare, Calendly, Microsoft) are documented around it. 1 3 5

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 SME Operator

Not a single price, tier or employee band appears anywhere in the captured pages; the only buying signal is a sales phone number and vertrieb@ email. An enterprise suite where every tier is a sales conversation is precisely the invoice I cannot defend at year-end. 1 3

Report an error

European sovereignty — proven facts

1 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.

Legal entity	Incorporated in DE	3/3 pts	4 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined ⚠ unverified	—	uncited Report an error
Subprocessors	Not determined ⚠ unverified	—	uncited Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 23 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

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.

We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
28 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
16 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
12 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us

Do you know more about otris Hinweisgebersystem? Tell us Report an error on this page

Sources (16)

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

1 Vendor homepage www.otris.de Checked 15 Sep 2026 +1 earlier capture: 23 Aug 2026 Details →
2 Hinweisgebersystem explainer www.otris.de Checked 15 Sep 2026 Details →
3 Vendor facts page www.otris.de Checked 15 Sep 2026 Details →
4 Imprint www.otris.de Checked 15 Sep 2026 Details →
5 Privacy policy www.otris.de Checked 15 Sep 2026 Details →
6 Whistleblowing wiki/product page www.otris.de Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
7 Security / trust page — found from the homepage www.otris.de Checked 30 Sep 2026 Details →
8 Reporting channels & reporter experience — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
9 Reporting channels & reporter experience — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
10 Case management & deadline discipline — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
11 Legal compliance alignment — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
12 Legal compliance alignment — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
13 Security & anonymity assurance — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
14 Security & anonymity assurance — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
15 Group & multi-entity capability — found from sitemap www.otris.de Checked 1 Oct 2026 Details →
16 Group & multi-entity capability — found from sitemap www.otris.de Checked 1 Oct 2026 Details →