Whistleblowing Portals
SpeakUp
EU-Made 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 SpeakUp B.V. · www.speakup.com
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
SpeakUp, a whistleblowing platform from Dutch vendor People InTouch B.V., is strongest on reporting channels, scoring 7-8: intake spans phone, voicemail, web browser and the SpeakUp app, with anonymous two-way follow-up backed by a published 49% average check-back rate, 100+ languages, and a platform statement that no IP addresses, device fingerprints or identifying metadata are collected. Security assurance follows at 6-7, resting on ISO 27001 and 27701 certification with quarterly ISAE 3000 Type II plus SOC 2 and TISAX audits, though we found no public information on penetration tests or end-to-end encryption architecture. Outside pricing, the weakest scores are multi-entity scale and compliance alignment at 4-5, with sovereignty at a uniform 4: the Dutch contracting entity is fully documented, but the EEA no-transfer statement covers only the marketing website, we found no public information on product-data hosting, subprocessors or a DPA, and a US sister entity sits alongside the Dutch core. Case management at 6-7 pairs triage-to-closure discipline with only generic statutory-deadline handling. Scores span at most one point per criterion; no genuine split emerged. Pricing is by customized quote.
Speaks for it
- Intake spans phone, voicemail, web browser and the SpeakUp app, with anonymous two-way follow-up backed by a published 49% average check-back rate
- The platform states it collects no IP addresses, device fingerprints or identifying metadata, the concrete claim behind its anonymity guarantee
- ISO 27001 and 27701 certification plus quarterly ISAE 3000 Type II, SOC 2 and TISAX audits provide a recurring third-party assurance cadence
- Case management runs from structured triage to closure with an audit-ready trail, custom roles and remediation tasks carrying owners and deadlines
- Language support covers 100+ languages, with machine and human translation plus transcription in over 75
Held against it
- We found no public information on product-data hosting, product subprocessors or a published DPA, because the EEA no-transfer statement expressly covers only the marketing website
- Statutory deadline handling appears only as generic obligations, with no public information on automated acknowledgment and feedback clocks or exclusion of implicated case handlers
- Multi-country support is asserted with named enterprise customers, but we found no public information on per-entity channels, delegated administration or external ombudsman roles
- We found no public information on penetration tests, end-to-end encryption architecture, or a security contact and disclosure policy
Best for
- You need anonymous, multilingual intake across phone, voicemail, web and app, with two-way follow-up that reporters actually use
- You want a recurring third-party assurance rhythm — quarterly ISAE 3000 Type II, SOC 2 and TISAX audits on top of ISO 27001 and 27701 — to show your auditors
- Your compliance team needs structured triage-to-closure case management with an audit-ready trail and dashboards exportable for regulators
Avoid if
- You are rolling a reporting channel out across many legal entities and need per-entity channels with separated case access documented before signing
- Your obligations hinge on the Directive's acknowledgment timelines and follow-up requirements, and you need automated clocks and conflict-of-interest exclusion documented up front
- Your procurement requires the SpeakUp system's data-processing terms in hand before contracting, since the privacy statement refers product-data processing to a separate document
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
Reports can come in by phone, voicemail, web browser or the SpeakUp app, with multi-device intake, and the anonymous two-way follow-up dialog looks first-class rather than bolted on — a published 49% average check-back rate is operational proof people actually use the dialog. Translation support spans 100+ languages with machine and human translation plus transcription. I found no public information on accessibility standards, QR entry points, or how anonymity is preserved through the voice channels, so I stay just below the top marks. 7 13 8
The Reporter's Advocate
Intake meets the frightened reporter where they are: phone, voicemail, web and app channels, multi-device, anonymous two-way follow-up, and a plain statement that the platform collects no IP addresses, device fingerprints or identifying metadata — identity documented as kept out of the channel itself. Language coverage runs broad with human and machine translation plus transcription, though the captured pages give different figures for supported languages. We found no public information on WCAG accessibility or whether every channel is anonymous-capable, so I stop below the top. 1 7 13
The SME Operator
Phone, voicemail, web and app intake with 100+ languages, professional translation and an anonymous two-way follow-up is more channel than my staff will ever need, and the statement that no IP addresses, fingerprints or identifying metadata are collected makes anonymity look engineered rather than decorative. I found no public information on accessibility standards for the intake or on how anonymity holds on the phone channel, which keeps it below the top band. 7 13
The Group Counsel
Intake spans phone, voicemail, browser and app with 100+ languages backed by machine and human translation and transcription, and anonymous two-way follow-up is first-class — a 49% check-back rate says reporters actually come back to the dialog. An explicit statement that the platform collects no IP addresses, device fingerprints or identifying metadata underpins the 100% anonymity guarantee. I found no public information on WCAG accessibility or per-channel anonymity engineering, which is what the top band demands. 7 13
The Security Auditor
Intake is documented across phone, voicemail, web browser and a mobile app, with 100+ languages plus machine and professional human translation and transcription, multi-device access, and an anonymous two-way follow-up dialog evidenced by a published 49% check-back rate. The platform states it collects no IP addresses, device fingerprints or identifying metadata, which is a concrete claim about the intake path. We found no public information on QR entry points, accessibility-standard conformance, or documentation of how reporter identity is kept out of the channels themselves. 7 8 13
The Skeptic
Reports can arrive by phone, voicemail, web browser or the SpeakUp app, with anonymous two-way follow-up the vendor says drives a 49% check-back rate, and the explicit statement that the platform collects no IP addresses, device fingerprints or identifying metadata is exactly the engineering detail an anonymity claim needs. Language coverage is stated as 100+ languages with human and machine translation in over 75. I found no public information on accessibility commitments such as WCAG, on QR entry points, or on whether the phone channel itself is anonymous-capable. 7 8 13
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
This is a real case environment — structured triage, investigation planning with logs, interviews and findings, custom roles for handler separation, remediation tasks with owners and deadlines, automatic audit logs, and dashboards with exports for regulators. But the statutory clocks are named only generically as acknowledgment timelines and follow-up requirements, and I found no public information on automated reminders for the 7-day and 3-month deadlines, conflict-of-interest exclusion of implicated handlers, or tamper-evidence of the case history — the exact points I answer for. 7 13
The Reporter's Advocate
Reports flow into a structured triage-to-closure environment with custom roles, an audit-ready trail from report to closure, remediation tasks carrying owners and deadlines, and dashboards exportable for regulators — real discipline, not a spreadsheet next door. But we found no public information on automated statutory clocks for the acknowledgment and feedback duties, nor on excluding case handlers who are themselves implicated in a report. 7 13
The SME Operator
Structured triage, custom roles, an audit-ready trail from report to closure, remediation tasks with owners and deadlines, and dashboards that export for regulators — the paperwork side is genuinely handled by the product. But statutory deadlines appear only as a generic reference to "acknowledgment timelines, follow-up requirements", and I found no public information on automated seven-day and three-month clocks or on excluding implicated case handlers, so deadline discipline would rest on my discipline. 7 8 13
The Group Counsel
Cases flow into a structured environment with triage, investigation documentation, custom workflows, custom role-based access and an audit-ready trail from report to closure, plus dashboards and exports for regulators — that clears the working bar. But statutory deadline handling is referenced only generically, and I found no public information on automated acknowledgment and feedback clocks, exclusion of implicated case handlers for conflict of interest, or per-case retention and deletion rules, which is exactly what a dozen subsidiaries need to stay out of trouble. 4 7 13
The Security Auditor
Structured triage with investigation planning, logs, interviews and findings is evidenced, alongside custom roles, remediation tasks carrying owners and deadlines, custom team workflows, an audit-ready trail from report to closure, and dashboards exportable for regulators. The acknowledgment-timeline and follow-up language is phrased as what such software must support rather than a documented automated clock. We found no public information on automated statutory deadlines, conflict-of-interest exclusion of implicated handlers, tamper-evidence of the case record, or per-case retention and deletion automation. 7 13
The Skeptic
The case worker's side looks real: structured triage-to-closure case management, an audit-ready trail, attachments, custom roles rather than all-or-nothing permissions, remediation tasks carrying owners and deadlines, investigation planning with logs and interviews, and dashboards exportable for regulators. But the statutory clocks appear only as a general remark that such software must support acknowledgment timelines and follow-up requirements — I found no public information on automated seven-day and three-month deadline handling, exclusion of implicated case handlers, or tamper-evidence for the case record. 7 13
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 Whistleblower Directive is supported, the 50-employee scope is stated correctly, and acknowledgment timelines, follow-up requirements and national whistleblower protection laws are named as obligations the software addresses, with German supply-chain law, GDPR, NIS2 and DORA also cited. I found no public information on per-country transposition rule sets, legal templates, or documented review by named counsel, so the legal mapping I could hand a regulator is not in the captured pages. 7 13
The Reporter's Advocate
The Directive is named together with its 50-employee duty, acknowledgment timelines and follow-up requirements are invoked as obligations the software must support, and retention and localization duties are claimed met alongside the German Supply Chain Act, GDPR, NIS2 and DORA. The mapping stays at that level: we found no public information on national transposition details, legal templates, named counsel or documented legal review. 7 13
The SME Operator
The EU Whistleblower Directive, German Supply Chain Act, GDPR, NIS2 and DORA are all named, with dedicated directive pages in English and German and claims that retention and localization duties are met. The mapping stays at the regulation-name level though: I found no public information on per-country rule sets, legal templates, or guidance maintained by named counsel, which is the homework I wanted shown in public. 7 11 12 13
The Group Counsel
The Directive's duties are named concretely — the 50-employee scope, acknowledgment timelines, follow-up requirements — alongside GDPR, retention and localization commitments and a German supply-chain law among supported regulations, which is more than label-wearing. The mapping stays at that level though: I found no public information on per-country rule sets for national transpositions, legal templates or review by named counsel, or guidance for group-wide channels and external ombudsman setups, the exact items my roll-out would hinge on. 7 13
The Security Auditor
The EU Whistleblower Directive is cited with the correct 50-employee obligation, and the vendor lists the Directive, the German Supply Chain Act, GDPR, NIS2 and DORA among supported regulations, with retention and localization duties claimed as fulfilled. The mapping stays at category level, and we found no public information on specific national transpositions such as the German whistleblowing act, legal templates, process guidance maintained by named counsel, or documented updates when a law changes. 7 13
The Skeptic
The EU Directive, German Supply Chain Act, GDPR, NIS2 and DORA are all invoked, and the pages correctly note the Directive bites from 50 employees, but the mapping stays at the level of "we help you comply", with deadlines and follow-up duties named only as generic obligations such software must support. I found no public information on national transposition specifics, legal templates, named counsel, or any commitment to update the product when a law moves. 7 13
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
Quarterly ISAE 3000 Type II, SOC 2 and TISAX audits on top of ISO 27001 and 27701 certification is a recurring assurance rhythm I can put in front of an auditor, and the explicit statement that the platform collects no IP addresses, device fingerprints or identifying metadata is the right kind of specificity. What holds it back is that I found no public information on penetration tests, on an encryption architecture beyond highest-standards language, or on a security contact and disclosure policy. 7 13
The Reporter's Advocate
A heavyweight, recurring assurance stack — ISO 27001 and 27701 certification with quarterly ISAE 3000 Type II, SOC2 and TISAX audits — plus the sentence I weigh most: no IP addresses, no device fingerprints, no identifying metadata. Encryption in transit and at rest is asserted without technical architecture behind it, and we found no public information on published penetration-test reports, a security contact or a disclosure policy. 7 13
The SME Operator
ISO 27001 and 27701 for the organisation plus quarterly ISAE 3000 Type II, SOC2 and TISAX audits of the platform is the strongest third-party cadence I have seen, and the explicit no-IP, no-fingerprint, no-metadata statement covers the anonymity promise. It falls short of the top band because I found no public information on documented end-to-end encryption architecture, published penetration test summaries, or a security contact and disclosure policy. 7 13
The Group Counsel
The assurance stack is strong and recurring — ISO 27001 and 27701 with quarterly ISAE 3000 Type II audits alongside SOC2 and TISAX, encryption at rest and in transit, MFA and SSO — and the anonymity engineering goes beyond adjectives with an explicit no-IP, no-device-fingerprint, no-identifying-metadata statement. I found no public information on penetration-test attestations, documented end-to-end encryption architecture, or a published security contact and disclosure policy, which keeps it shy of the top band. 7 13
The Security Auditor
Certification is claimed for ISO 27001 and ISO 27701 with quarterly ISAE 3000 Type II audits plus SOC 2 and TISAX, and the platform states it collects no IP addresses, device fingerprints or identifying metadata — that is a minimization statement I can actually work with. Encryption is asserted at rest and in transit, but "highest encryption standards" and "100% anonymity guaranteed" are adjectives, not architecture. We found no public information on penetration tests, the visible scope of the certificates, end-to-end encryption of report content, or a published security contact and disclosure policy, so the question of whether the operator could unmask a reporter goes unanswered in public. 7 13
The Skeptic
The claims are unusually specific for this market — ISO 27001 and 27701, quarterly ISAE 3000 Type II plus SOC 2 and TISAX audits, MFA and SSO — and the explicit no-IP, no-fingerprint, no-identifying-metadata statement is the metadata minimization I hunt for. My discount: the captured pages assert certificates without showing them, describe encryption only as "highest standards" at rest and in transit, and I found no public information on an end-to-end encryption architecture, penetration test reports, or a security contact and disclosure policy. "100% Anonymität garantiert" is a slogan; the metadata statement is the part a buyer can hold them to. 7 13
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
Support for organizations with entities in multiple countries and a customer base including Nestlé, Daimler Truck, Electrolux and Swarovski suggest group fitness, with dashboards showing trends across locations and custom roles enabling some access separation. But I found no public information on per-entity channels, delegated administration, external ombudsman or counsel access, or per-entity branding — the structures a corporate group would actually rely on are not evidenced. 4 7 13
The Reporter's Advocate
The vendor says it is suited to organizations with entities in multiple countries and shows global enterprise customers with custom team workflows and dashboards cutting across locations. But that is fit, not architecture: we found no public information on channels separated per legal entity, per-entity branding, delegated administration or external ombudsman access. 4 7 13
The SME Operator
Multi-country entities are explicitly supported, custom roles and per-team workflows let case handlers be separated, and dashboards roll up across locations for the global customers they name. I found no public information on per-entity branding, delegated administration or external ombudsman access, so the group structure is asserted rather than documented — as a single-entity firm I only care about that at renewal time. 4 7 13
The Group Counsel
There is group-level evidence: suitability for organizations with entities in multiple countries is affirmed, dashboards trend across locations, teams and custom roles structure access, and global enterprises like Nestlé and Daimler Truck are named customers. But I found no public information on separate channels per legal entity with hard access separation, delegated administration, external ombudsman roles, or group reporting that respects entity boundaries — so a 25-subsidiary roll-out would rest on customer logos rather than demonstrated entity architecture. 4 7 13
The Security Auditor
The vendor states it is suited to organizations with entities in multiple countries, and dashboards show trends across locations with custom roles, custom team workflows and a multinational customer list. We found no public information on per-entity channels with separated case access, delegated administration, external ombudsman or counsel roles, or per-entity branding and white-label reporting pages. 4 7 13
The Skeptic
Multi-country entities are claimed as supported and enterprise logos are everywhere, with analytics across locations, configurable teams and custom workflows — but the captured pages stop at "perfectly suited for international companies". I found no public information on per-entity channels, per-entity case-access separation, per-entity branding, delegated administration, or external ombudsman and counsel roles. 4 7
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
The European contracting entity is the Dutch People InTouch B.V. with full registry details, and the privacy statement commits to no transfers outside the EEA — but that statement expressly covers only the marketing website, and the document governing the SpeakUp product's own data processing was not in the captures. I found no public information on a published DPA, a subprocessor list for the product, or named data centers, and a New York sister entity plus Bengaluru and New York offices sit alongside the Dutch core. 5 3 6
The Reporter's Advocate
The European contracting party is a Dutch company with registration, tax and VAT details published, though the captured pages also list a New York entity and office within the group. The only no-transfer statement we found sits in a privacy statement that expressly covers the marketing website alone and points to a separate document for the SpeakUp system's data processing — so we found no public information confirming where report data itself is hosted, nor a published DPA or subprocessor list. 3 5 6
The SME Operator
The contracting entity is Dutch with a stated GDPR commitment and an EEA-only transfer statement, and the pages claim data localization requirements are met. But that transfer statement covers only the marketing website, and I found no public information on where the whistleblowing system's reports are hosted, on a public DPA, or on any subprocessor list — for the most sensitive data a company holds, that is thin. 3 5 13
The Group Counsel
The contracting entity is the Dutch People InTouch B.V. with an EEA-no-transfer statement and GDPR posture, and the one US tracking tool is explicitly limited to US visitors, so the default direction is European. But the privacy statement expressly covers only the marketing website and refers product-data processing to a separate document, and I found no public information on a published DPA, a product subprocessor list, or named data centers for report content — while a US sibling entity and New York office sit alongside the Dutch company. 3 5 6
The Security Auditor
The European contracting entity is the Dutch People InTouch B.V. at an Amsterdam address, and the privacy statement says personal data is not transferred to processors outside the EEA — but that statement expressly covers only the marketing website, with the product's data processing documented separately. We found no public information on where the product's report data is hosted, on product subprocessors, on named data centers, or on a published data processing agreement and technical measures. A US sibling entity (SpeakUp US, Inc., New York) and offices in New York and Bengaluru sit alongside the Dutch entity. 3 5 9
The Skeptic
The Dutch contracting entity is verifiable down to KvK number, VAT number and an Olympisch Stadion address — the best-documented fact in this file. But the EU-only transfer statement expressly covers only the marketing website, with product data processing referred to a separate document not among the captured pages; I found no public information naming product data centers, product subprocessors, a DPA or TOMs, while a US sister entity and a US-visitor identity-resolution tool tying browsing to a known email address appear on the vendor's own pages. 3 5 6
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
Pricing is explicitly customized on company size and features such as advanced analytics and SSO, and no figures appear on any captured page, so I cannot compute an invoice for a 600-employee company from public information. The only public pricing facts are qualitative — case management is always included in the price and support packages carry no additional costs — which tells me about scope, not cost. 4
The Reporter's Advocate
Every price is a sales conversation: the public pricing page says pricing is customized to company size and features, and no figures are published for any tier. Small credit for stating that the case management system is always included within the price and that support packages carry no hidden fees — but an obligated company cannot compute an invoice from the public pages. 4
The SME Operator
The pricing page carries no numbers at all — "Our pricing is customized based on your company size and the features you need" — and it describes the platform as serving companies from 500 employees to global enterprises, while a solutions page also says small and medium businesses are supported; either way a 60-employee buyer cannot compute any invoice without a sales call. The only comfort is public — case management is always included and support packages carry "no additional costs, no hidden fees" — but that is a promise, not a price. 4
The Group Counsel
The public answer is a sales conversation: "Our pricing is customized based on your company size and the features you need, such as advanced analytics or SSO," aimed at companies from 500 employees to global enterprises, with no tier, band, entity or setup figures anywhere in the captured pages. A support package with "no additional costs, no hidden fees" is a fairness promise, not a computable invoice — I cannot price a five-entity group from public information at all. 4
The Security Auditor
Every tier is a customized quote based on company size and features needed, and we found no public price figures for any tier on the captured pricing page. The only disclosed terms are that case management is always included in the price and that support packages carry no additional costs or hidden fees, with the target market stated as 500 employees up to global enterprises — none of which lets an obligated company compute an invoice. 4
The Skeptic
Every price is a sales conversation: the pricing page says quotes are customized on company size and features such as SSO, and the stated audience starts at 500 employees — so an obligated 60-employee company cannot even establish it is in scope, let alone compute an invoice. "No hidden fees" and "case management always included in that price" are promises about a price nobody is shown; we found no public figures at all. 4
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 | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | EU only ⚠ unverified | 2/2 pts | 5 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 — Legal entity, Data residency. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Subprocessors. No subprocessors are named, the statement covers website personal data rather than the SpeakUp product whose data processing is documented separately, and the US tool RB2B (Retention.com) only processes US website visitors, being marketing tooling rather than a product subprocessor.
- 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.
- 55 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
- 11 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
- 4 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 pricing 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 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
- 2 hosting 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 integrations 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.speakup.com Checked 5 Oct 2026 +1 earlier capture: 23 Aug 2026 Details →
- 2 About page www.speakup.com Checked 5 Oct 2026 Details →
- 3 Company / legal information www.speakup.com Checked 5 Oct 2026 Details →
- 4 Pricing page www.speakup.com Checked 5 Oct 2026 Details →
- 5 Privacy policy www.speakup.com Checked 5 Oct 2026 Details →
- 6 Imprint www.speakup.com Checked 5 Oct 2026 Details →
- 7 Reporting channels & reporter experience — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →
- 8 Reporting channels & reporter experience — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →
- 9 Case management & deadline discipline — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →
- 10 Case management & deadline discipline — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →
- 11 Legal compliance alignment — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →
- 12 Legal compliance alignment — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →
- 13 Security & anonymity assurance — found from sitemap www.speakup.com Checked 5 Oct 2026 Details →