FaceUp
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by FaceUp Technology s.r.o. · www.faceup.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
FaceUp at a glance
- Vendor
- FaceUp Technology s.r.o.
- Headquarters
- Incorporated in Czechia source, captured 16 Nov 2026
- Data hosting
- Default not stated; pages mention the EU, the United States and Middle East source, captured 16 Sep 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates FaceUp 3/5, the mean of 6 judges. FaceUp is a whistleblowing and ethics reporting platform from Czech vendor FaceUp Technology s.r.o. how scores are made
- As of
- Vendor pages captured 16 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
FaceUp is a whistleblowing and ethics reporting platform from Czech vendor FaceUp Technology s.r.o. Its strongest area is reporting channels at 7 to 9: web forms, automated, AI-powered and live hotlines, surveys and mobile apps in 113 languages with automatic translation, and anonymity engineering documented — a 16-digit case key never sent by email or SMS, no IP logging and Tor support. Security assurance sits at 7 to 8 on end-to-end encryption with device-held keys and stated ISO 27001 and SOC 2 certifications. The weak spots are compliance alignment and sovereignty, both flat at 4: the EU Whistleblowing Directive is explained, but we found no public information mapping the seven-day acknowledgement or three-month feedback deadlines to features, and while the EU is one of four selectable AWS regions with no default stated, hotline services are processed in the United States through Vonage, AnswerNet and OpenAI regardless of the chosen region. Case management and multi-entity scale sit at 6 to 7. No prices are public. Scores cluster tightly on every criterion; no meaningful disagreement was flagged.
Speaks for it
- Reporting channels score 7 to 9 on breadth — web forms, three hotline types, surveys and mobile apps in 113 languages with automatic translation
- Anonymity is engineered and documented — the 16-digit case key is never sent by email or SMS, IP addresses are not logged, attachment metadata is stripped and Tor is supported
- Case activity is logged in a tamper-proof record whose entries cannot be altered or deleted even by investigators, and it exports for legal review
- End-to-end encryption keeps keys on the user's device, with a unique recovery key per member
- Group basics are covered — separate forms per entity, entity-specific routing and access permissions, and 113 languages on every plan
Held against it
- Compliance alignment is flat at 4 — we found no public information mapping the seven-day acknowledgement or three-month feedback deadlines to product features
- Sovereignty is flat at 4 — the EU is one of four selectable AWS regions with no default stated, and hotline services are processed in the United States through Vonage, AnswerNet and OpenAI regardless of the chosen region
- We found no public information on accessibility or WCAG conformance for reporters
- We found no public information on delegated administration per subsidiary or access for an external ombudsperson
- We found no public information on certificate scopes, penetration-test summaries or a security disclosure policy
Best for
- You need broad anonymous intake — web forms, phone hotlines and mobile apps in 113 languages — with anonymity mechanics you can document to reporters
- You want every case action captured in a tamper-proof log whose entries cannot be altered even by investigators, exportable for legal review
- You run a lean team that builds its own forms, workflows and permissions, with setup stated in hours and no professional services contract
Avoid if
- You must keep spoken reports on a European processing chain — the captured pages state hotline services are processed in the United States through Vonage, AnswerNet and OpenAI, regardless of the chosen region
- You expect EU residency by default — ask the vendor: the public pages we read do not show it
- You need the statutory seven-day acknowledgement and three-month feedback clocks as product behaviour — the documented reminders are generic email nudges before due dates
- You must cite a single scoped SOC 2 certificate in your audit file — the captured pages give different framings for SOC 2, the platform in one place and the AWS infrastructure in another
The scores
| Criterion | Panel median |
|---|---|
| Reporting channels & reporter experience | 4 of 5 |
| Case management & deadline discipline | 3 of 5 |
| Legal compliance alignment | 2 of 5 |
| Security & anonymity assurance | 3.5 of 5 |
| Group & multi-entity capability | 3 of 5 |
| European sovereignty | 2 of 5 |
Reporting channels & reporter experience
Show reasoningHide reasoning
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialogue, phone or voice message, languages, accessibility — and whether anonymity survives first contact.
0 — Not a reporting channel; a general contact or survey form with no anonymous route and no way to reach the reporter afterwards.
3 — A web form that accepts anonymous reports, with a case number or access code the reporter can use to check the report later.
5 — Anonymous two-way dialogue through a protected mailbox or access code, the reporting page in several languages, and use on mobile devices without an app or account.
8 — Several channels (web, voice message or phone hotline, in-person meeting requests, QR or intranet entry points), broad language coverage with translation of messages, accessibility addressed, and voice distortion or another anonymity measure for spoken reports.
10 — Intake engineered around the frightened reporter: every channel usable anonymously, dozens of languages, WCAG conformance stated, no app or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Compliance Officer
Web forms, automated, AI-powered and live hotlines, surveys and mobile reporting give a frightened reporter several doors in, in up to 113 languages with automatic translation of the two-way dialogue. The anonymity engineering is documented in a way I can defend: a 16-digit case key that is never sent by email or SMS, follow-up without an account, no IP logging, stripped attachment metadata, altered voice messages with anonymisation of hotline recordings, and even Tor support — though I found no public information on accessibility or WCAG conformance. 3 14 6 2 8 11
The Reporter's Advocate
This is intake built for the frightened reporter: anonymous two-way chat on a 16-digit case key that is never sent by email or text, follow-up with no account, forms in 113 languages with automatic translation of the dialogue, and web plus automated, AI-powered and live hotlines where voice is anonymised or altered. The pages even document how identity stays out of the channel — IP addresses not logged, attachment metadata stripped, no device ID, no calls to external sites, Tor welcome, anonymous submission settable as the default. We found no public information on accessibility conformance, which is the one thing keeping this off the top rung. 3 14 6 2 9 7 8
The SME Operator
My staff can choose web forms, an automated, AI-powered or live phone hotline, a survey or mobile apps, in 113 languages with automatic translation of the two-way chat, and reporters keep control with a 16-digit case key that is never sent by email or SMS. Voice messages are altered, the AI voice agent anonymizes caller recordings, and the reporting form makes no calls to external sites; we found no public information on accessibility for reporters with disabilities, which is the one gap in an otherwise broad intake. 2 6 8 14 2 3
The Group Counsel
The intake side is genuinely multi-channel — web forms, an automated, AI-powered or live phone hotline, and surveys — with reporting in 113 languages, automatic translation of the encrypted two-way dialogue, and anonymous follow-up through a 16-digit case key that is never sent by email or SMS. Spoken reports get real protection: voice messages are altered and the AI voice agent applies voice anonymization to recordings. We found no public information on accessibility or WCAG conformance, which is what keeps this below the top band. 6 7 8 14 2 3 2
The Security Auditor
Web, mobile apps and three kinds of hotline are documented intake channels in 113 languages with automatic translation of the encrypted two-way dialogue, and the anonymity engineering is unusually well documented: IP addresses are not logged, no device IDs are linked, attachment metadata is stripped, the form makes no external calls, Tor is recommended, the 16-digit case key is never sent by email or SMS, and hotline voice is altered. We found no public information on accessibility conformance, QR or intranet entry points, or in-person meeting requests. 7 8 14 3 2
The Skeptic
Intake is unusually well evidenced: multiple forms, three hotline types, surveys and mobile apps, 113 languages with automatic translation, and — rare in this market — concrete mechanics for keeping identity out of the channel, with the 16-digit case key deliberately not sent by email or SMS, IP addresses not logged, no external scripts on the form, Tor supported, and voice recordings altered. What I found no public information on is accessibility conformance, which keeps this below the top band. 7 8 14 2 3
Case management & deadline discipline
Show reasoningHide reasoning
How this is scored
The case worker's side: triage, the statutory deadlines (7-day acknowledgement, 3-month feedback), roles for case handlers, documentation of each case, and retention and deletion.
0 — No case handling; reports are forwarded by email and handled outside the product.
3 — Reports collected in a case list with status, notes and messages to the reporter.
5 — Reminders or deadline tracking for the 7-day acknowledgement and 3-month feedback, case handlers assigned with roles and permissions, and notes, documents and the full dialogue kept per case.
8 — Statutory deadlines tracked automatically with escalation, conflict-of-interest handling that excludes implicated case handlers, a tamper-evident case history, retention and deletion periods applied per case, and caseload statistics or management reports.
10 — A case system an external investigator can rely on: configurable investigation workflows, a complete audit trail of every access and change, deletion automated to the statutory retention periods with evidence, and statistics prepared for the annual report or the regulator.
The Compliance Officer
Every case holds its reports, messages, attachments and outcomes on one record with owner, status and due date, permissions split between viewing, managing, exporting and deleting, and an immutable, tamper-proof activity log of assignments, field and status changes and closings that exports for legal purposes — documentation that would survive a regulator. What holds the score back: due dates carry email reminders, but I found no public information tying tracking to the seven-day acknowledgement and three-month feedback clocks, or on automatic escalation, exclusion of implicated handlers, or retention periods applied per case. 9 12 9 2 6
The Reporter's Advocate
Cases carry status, owner, due date and the whole dialogue on one record, backed by a tamper-proof log whose entries nobody — including investigators — can alter, custom statuses, priorities and email reminders before due dates, and granular permissions by category or organisational unit. What I cannot find is the statutory clock: no public information on automatic tracking of the 7-day acknowledgement or 3-month feedback, on escalation, or on automatic exclusion of implicated case handlers. Retention is customizable, but per-case statutory deletion is not shown. 9 12 2 6 11
The SME Operator
Every report becomes one case record with status, owner, due date, labels, priorities and full history, email reminders fire before due dates, a closing reason is required, and the activity log is tamper-proof with entries that cannot be altered or deleted even by investigators. Custom statuses, separate permissions for viewing, managing, exporting and deleting, and real-time dashboards round it out; what we found no public information on is automatic tracking of the statutory seven-day acknowledgement and three-month feedback deadlines with escalation. 6 9 10 12 9
The Group Counsel
Every case carries status, owner, due date and full history on one record, with a tamper-proof, immutable activity log whose entries cannot be altered even by investigators and which exports for legal review; access is scoped by category, organizational unit or assignment with separate permissions for viewing, managing, exporting and deleting. What I do not see is the statutory clock: we found no public information tying due-date reminders to the seven-day acknowledgement or three-month feedback, nor on a conflict-of-interest rule excluding an implicated handler from a case. 9 12 9 2
The Security Auditor
Every case keeps reports, messages, attachments and outcomes on one record with status, owner, due date and history; permissions split by organizational unit and by viewing, managing, exporting and deleting; and the activity log is stated tamper-proof, unalterable and exportable for legal review. Due-date reminders are generic email nudges, and we found no public information connecting tracking or escalation to the statutory seven-day acknowledgement and three-month feedback deadlines, or automated per-case deletion to statutory retention periods. 6 9 12 9
The Skeptic
Case handling is documented with real mechanics: owner, status and due date at each step, custom statuses, separate internal comments, and an activity log the vendor states cannot be altered or deleted, exportable for legal review, plus dashboards and retention that can be customised. What I could not find is the statutory layer: no evidence that the 7-day acknowledgement or 3-month feedback deadlines are tracked or escalated, and no exclusion of implicated case handlers — the due dates and reminders described are generic. 9 12 9 2
Legal compliance alignment
Show reasoningHide reasoning
How this is scored
How specifically the product implements EU Directive 2019/1937 and its national transpositions (HinSchG et al.): which statutory duties it maps to features, which countries it names, and how it keeps up when the law changes.
0 — Generic feedback or survey software with no reference to the whistleblowing obligations.
3 — The directive or HinSchG named on the vendor's pages, with the product presented as a way to meet the duty to provide an internal reporting channel.
5 — The statutory duties described as product features for at least one named national law — confidentiality, the acknowledgement and feedback deadlines, documentation of reports, and deletion after the retention period.
8 — Several national transpositions supported with their differing details, templates or process guidance (reporting policy, employee information) provided, and legal review by named counsel or a documented process.
10 — The product is a legal instrument: per-country rule sets kept current with a stated update process, documented legal review, and guidance for edge cases (group-wide channels, external ombudsman set-ups, works council involvement under the BetrVG) published.
The Compliance Officer
The EU Whistleblower Directive is named with who it covers, the transposition deadline and per-country penalties, and the platform lists the directive alongside UK PIDA and California SB 553 as supported regulations — enough to show it is sold for the duty to run an internal channel. But I found no public information naming a national transposition such as the HinSchG, mapping the acknowledgement and feedback deadlines to product features, or offering reporting-policy templates or a documented legal review. 11 1
The Reporter's Advocate
The EU Whistleblower Directive is named and genuinely explained — who is obligated from 50 employees, the transposition date, penalty examples by country — and the product is presented as the internal channel duty-solver across EU, UK, US and UAE regimes. But we found no public information on any national transposition such as the German HinSchG mapped to product features, nor the acknowledgement and feedback deadlines appearing as product behaviour; policy publishing and acknowledgement tracking are marked coming soon. 11 1 9 2
The SME Operator
The vendor publishes a dedicated page explaining that the EU Whistleblower Directive is mandatory, applies to private businesses with 50 or more employees, and carries fines up to €50,000 in Italy and Germany, and lists UK PIDA, California SB 553 and ISO 37002 alongside auditable case management and customizable retention. But we found no public information naming a national transposition such as the German HinSchG, mapping the acknowledgement and feedback deadlines to features, or documenting legal review by named counsel with an update process. Self-serve setup in hours is the appeal for me, yet the legal homework stays mine. 11 1 2
The Group Counsel
The EU Whistleblowing Directive is explained with real substance — the 50-employee and 10,000-inhabitant thresholds, the transposition deadline, member-state penalties in Italy, Germany, France and Belgium — and the platform is positioned as the internal reporting channel, with UK PIDA and California SB 553 also named. But no national transposition is implemented as a feature set: we found no public information on per-country rule sets, on reporting-policy or employee-information templates, or on legal review by named counsel or a documented process. 11 1
The Security Auditor
The EU Whistleblower Directive is named with who it obliges — private businesses and public bodies with 50 or more employees — its transposition deadline and example penalties in Italy, France, Belgium and Germany, and the platform is presented as the internal reporting channel for it alongside UK PIDA, California SB 553 and ISO 37002. We found no public information on national transpositions implemented as per-country rule sets, on the acknowledgement and feedback deadlines mapped to product features, or on templates, employee-communication guidance or legal review by named counsel. 11 1
The Skeptic
The vendor names the EU Whistleblowing Directive with real regulatory detail — employee and inhabitant thresholds, the transposition deadline, and penalty examples for Italy, Germany, France and Belgium — plus UK PIDA and California SB 553, which is more than a badge. But the pages never map the directive's operational duties to features, I found no public information on national transposition rule sets or named legal counsel, and the policy management module that would carry employee-facing templates is marked coming soon. 11 1
Security & anonymity assurance
Show reasoningHide reasoning
How this is scored
Whether the confidentiality promise is engineered and evidenced: encryption, IP and metadata handling, penetration tests, certifications of the vendor and its hosting.
0 — Reports are not protected as confidential data; the product makes no security or confidentiality commitment for them.
3 — Encrypted transmission and storage of reports stated, and a commitment that reports are confidential.
5 — Encryption of report content described with some technical detail (end-to-end or at rest with key handling), a statement that IP addresses or metadata are not logged, and an ISO 27001 certificate for the vendor or its named hosting provider.
8 — A certified ISMS covering the product itself, regular third-party penetration tests stated, the encryption architecture documented, metadata minimisation explained, and a security contact or disclosure policy published.
10 — Assurance a hostile auditor accepts: current certificates with their scope published, recurring pentest summaries public, the cryptographic architecture documented, and anonymity analysed against the operator itself — the vendor explains why it cannot unmask a reporter.
The Compliance Officer
ISO 27001 and SOC 2 are stated, regular penetration testing and continuous code security testing are claimed, and the encryption architecture is documented in real depth: standard versus end-to-end modes, keys that never leave the user's device, stated key lengths, per-member recovery keys and the feature trade-offs of end-to-end encryption. Metadata minimisation is explained — no IP logging, no device IDs, stripped attachment metadata, no tracking tools — though I found no public pentest summaries, certificate scopes or security disclosure policy. 6 3 13 14 9 3
The Reporter's Advocate
The confidentiality promise is engineered in public: end-to-end encryption whose keys never leave the device, stated key lengths of 128-bit symmetric and 1024-bit asymmetric, IP addresses not logged, emails hashed beyond retrieval, voice altered, no tracking scripts on the form, with ISO 27001 and SOC 2 claimed and regular penetration testing stated. What holds it below the top: certificate scopes are not published, pentest results are not public, and we found no published security contact or disclosure policy. 3 13 6 14 3 1
The SME Operator
ISO 27001 and SOC 2 certifications, regular penetration testing and continuous code security testing, encryption at rest and in transit with an end-to-end mode where keys never leave the device, no IP logging, stripped attachment metadata, no device IDs and Tor support give me a story a hostile auditor can check. We found no public information on published penetration test summaries or a security contact and disclosure policy, so it stops short of the top tier of assurance. 3 6 13 14 1 3
The Group Counsel
Both encryption modes are documented with key handling — end-to-end keys never leave the user's device, plus 128-bit symmetric and 1024-bit asymmetric ciphers — alongside ISO 27001 and SOC 2 certification, regular penetration testing, no IP logging, stripped attachment metadata, hashed emails, an in-house anti-spam solution that preserves anonymity, and Tor support. A hostile auditor will still push back: we found no public information on certificate scope, pentest summaries, or a published security contact or disclosure policy. 3 6 13 14 3
The Security Auditor
The anonymity engineering is real and documented: end-to-end mode keeps keys on the device with a per-member recovery key, IP addresses are not logged, no device IDs, attachment metadata stripped, no tracking scripts or external calls on the form, emails hashed in the database, and hotline voice anonymised. ISO 27001 and SOC 2 are stated as badges but we found no published scope for either certificate, penetration testing is claimed as regular with no third-party attribution, dates or summaries, the data processing agreement states a 1024-bit asymmetric key length which I would not accept today, and we found no public information on a security contact or vulnerability disclosure policy. 3 6 9 13 14 3
The Skeptic
Certificates appear as badges: ISO 27001 and SOC 2 are claimed on several pages, though the captured pages give different framings for SOC 2 — the platform in one place, the AWS infrastructure in another — and neither certificate's scope is published, while pentests are "regular" with no third party or summary named. The engineering detail is what earns the score: end-to-end encryption with keys that stay on the device, documented recovery limits and feature trade-offs, hashed emails, no IP logging, and a stated no-tracking-tools position with no analytics scripts on the reporting form. 3 6 13 14 3
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-labelling.
0 — Built for a single organisation only; a group needs one separate contract and instance per company.
3 — Several reporting channels or companies managed under one account.
5 — Separate channels per legal entity with their own case handlers, a group-level overview, and branding per channel; access for an external ombudsperson or counsel possible.
8 — A multi-tenant group structure: per-entity channels, languages and branding, delegated administration per subsidiary, external ombudsman roles, and group reporting that respects entity boundaries.
10 — Group compliance as architecture: hundreds of entities managed centrally, per-country legal rules assigned per entity, white-label reporting pages, and access separation strong enough to satisfy each subsidiary's works council — all documented.
The Compliance Officer
Separate forms per entity, entity-specific routing and access permissions, per-unit anonymity settings, multi-entity oversight on every plan, per-channel branding with custom domains, and an enterprise package for programs across entities and regions give a genuine group structure. I found no public information on delegated administration per subsidiary or on access for an external ombudsperson or counsel. 2 11 1 2 7 9
The Reporter's Advocate
Separate forms per entity, topic or region with entity-specific routing and access permissions, anonymity configurable per organisational unit, branding and 113 languages on every plan, and multi-entity oversight stated as out of the box. We found no public information on access for an external ombudsperson or counsel, nor on delegated administration per subsidiary, so this reads group-friendly rather than group-proven. 2 11 1 7 2
The SME Operator
Separate forms per entity, topic or region with entity-specific routing and access permissions, per-unit anonymity settings, multi-entity oversight on every plan and branding by logo, colors and custom domain cover a group's basics. We found no public information on delegated administration per subsidiary or dedicated external ombudsperson access, and the full multi-entity, multi-country support sits in the Enterprise package where scope is negotiated with sales. 2 7 11 1 2
The Group Counsel
Group use is more than an afterthought: entity-specific routing and access permissions, separate forms per entity, topic or region, per-organizational-unit anonymity settings, branding with custom domains per channel, multi-entity oversight claimed on every plan, and enterprise support for multi-entity and multi-country setups, with dashboards filterable by region. For my 25 subsidiaries the gaps matter: we found no public information on delegated administration per subsidiary, on an external ombudsman role, or on group reporting that consolidates while respecting entity boundaries. 2 7 9 11 1 9
The Security Auditor
Separate forms per entity, topic or region, entity-specific routing and access permissions, anonymity configurable per organizational unit, multi-entity oversight, per-channel branding and a multi-entity enterprise package are all documented. We found no public information on delegated administration per subsidiary or on access for an external ombudsperson. 2 7 11 1 9
The Skeptic
Group operation is more than a marketing line: separate forms per entity, entity-specific routing and access permissions, per-organisational-unit anonymity settings, branding by logo, colours and domain, a stated multi-entity overview, and 113 languages on every plan rather than only the top tier. I found no public information on delegated administration per subsidiary or access for an external ombudsperson, which is what separates serious group setups. 2 11 1 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where reports about people actually live and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, phone or voice provider, translation, email), and the data processing agreement. In this category the data is by definition the most sensitive a company holds. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or EU hosting is offered only on request or on top tiers.
5 — EU hosting stated as the default, a data processing agreement and a subprocessor list published; a parent company or a subprocessor may sit outside the EU.
8 — EU entity, EU hosting in named data centres, a subprocessor list with no non-EU processor touching report content, and the DPA and TOMs published.
10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors for report content and metadata, an on-premises or sovereign-cloud option, and the whole chain documented publicly.
The Compliance Officer
The contracting entity is Czech, the data processing agreement is public with a subprocessor annex and EU standard contractual clauses, and AWS hosting offers a selectable EU region among four, with no default region stated — EU residency depends on the customer's own choice. For hotline content the position is weaker regardless of region: hotline services are processed in the United States, and the subprocessor list names US processors — Vonage, AnswerNet, OpenAI and Sentry. 4 6 3
The Reporter's Advocate
The contracting entity is Czech and the data processing agreement with a published subprocessor annex exists, but EU storage is one of four selectable AWS regions with no default stated — and the captured pages give different lists of the available regions. Whatever region a customer picks, hotline calls are processed in the United States through US phone and AI subprocessors, and a US sister entity handles United States data, so the chain touching spoken reports about people is not European end to end. 4 6 3 3
The SME Operator
The contracting picture is a Czech company plus a second entity in Brno for the rest of the world and a US entity for US data, and EU storage on AWS is customer-selectable among the US, EU, UAE and Australia with no default stated. The data processing agreement and subprocessor list are published, but the hotline runs through US providers (Vonage, AnswerNet, OpenAI) and hotline services are processed in the US regardless of the chosen region, so anonymous voice reports about my staff do not stay in the EU even when I select the EU region. 4 6 3
The Group Counsel
The contracting entity is Czech and a data processing agreement with technical measures and a subprocessor list in Annex B is published, but the EU is only one of four selectable AWS regions — alongside the US, UAE and Australia — with no default stated, and hotline calls are processed in the United States through OpenAI, Vonage and AnswerNet regardless of the chosen region, while AI, translation and transcription run centrally in the EU. With US processors touching hotline content and metadata, and we found no public information on a sovereign-cloud or on-premises option, this is not a chain I can defend to a works council. 4 6 3
The Security Auditor
A Czech contracting entity, a published data processing agreement with SCCs and a subprocessor annex are proven, but the EU is one of four selectable AWS regions with no default stated, and the chain has hard non-EU dependencies: hotline calls are processed in the United States through Vonage, AnswerNet and OpenAI, and Sentry handles error reporting. AI features are processed centrally in the EU regardless of chosen region, and we found no public information on an on-premises or sovereign-cloud option. 4 6 3
The Skeptic
The chain is half-proven: a Czech contracting entity, a selectable EU region on AWS, a published DPA with SCCs and a subprocessor list — but no default region is stated, and the hotline chain is American end to end, with Vonage, AnswerNet and OpenAI as named US subprocessors and hotline processing stated to occur in the US, while a second entity serves US data processing. Voice reports about people — the most sensitive data a company holds — are documented as flowing through that US chain regardless of the chosen region. 4 6 3
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: tier prices, billing period, employee bands, add-ons (phone intake, languages, entities) and setup fees.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier; the other tiers, employee bands or add-ons are not public.
5 — Public per-tier prices with the billing period (monthly or annual) stated and the main inclusions or employee band of each tier listed.
8 — Every tier priced publicly with employee-band boundaries, entity rules, add-ons (phone intake, languages, extra entities) and setup fees stated, and VAT treatment given; 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
No tier carries a public price — Starter is "Get a Quote", Enterprise is "Contact Sales", and the pricing page itself asks why prices are not on the page — so I cannot compute an invoice for my 600 employees from anything published. Some credit for structure: a platform fee plus chosen capabilities priced on the headcount of everyone who can report, monthly, quarterly or annual billing with an annual saving of up to 30%, and per-plan administrator limits. 2 8 2
The Reporter's Advocate
The pricing model is explained — a platform fee plus chosen capabilities priced on everyone who can report, monthly, quarterly or annual billing with up to 30% annual saving, admin limits per tier, never charged per report, no mid-term charge for growth — but not a single figure is public: the Starter tier is a quote request, Enterprise is contact sales, and the current page itself asks why prices are not shown. An obligated company cannot compute any part of the invoice from public pages. 2 2 8 2
The SME Operator
The pricing model is public and, for my taste, right: a platform fee plus chosen capabilities priced on everyone who can report, never charged per report, monthly, quarterly or annual billing with up to 30% saved on annual, headcount fixed at contract so growth creates no mid-term charge, and self-serve setup with no professional services contract. But not one euro is published — the pricing page asks "Why aren't prices on this page?", Starter is "Get a Quote" and Enterprise is "Contact Sales" — so my year-end invoice cannot be computed from public pages and starts with a sales call. 2 8 2 2
The Group Counsel
No figure appears anywhere: the Starter plan says "Get a Quote", Enterprise says "Contact Sales", and the pricing page itself asks "Why aren't prices on this page?" while referring to a price list that states no prices. The model is described — a platform fee plus chosen capabilities priced on everyone who can report, monthly, quarterly or annual billing with up to 30% annual saving, and no mid-term charge for growth — but for a 25-entity group the invoice is not computable from public pages. 2 8 2
The Security Auditor
We found no public prices at all: Starter is quote-based, Enterprise is contact-sales, and the captured pages themselves ask why prices are not shown. The structure is public — a platform fee plus chosen capabilities priced on the headcount of everyone who can report, monthly, quarterly or annual billing with up to 30% annual savings, and per-plan administrator limits — but no figure an obligated company could compute an invoice from. 2 2
The Skeptic
No price figure is public anywhere in the captured pages — Starter is "Get a Quote" and Enterprise is "Contact Sales" — so an obligated company cannot compute a real invoice from public material. To be fair, the model is described openly: a platform fee plus chosen capabilities priced on the headcount of everyone who can report, never per report, with monthly, quarterly or annual billing and up to 30% off for annual — but a described model without numbers is still a sales conversation. 2 8 2
European sovereignty — proven facts
3 of 6 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 |
Incorporated in CZ
unverified
Why unverified?Dual-entity structure: the same page names a second entity, FaceUp Technology s.r.o. with registered address at Jiráskova 222/18, 602 00 Brno - střed, for processing in the rest of the world, but states no country for it. |
2/2 pts | 4 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?EU is only one selectable region among US, UAE and Australia and no default region is stated; the same page notes that some features are processed centrally regardless of the chosen region (AI features in EU, live hotline in US). |
— | uncited Report an error |
| Hosting options |
EU region selectable
unverified
Why unverified?The EU region is one of four selectable AWS regions and the choice is left to the customer; no self-hosted or on-premises option is offered anywhere on the pages. |
1/1 pts | 3 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 6 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about FaceUp
Is FaceUp European?
Yes. whats-best.ai classifies FaceUp as EU-Made. Its vendor, FaceUp Technology s.r.o., is incorporated in Czechia, per the vendor’s page captured 16 Nov 2026.
Where does FaceUp store data?
The default storage location for customer data is not stated on the vendor’s pages as of 16 Nov 2026. The vendor’s pages mention the EU, the United States and Middle East as hosting locations, per the vendor’s page captured 16 Sep 2026.
Does FaceUp have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to FaceUp?
As of 19 Nov 2026, the panel rates preeco | hinweisgeberschutz (3.5/5), SpeakUp (3.5/5) and EQS Integrity Line (3.5/5) highest among the other 44 Whistleblowing Portals products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | hinweisgeberschutz (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: FaceUp alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 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. Dual-entity structure: the same page names a second entity, FaceUp Technology s.r.o. with registered address at Jiráskova 222/18, 602 00 Brno - střed, for processing in the rest of the world, but states no country for it.
- Weak sourcing — Hosting location. EU is only one selectable region among US, UAE and Australia and no default region is stated; the same page notes that some features are processed centrally regardless of the chosen region (AI features in EU, live hotline in US).
- Weak sourcing — Hosting options. The EU region is one of four selectable AWS regions and the choice is left to the customer; no self-hosted or on-premises option is offered anywhere on the pages.
- 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.
- 8 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
- 5 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
- 5 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
- 3 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
- 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 pricing 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 subprocessors 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.faceup.com Checked 16 Nov 2026 +1 earlier capture: 16 Sep 2026 Details →
- 2 Pricing page www.faceup.com Checked 16 Nov 2026 +2 earlier captures: 19 Oct 2026, 16 Sep 2026 Details →
- 3 Security page www.faceup.com Checked 16 Nov 2026 +1 earlier capture: 16 Sep 2026 Details →
- 4 Privacy policy www.faceup.com Checked 16 Nov 2026 Details →
- 5 Whistleblowing product page www.faceup.com Checked 16 Nov 2026 Details →
- 6 Data processing agreement (dpa) www.faceup.com Checked 16 Nov 2026 Details →
- 7 Reporting channels & reporter experience — found from sitemap support.faceup.com Checked 16 Nov 2026 Details →
- 8 Reporting channels & reporter experience — found from sitemap support.faceup.com Checked 16 Nov 2026 Details →
- 9 Case management & deadline discipline — found from sitemap www.faceup.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 10 Case management & deadline discipline — found from sitemap support.faceup.com Checked 16 Nov 2026 Details →
- 11 Legal compliance alignment — found from sitemap www.faceup.com Checked 16 Nov 2026 Details →
- 12 Legal compliance alignment — found from sitemap support.faceup.com Checked 16 Nov 2026 Details →
- 13 Security & anonymity assurance — found from sitemap support.faceup.com Checked 16 Nov 2026 Details →
- 14 Security & anonymity assurance — found from sitemap support.faceup.com Checked 16 Nov 2026 Details →
- 15 Structured-data backfill: markup only, no text or screenshot www.faceup.com Checked 8 Nov 2026 Details →