Whistleblowing Portals
EQS Integrity Line
EU origin, foreign-owned Report an errorPanel 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 EQS Group GmbH · www.integrityline.com
Compare with Hintbox → Compare with preeco | hinweisgeberschutz → Compare with NAVEX One EthicsPoint → 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 panel's verdict
EQS Integrity Line, a whistleblowing hotline from Munich-based EQS Group GmbH, is strongest on the reporter-facing channel: reporting channels & reporter experience sits at 7 with no spread, resting on anonymous two-way dialogue, 80+ languages with integrated machine translation, mobile optimization and a stated absence of tracking mechanisms. Security & anonymity assurance scored 6-7 on real attestations — ISO 27001 covering EQS Group and its data centres, a PwC ISAE 3000 Type I and II audit, CSA STAR — though judges criticized the 'latest encryption' claim as adjective-grade and noted no published pentest. The structural weakness is statutory work: legal compliance alignment landed flat at 3, the directive appearing in one marketing sentence with no transposition or deadline features, and case management & deadline discipline has granular need-to-know roles and dual control but nothing on 7-day/3-month clocks. Scores span 2-4 on group & multi-entity capability and 4-6 on sovereignty — hosting 'exclusively in Germany' against an undocumented chain: no DPA, no subprocessor list, 'geographically distributed' backups, US PE ownership (Thoma Bravo). Pricing is invisible beyond a 'Start free trial' button.
Speaks for it
- Anonymous two-way dialogue between whistleblower, case handler and external experts, available in 80+ languages with integrated machine translation
- ISO 27001 certification covering EQS Group and its data centres, plus a PwC ISAE 3000 Type I and II audit and CSA STAR registration
- Granular need-to-know permissions with configurable dual control and a revision log per case and per activity
- Hosting exclusively in Germany at a named Munich East data centre, under Munich-based EQS Group GmbH
- Mobile-optimized reporting for PC, smartphones and tablets, with a stated absence of tracking mechanisms
Held against it
- EU Whistleblowing Directive compliance is asserted in a single marketing sentence, with no national transposition or deadline features named
- Nothing on 7-day acknowledgment or 3-month feedback clocks, conflict-of-interest exclusion, or per-case retention and deletion
- No engineered anonymous voice, hotline or QR intake — the multichannel fact is the operator manually creating cases from letters, emails and calls
- No published DPA, subprocessor list or pentest summaries, and daily backups sit in 'geographically distributed' data centres of unstated country
- Nothing evidences per-entity channels, separated entity case access or group-level oversight for multi-subsidiary groups
Best for
- You need a first-class anonymous two-way dialog for a multilingual workforce, with 80+ languages and integrated machine translation
- You can run statutory deadline and retention discipline in-house and want solid casework bones: need-to-know roles, dual control, per-activity revision logs
- You are a single legal entity that values attested security (ISO 27001, PwC ISAE 3000) and hosting exclusively in Germany
Avoid if
- You need built-in 7-day/3-month deadline tracking, per-case retention automation and conflict-of-interest exclusion rather than manual discipline
- You are a corporate group needing per-entity channels, separated entity case stores and consolidated oversight
- You require a published DPA and subprocessor list, or are constrained by US PE ownership (Thoma Bravo, 2024)
- You need reporter-facing voice or hotline intake beyond the anonymous web dialog
The scores
Reporting channels & reporter experience
Show reasoningHide reasoning
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.
The Compliance Officer
Anonymous two-way dialog is first-class ("complete anonymity... anonymous dialogue between the whistleblower, case handler and external experts", no tracking mechanisms), with 80+ languages, integrated machine translation, browser auto-detect and mobile optimization — but voice/hotline or QR intake is never evidenced as an engineered anonymous channel; the "telephone call" in the multichannel fact is a handler manually creating a case, not reporter voice intake, and WCAG only at bronze. 1 2 3 4
The Reporter's Advocate
Anonymous two-way dialog is claimed as first-class — whistleblower, case handler and external experts — with 80+ languages, browser auto-detect, in-system machine translation, mobile optimization, WCAG bronze and a written no-tracking statement. But the only 'telephone' channel is the caseworker creating a case from a call or letter; there is no evidenced reporter-facing hotline, voice intake or QR entry, and nothing promises the reporter needs no account or app install. Dialog and languages nearly reach 8; the night-shift phone channel and the identity-out-of-the-channel documentation are missing. 1 2 3 4
The SME Operator
Anonymous two-way dialog is first-class with no tracking mechanisms, 80+ languages with integrated machine translation, mobile-optimized and WCAG bronze — that earns most of the 8 anchor. But there is no reporter-facing voice, hotline or QR channel evidenced: the multichannel fact is my caseworker creating a case from a letter or phone call, not a frightened employee calling in. 1 2 3 4
The Group Counsel
Anonymous two-way dialog that can even include external experts, 80+ languages with integrated machine translation and browser auto-detect, mobile-optimized, WCAG bronze, and an explicit no-tracking statement make the anonymous dialog first-class. But the 'multichannel' quote is about the caseworker manually creating a case from a letter, email or phone call — no anonymous voice or hotline intake by the product itself is evidenced, which a dozen-country rollout would need. 1 2 3 4
The Security Auditor
Anonymous two-way dialog is first-class with an explicit no-tracking statement, 80+ languages with auto-detect and integrated machine translation, and mobile optimization; but WCAG 'bronze' is the floor of accessibility and phone/letter intake is just the operator transcribing offline inputs into cases, not engineered anonymous voice intake. 1 2 3 4
The Skeptic
Anonymous two-way dialogue is first-class with 80+ languages, browser auto-detect, integrated machine translation and mobile optimization, and 'no tracking mechanisms' is at least stated. Docked below 8: the non-web channels in are cases created by the operator from a letter/phone call/meeting, not engineered anonymous reporter channels, and 'WCAG bronze level certification' is not a WCAG conformance level anyone audits to. 1 2 3 4
Case management & deadline discipline
Show reasoningHide reasoning
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.
The Compliance Officer
Integrated case management with a per-activity revision log, granular need-to-know permissions, configurable dual control and partial case anonymisation is a real permission model — but the evidence is entirely silent on the statutory clocks: no 7-day acknowledgment automation, no 3-month feedback deadline, no conflict-of-interest exclusion of implicated handlers, no per-case retention or deletion rules. The deadlines would be my problem again, and dashboards don't fix that. 2 3 4
The Reporter's Advocate
Integrated case management with a per-activity revision log, granular need-to-know rights, configurable dual control, partial case anonymisation and real-time dashboards — permissions and audit trail sit above rubric level 5. But the evidence is silent on the statutory clocks: no 7-day acknowledgment or 3-month feedback tracking, no retention/deletion per case, no conflict-of-interest exclusion — nothing on this page forces anyone to ever answer the reporter. 3 4
The SME Operator
Integrated case management with a per-activity revision log, granular need-to-know rights with dual control, partial case anonymisation and dashboards are solid bones. But the evidence is silent on the two things I'm legally on the hook for — automated 7-day/3-month deadline clocks and per-case retention/deletion — and on excluding implicated handlers, so the statutory discipline is my problem, not the product's. 3 4
The Group Counsel
Integrated case management with a per-activity revision log, granular need-to-know roles, configurable dual control, partial case anonymisation and dashboards is real. But the evidence is dead silent on statutory deadline tracking, conflict-of-interest exclusion and per-case retention/deletion — the anchor-5 requirement — and I do not buy deadline discipline on faith for 25 entities. 1 3 4
The Security Auditor
Granular need-to-know authorization with configurable dual control, per-case/per-activity revision logs, case anonymisation and live dashboards beat rubric level 5's basic role separation — but the evidence is dead silent on statutory deadline clocks, conflict-of-interest exclusion, tamper-evidence and retention automation. 1 3 4
The Skeptic
Granular need-to-know roles, configurable dual control, per-activity revision log and real-time dashboards are evidenced, exceeding basic role separation. But the evidence is entirely silent on the statutory 7-day/3-month clocks, conflict-of-interest exclusion and per-case retention/deletion — the 'deadline discipline' half of this criterion has zero supporting evidence. 2 3 4
Legal compliance alignment
Show reasoningHide reasoning
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.
The Compliance Officer
The EU Whistleblowing Directive appears exactly once, as a marketing assertion that the hotline "ensures that your organisation fully complies" — no national transposition (HinSchG or otherwise), no deadline or documentation duties implemented as features, no retention periods, no named counsel or legal review. The mapping is the customer's problem. 4
The Reporter's Advocate
The only legal facts are marketing sentences that the hotline 'fully complies' with the EU Whistleblowing Directive and GDPR. No feature mapping, no national transposition such as HinSchG, no legal templates or named counsel, and the deadline duties appear nowhere as product behaviour — the directive is invoked, the implementation is the customer's problem. That is rubric level 3 exactly. 1 4
The SME Operator
One marketing sentence claims full EU Whistleblowing Directive compliance with no mapping to actual duties: no national transposition (HinSchG et al.) named, no acknowledgment/feedback clock features, no documentation or retention rules in the product, no counsel review. That's the 3 anchor verbatim — the directive is invoked, the obligations stay mine. 4
The Group Counsel
The directive appears once, as a marketing claim that the hotline 'fully complies' with it; no national transposition, no per-country rule set, no named counsel, no acknowledgment or feedback clocks as product features. Deadlines, documentation and retention are evidently the customer's problem — that is the anchor-3 definition verbatim. 4
The Security Auditor
The directive appears exactly once, as a marketing adjective ('fully complies with... the EU Whistleblowing Directive (GDPR compliant)') with no feature mapping, no national transposition like HinSchG, no named counsel and no templates — the textbook anchor-3 invocation. 4
The Skeptic
The directive appears in exactly one marketing sentence — 'fully complies with... the EU Whistleblowing Directive (GDPR compliant)' — with no national transposition named, no deadline/documentation/deletion features, no legal templates and no named counsel. Directive invoked, mapping vague, statutory duties left to the customer: rubric level 3 verbatim. 4
Security & anonymity assurance
Show reasoningHide reasoning
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".
The Compliance Officer
Strong on attestations: ISO 27001 with stated scope ("EQS Group and our data centres"), PwC ISAE 3000 Type I and II, CSA STAR Registry, OWASP threat analysis, 2FA as standard. It falls short of the top anchors because the "EQS Group can at no time access your data" claim is asserted rather than documented — no published pentest summaries, no cryptographic architecture, and "no tracking mechanisms" is the only metadata statement we get. 2 3 4
The Reporter's Advocate
ISO 27001 for EQS Group and its data centres, a PwC ISAE 3000 Type I & II audit, STAR Registry, OWASP threat analysis, WAF, 2FA as standard, and a written claim that EQS Group 'can at no time access' report data plus no user tracking. Held below 8: no published penetration test reports, no documented encryption architecture, no metadata/IP-logging detail and no disclosure policy to back the we-cannot-unmask promise — I have the vendor's word, not its homework. 3 4
The SME Operator
ISO 27001 covering both EQS Group and the data centres, a PwC ISAE 3000 Type I and II audit, CSA STAR registration and OWASP-based threat analysis, plus 2FA as standard and a vendor-cannot-access encryption claim — that is audited assurance, not adjectives. It stops short of 8 because there are no public pentest summaries, no explicit IP-logging statement (only a generic no-tracking claim) and no published security contact or disclosure policy. 2 3 4
The Group Counsel
ISO 27001 covering EQS Group and its data centres, a PwC ISAE 3000 Type I+II audit, STAR Registry, 2FA as standard, OWASP threat analysis and a stated absence of tracking mechanisms, plus the vendor's claim it can at no time access report data. What keeps it off the 8 anchor: no named penetration-test attestations, no security contact or disclosure policy, and 'latest encryption algorithms and SSL certificates' is adjective-grade, not a documented architecture. 2 3 4
The Security Auditor
PwC's ISAE 3000 Type I/II attestation and ISO 27001 covering 'EQS Group and our data centres' are real artifacts, but there are no certificate dates, no published pentest reports behind the bare 'regular external security audits', no cryptographic architecture behind the 'latest encryption algorithms' claim, no explicit no-IP-logging statement, and no security contact or disclosure policy. 3 4
The Skeptic
ISO 27001 for 'EQS Group and our data centres', ISAE 3000 Type I and II by PwC, CSA STAR and regular external audits are real attestations, not adjectives. But the claim that EQS 'can at no time access your or your whistleblowers' data' is justified by 'SSL certificates' — transport security is not a documented end-to-end architecture — and there is no published pentest, no security contact/disclosure policy, and 'no tracking' is the only metadata statement. 1 3 4
Group & multi-entity capability
Show reasoningHide reasoning
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.
The Compliance Officer
Corporate branding and granular per-case access are evidenced, and external experts can join the anonymous dialogue — but there is not a single fact on per-entity channels, separated entity case stores, group-level consolidated oversight, delegated administration, or per-entity legal rules. Whether one contract can serve a corporate group is simply unanswered. 3 4
The Reporter's Advocate
Nothing evidences per-entity channels, separated entity case access, a consolidated group view or ombudsman roles; the only group-adjacent facts are single-instance branding, granular user rights and external experts joining the dialog. Not even 'multiple channels under one account' is on the page, so a corporate group cannot be scoped from this sheet. 3 4
The SME Operator
The evidence is entirely silent on multi-entity structure — no per-entity channels, no entity-separated case access, no group overview. What exists are building blocks: custom branding, granular user rights and external experts in the anonymous dialog, which is not the same as per-subsidiary separation or ombudsman roles. 2 3 4
The Group Counsel
Granular need-to-know authorization, per-user rights and an anonymous dialog that includes external experts are hints of what I need, but nothing evidences per-entity channels, delegated administration, group reporting that respects entity boundaries, or ombudsman roles. The evidence shows me one channel with custom branding — and I reject one-channel products multiplied by twenty-five contracts. 1 3 4
The Security Auditor
Granular case access and an anonymous dialog that includes external experts get partway to rubric level 5, and branding is customisable — but nothing evidences per-entity channels, group-level oversight, delegated administration or per-subsidiary white-labeling; the evidence speaks of 'your company', singular. 1 3 4
The Skeptic
The evidence says nothing about per-entity channels, separated entity case access, group-level overview, delegated administration or ombudsman roles; only single-instance branding, generic granular permissions and 'external experts' joining a dialogue gesture at group use. '2,500 customers' is a count, not a multi-tenant architecture. 2 3 4
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
The Compliance Officer
German legal entity (EQS Group GmbH, Munich) and hosting "exclusively in Germany" with a named Munich East data centre are anchor-grade facts on where reports live — but the registry contains no DPA, no subprocessor list and no TOMs at all, and the vendor has been owned by US PE firm Thoma Bravo since 2024. For the most sensitive data a company holds, the chain past the first data centre is undocumented, so I cannot go higher. 3 4 5
The Reporter's Advocate
Exclusive German hosting, a named Munich East data centre and a German vendor entity are solid anchor-8 material. But no DPA and no subprocessor list appear on any captured page, the vendor now sits under US private-equity ownership (Thoma Bravo), and 'geographically distributed' backup data centres leave open where copies of my report sleep — that pulls it back down. 3 4 5
The SME Operator
Hosting is exclusively in Germany with a named data centre (Munich East) under a Munich-based GmbH — the core of the 8 anchor's facts. But nothing here shows a published DPA or subprocessor list, backups go to 'geographically distributed' centres of unstated location, and the vendor sits under US PE ownership (Thoma Bravo) — the chain is undocumented, which caps it at 5. 3 4 5
The Group Counsel
A German GmbH with exclusive German hosting and a named Munich East data centre is a genuine sovereignty signal. But the chain is undocumented: no DPA, no subprocessor list, backups only 'geographically distributed', and the machine-translation service that touches case content has no jurisdiction stated — all under US PE ownership per the evidence's own provenance note. 3 4 5
The Security Auditor
Germany-exclusive hosting with a named Munich East data centre and a German legal entity are concrete; but for the most sensitive data a company holds, the evidence publishes no DPA, no subprocessor list and no TOMs, and Thoma Bravo's 2024 take-private puts the vendor inside US jurisdictional reach. 3 4 5
The Skeptic
German legal entity, hosting 'exclusively in Germany' and a named Munich East data centre are genuine strengths. But no published DPA or subprocessor list appears anywhere in the evidence, ownership sits with US PE firm Thoma Bravo per provenance, and daily backups are stored 'for several years in geographically distributed data centres' with no country named — the most sensitive data exits the documented chain precisely where scrutiny matters. 3 4 5
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
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.
The Compliance Officer
The only pricing fact in the entire registry is a "Start free trial" button — no tier prices, no employee bands, no entity rules, no VAT treatment, no setup fees. I could not begin to compute the invoice for a 600-employee company from these pages. 1
The Reporter's Advocate
Across five captured pages the only pricing fact is a 'Start free trial' button — no tier, employee band, entity rule or setup fee is public anywhere. An obligated company cannot compute anything from this sheet; rubric level 0 with a trial-button courtesy. 1
The SME Operator
The only pricing-related fact in the entire sheet is 'Start free trial' — no tiers, no numbers, no employee bands, no VAT treatment, no setup-fee disclosure. I cannot compute my invoice from these pages, and everything above entry implies a sales conversation, which is precisely what my year-end review will question. 1
The Group Counsel
Across five captured pages the only pricing fact is a 'Start free trial' button; no tier, employee band, entity rule or setup fee appears anywhere. An obligated company — much less a 25-entity group — cannot compute any invoice from public pages, which is the anchor-0 definition. 1
The Security Auditor
Across five captured pages the only pricing artifact is a 'Start free trial' button — not one number, tier, employee band or setup fee; that is anchor-0 territory, softened by one point for the trial existing. 1
The Skeptic
Not one price appears on any captured page: no tiers, no employee bands, no VAT treatment, no setup fees — only a 'Start free trial' button. Per the anchors, every tier being a sales conversation is a zero. 1
European sovereignty — proven facts
1 of 4 dimensions provenBuilt 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 1 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 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. This is homepage marketing copy; the security page names only the Munich East data centre, and backups are described as lying in unspecified "geographically distributed data centres", so non-German backup locations cannot be ruled out.
- 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.
- 14 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
- 11 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
- 3 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
- 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
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product homepage www.integrityline.com Checked 15 Sep 2026 Details →
- 2 Product page www.integrityline.com Checked 15 Sep 2026 Details →
- 3 Features page www.integrityline.com Checked 15 Sep 2026 Details →
- 4 Security/trust page www.integrityline.com Checked 15 Sep 2026 Details →
- 5 About EQS page www.integrityline.com Checked 15 Sep 2026 Details →
- 6 Reporting channels & reporter experience — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →
- 7 Reporting channels & reporter experience — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →
- 8 Legal compliance alignment — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →
- 9 Security & anonymity assurance — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →
- 10 Security & anonymity assurance — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →
- 11 Group & multi-entity capability — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →
- 12 Group & multi-entity capability — found from sitemap www.integrityline.com Checked 1 Oct 2026 Details →