Whistleblowing Portals
Walor
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 Walor ApS · www.walor.io
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
Walor ApS, a Copenhagen-based whistleblowing portal acquired by Ziik in November 2024, posts its top marks on pricing transparency and its floor on group & multi-entity capability. Reporting channels & reporter experience, case management & deadline discipline, and sovereignty sit flat at 4: a unique link offers confidential or anonymous two-way dialogue, report management carries deadline alerts and GDPR-time-limit auto-deletion, and EU-only hosting is claimed alongside an available DPA, with no data centers or subprocessors named. The widest spread is legal compliance alignment: lower scores cite no mention of Directive 2019/1937 or any national transposition, only ISO 37002 principles and a policy-creation onboarding service, while the SME Operator credits that same scaffolding as more than a feedback box. Pricing transparency spreads over a single visible figure — 87 € excl. VAT per month, billed annually — stretched across two tiers and four employee bands. Group & multi-entity capability is the lowest category: one reporting link per customer, bands capped at 500–999 employees, no group view or per-entity access in evidence; security & anonymity assurance leans on ISO 27001 scoped to hosting data, standard 2FA, and self-graded encryption.
Speaks for it
- Confidential or anonymous two-way dialogue with follow-up communication keeps the conversation alive past submission
- One real price is public — 87 € excl. VAT per month, billed annually in Euros — with four published employee bands, two tiers, and a free trial
- EU-only hosting is claimed as the default, a DPA is available, and ownership remains Danish after the Ziik acquisition
- Two-factor authentication is the standard and the platform states it applies no tracking mechanisms on users
- Caseworkers can be selected from inside or outside the organisation, including external compliance officers
Held against it
- Employee bands stop at 500–999 and a single visible price covers two tiers, so only a small single company can roughly compute its invoice
- Nothing evidences per-entity channels, separated case access, delegated administration, or a consolidated group view
- Directive 2019/1937 and national transpositions such as HinSchG are never named, leaving compliance to ISO 37002 principles and generic GDPR claims
- End-to-end encryption is described in marketing superlatives with no architecture, pentest attestation, security contact, or disclosure policy
- Deadline alerts are never tied to the statutory 7-day acknowledgment or 3-month feedback clocks, and no audit trail, role separation, or caseload reporting is evidenced
Best for
- You are a single legal entity in the 50–249 employee band that needs one anonymous channel with follow-up dialogue at a roughly computable price
- You want a fast launch — signup is advertised at 5 minutes, with a free trial and an onboarding service that creates your whistleblower policy
- You require EU-based hosting and an available DPA as your baseline before deeper due diligence
Avoid if
- You are a corporate group needing per-entity channels, separated case access, or a consolidated group view — the evidence evidences none of these
- You must map product features to Directive 2019/1937 or a named national transposition before signing — neither appears anywhere on the evidence
- You employ more than 999 people — ask the vendor: the public pages we read do not show it
- You need verified security documentation — ISO 27001 scope, a pentest report, a subprocessor list — to pass procurement or an external audit
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 dialogue with whistleblowers and a distributable unique link are claimed, with follow-up communication as a listed feature, so the dialog does not dead-end like an inbox form. But there is zero evidence on phone/voice intake, language coverage, mobile-friendliness or accessibility, so I cannot push this past mid-table — the frightened reporter gets a link and a mailbox, and that is all I can confirm. 2 3 4
The Reporter's Advocate
A unique link with 'confidential or anonymous dialogue' and no tracking mechanisms on users is a workable front door, but the evidence is silent on languages, phone or voice intake, mobile behavior, and how the reporter's identity stays out of the channel — the frightened worker gets anonymity of unstated shape, with no evidence they can report in their own language at 3 a.m. 2 3 4
The SME Operator
Anonymous or confidential submission and follow-up dialogue are confirmed through the reporting link, so anonymity survives first contact — but the evidence is silent on languages, phone intake, and mobile, which caps it below the anchor where those are evidenced. 3 4
The Group Counsel
Confidential or anonymous dialogue with follow-up communication is claimed, so the dialog does not die at the form, but there is not one word on languages, voice intake, mobile, or how a reporter's identity stays out of the single unique link. For a group spread across a dozen countries, total silence on language coverage is itself information — this sits between a dead-end anonymous form and a first-class channel. 3 4
The Security Auditor
There is a unique distribution link with confidential or anonymous submission and a claimed two-way 'dialogue with whistleblowers' plus follow-up communication, which clears the anonymous-form-only bar. But the evidence is silent on languages, phone/voice intake, accessibility, mobile behavior, and — the part I actually care about — how the reporter's identity is kept out of the channel itself; 'anonymous' is asserted, never engineered in public. 3 4
The Skeptic
Anonymous or confidential two-way dialogue is claimed, and "the platform does not apply tracking mechanisms on users" is the sole statement about keeping identity out of the channel — the anchor-10 requirement of documenting how is absent. The evidence is completely silent on languages, mobile, voice, QR and accessibility; one unique web link is the only intake channel in evidence, which sits between the dead-end form and a properly engineered dialog. 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
"Receive deadline alerts" and "Report management" use the right vocabulary, but nothing ties the alerts to the 7-day acknowledgment or 3-month feedback clocks, and there is no evidence of case notes, attachments, tamper-evident history, or role separation beyond choosing internal or external caseworkers. Automatic deletion per GDPR time limits is the only discipline I can actually verify — as the one who answers for missed clocks, "deadline alerts" is a promise, not a system. 2 3 4
The Reporter's Advocate
'Receive deadline alerts', internal-or-external caseworker selection, report management and automatic GDPR deletion is more than an inbox, but nothing evidences the 7-day/3-month statutory clocks being enforced, conflict-of-interest exclusion, a tamper-evident history, or any caseload reporting. 2 3 4
The SME Operator
Deadline alerts and selectable internal or external caseworkers exist, which is the scaffolding I want for legal duties handled by the product — but nothing ties the alerts to the 7-day acknowledgment or 3-month feedback clocks, and there is no evidence of an audit trail or case-level retention beyond generic GDPR auto-deletion. 2 3
The Group Counsel
'Receive deadline alerts' and 'report management' are the entire case story — no statutory 7-day/3-month clocks, no role separation, no audit trail, no caseload statistics. The option to name external caseworkers and automatic GDPR-based deletion are the only fragments lifting this above a case list next to a spreadsheet. 2 3 4
The Security Auditor
Report management, deadline alerts, automatic deletion per GDPR time limits, and caseworkers selectable from inside or outside the organisation put this slightly above a bare case list. Nothing on role separation, conflict-of-interest exclusion, tamper-evident history, or caseload reporting — deadlines get alerts, but the audit-proof record a case worker would be judged on is unevidenced. 3 4 2
The Skeptic
"Report management" and "follow-up communication" plus generic "deadline alerts" and GDPR-based automatic deletion give reminders and retention, but nothing evidences an audit trail, tamper-evident history, conflict-of-interest exclusion, case notes or caseload reporting. The statutory clocks (7-day, 3-month) are never named, so the deadline feature could be a calendar nudge for all the evidence shows. 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
No national transposition is ever named — not Directive 2019/1937, not HinSchG — just ISO 37002 "principles" and policies "ensuring compliance with relevant legislation", which is exactly the vague marketing mapping rubric level 3 describes. Clocks and retention exist as product features, but the legal homework is nowhere shown. 1 2 3
The Reporter's Advocate
The Directive and every national transposition are absent from the evidence; the compliance story rests on ISO 37002 'principles' and generic GDPR deletion, with legal duties outsourced to a service that writes your policy for you rather than implemented as product features. 1 2
The SME Operator
The vendor builds my policies 'ensuring compliance with relevant legislation' and leans on ISO 37002 principles with GDPR-time-limit auto-deletion, which is more than a relabeled feedback box — but Directive 2019/1937 and national transpositions like HinSchG are never named, and the statutory clocks are not documented as product features, so the mapping stays vague. 1 2
The Group Counsel
Nowhere does the evidence mention Directive 2019/1937 or any national transposition — the product leans on ISO 37002 principles and generic GDPR claims, plus onboarding that 'ensur[es] compliance with relevant legislation'. For a dozen jurisdictions this is a label, not legal implementation: no per-country rule sets, no named counsel, no acknowledgment or feedback duty anywhere in evidence. 1 2 3
The Security Auditor
The evidence names GDPR, ISO 37002 principles, GDPR-based automatic deletion, and a policy generator with onboarding 'ensuring compliance with relevant legislation' — but EU Directive 2019/1937 and any national transposition like HinSchG are never named, and the 7-day/3-month statutory clocks are not implemented as anything more than generic deadline alerts. This is compliance-adjacent feature marketing, not a mapping of legal duties to product behavior. 2 3 1
The Skeptic
Nowhere in the captured pages does Walor name EU Directive 2019/1937 or any national transposition — only "compliance with relevant legislation", GDPR, and being "built on the principles of" ISO 37002, a management standard, not a law. "Become compliant... in 5 minutes" is a slogan, no named counsel or legal-update process exists, and the policy-creation service promises legal correctness with no named lawyer behind it. 1 2 3
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
ISO 27001 for hosting and standard two-factor authentication are on the security page, but the end-to-end encryption claim is pure adjectives — "top marks", "strongest algorithms" — with no architecture, no pentest, no no-IP-logging statement and no metadata discussion. "Does not apply tracking mechanisms" is the only nod toward the operator not seeing the reporter; nobody here could yet answer "how would you unmask a whistleblower?". 2
The Reporter's Advocate
ISO 27001 is claimed for 'our approach to hosting data' — whose certificate, whose hosting, unstated — and end-to-end encryption is self-graded 'top marks' with no pentest, no security contact, and no answer to 'how would you unmask a reporter?'; the no-tracking statement is the one genuinely reporter-protective fact, but metadata handling beyond it is undocumented. 2
The SME Operator
ISO 27001 certified hosting, 2FA as standard, claimed end-to-end encryption, and no user tracking is roughly the 5-anchor package and enough for a year-end review — but 'top marks' is marketing with no pentest, no disclosure policy, and a certificate scope limited to hosting data rather than the vendor itself. 2
The Group Counsel
ISO 27001 is claimed for hosting and 2FA is standard, but the end-to-end encryption is described in marketing superlatives with no architecture, no pentest report, no security contact or disclosure policy, and 'no tracking mechanisms' is not an IP-logging statement. I could not hand this file to an external auditor and expect it to survive. 2
The Security Auditor
This is adjective security: 'top marks for our secure end-to-end encryption' and 'strongest encryption algorithms' with zero technical architecture, no published pentest, no certificate document or visible ISO 27001 scope (it certifies 'our approach to hosting data', whatever that means), and no security contact or disclosure policy. The 2FA-by-default and no-tracking statements earn partial credit, but nobody here can answer 'how would you unmask a reporter?' with evidence. 2
The Skeptic
The ISO 27001 claim covers "our approach to hosting data" — read: the host's certificate, not the vendor's product ISMS, and no certificate scope or number is shown. "Walor achieves top marks for our secure end-to-end encryption" is self-graded puffery with zero architectural detail, and beyond "no tracking mechanisms" there is no pentest attestation, no security contact or disclosure policy, and no explicit IP/metadata logging statement. 2
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
The evidence is silent on per-entity channels, group oversight and ombudsman access, and the employee-band ladder stops at 500-999 with no enterprise or group tier — one company, one channel, N instances for a group. The only group-adjacent fact is that caseworkers may be external parties, which does not buy an entity structure. 3 4
The Reporter's Advocate
Nothing in the evidence serves a corporate group: no per-entity channels, no consolidated view, no delegated administration anywhere; the only group-adjacent fact is that external compliance officers can act as caseworkers, and the employee bands stop at 999, which tells you the market they're aiming at. 3 4
The SME Operator
Nothing in the evidence evidences per-entity channels, separated case access, or any group overview — the single distributed reporting link and employee tiers topping out at 999 read single-company. Fine for my one entity, but a group buyer has no evidence to stand on. 3 4
The Group Counsel
The product is one unique link per customer with employee bands capped at 999; nothing evidences per-entity channels, separated case access per subsidiary, delegated administration, or a consolidated group view. This is precisely the one-channel product I would have to multiply by twenty-five contracts — my standing rejection case, and the external-caseworker option is the only sliver suggesting anything beyond a single entity. 3 4
The Security Auditor
The evidence is completely silent on multiple channels per legal entity, per-entity case separation, group overview, branding, or delegated administration — silence is information, and I score what's evidenced. The only group-adjacent fact is that caseworkers can be external parties, which is about individuals, not structure. 3 4
The Skeptic
The features list contains nothing about per-entity channels, separated case access, group overviews, delegated administration or ombudsman roles — the only multi-party gesture is that caseworkers can be external compliance officers. Pricing tops out at a 500–999 employee band, and absence of any group language on the vendor's own pages tells me a corporate group is buying N instances. 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
EU-only hosting is stated as the default and a DPA exists, and the vendor stays Danish after the Ziik acquisition — better than EU-on-request. But no data centers are named, no subprocessor list is published, and the residency claim sits in marketing copy, so the chain behind the most sensitive data we hold cannot be verified from public pages. 1 2 4
The Reporter's Advocate
'Only hosts data on EU-based servers' with a public DPA and Danish ownership under Ziik is a start, but no data centers are named, no subprocessor list exists, and the host behind the ISO 27001 claim is invisible — for the most sensitive data a company holds, the chain is asserted in marketing copy, not documented. 1 2 4
The SME Operator
Danish entity under Danish ownership (Ziik), EU-only hosting, and a published DPA point the right way — but the EU-only claim is one marketing line with no named data centers, no subprocessor list, and no TOMs, and undocumented subprocessors for the most sensitive data my company holds is exactly the gap I cannot ignore. 1 2 4
The Group Counsel
EU-only hosting is claimed and a DPA exists, and Walor ApS under Danish ownership post-Ziik is a promising start — but there are no named data centers, no subprocessor list, no TOMs, and the vendor's own captured pages do not even confirm jurisdiction. A marketing sentence about EU servers is not a documented chain for the most sensitive data a group holds. 1 2 3 4
The Security Auditor
Walor ApS is Danish, ownership after the Ziik acquisition remains Danish, EU-only hosting is asserted as the default, and a DPA is available — that clears the 3-anchor. But the EU-hosting claim is one marketing sentence with no named data centers, no published subprocessor list, and subprocessor exposure explicitly unknown, which for the most sensitive data a company holds means I cannot verify the chain. 2 3 1 4
The Skeptic
EU-only hosting is asserted in marketing copy with no named data centers, providers or redundancy regions, and a DPA exists — but there is no published subprocessor list, no TOMs, and the evidence itself flags legal-entity jurisdiction and ownership as unconfirmed with a post-acquisition caveat. An unaudited "EU-based servers" sentence is exactly where a US-touched host hides. 1 2 3 4
Pricing transparency
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
One real number — €87 excl. VAT, billed annually — with employee bands 1-49 through 500-999 and a "no hidden fees or extra charges" claim. I can roughly compute a single-entity 600-employee invoice, but the second tier's price, per-entity rules and any add-ons are absent from evidence, so a group's invoice is not computable from these pages. 1 3 4
The Reporter's Advocate
Two tiers with 'no hidden fees or extra charges', €87/month excl. VAT billed annually and a free trial put real numbers, VAT treatment and billing period on the table — but four employee bands share one visible price, so an obligated mid-band company still cannot compute its invoice from the evidence. 1 3 4
The SME Operator
Two tiers with 'no hidden fees or extra charges', €87/month excl. VAT billed annually in euros, published employee bands covering my 50-249 range, and a free trial is nearly the invoice I can defend — but only one price is evidenced for two tiers, so I cannot confirm which number lands on my 60-employee bill, and entity rules are unstated. 1 3 4
The Group Counsel
Band boundaries, annual Euro billing, VAT-excluded treatment and a 'no hidden fees' promise are public, yet only one figure (87 €/month) is captured for a two-tier product and per-entity pricing does not exist anywhere on the evidence. A 60-employee single company can roughly guess its invoice; a 25-entity group cannot begin to compute one. 1 4
The Security Auditor
Real numbers with VAT treatment and billing period stated: €87 excl. VAT/month billed annually, four employee bands, a 'no hidden fees' claim, and a free trial. But only one of the two tiers carries a visible price in the evidence, the bands stop at 999 employees leaving larger obligated companies unpriced, and nothing is said about entities — so the invoice is computable for a small single company only. 4 1 3
The Skeptic
One real number is public — 87 €/month excl. VAT, billed annually — with a free trial and a "no hidden fees or extra charges" slogan, but four employee bands sit against a single captured price across two tiers, so I cannot compute the invoice for a 300-employee company from these pages. Per-entity pricing does not exist at all, and "no hidden fees" is a claim, not an add-on price list. 1 3 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 | EU only ⚠ unverified | 3/3 pts | 2 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 17 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. The DPA permits processing in "Copenhagen, Denmark and any other locations mentioned under B.2", and the Appendix B sub-processor table containing those locations is not shown in the excerpt.
- 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.
- 25 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
- 12 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 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
- 5 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 subprocessors 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 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.walor.io Checked 17 Sep 2026 Details →
- 2 Security page www.walor.io Checked 17 Sep 2026 Details →
- 3 Features page www.walor.io Checked 17 Sep 2026 Details →
- 4 Pricing page www.walor.io Checked 17 Sep 2026 Details →
- 5 Terms of service www.walor.io Checked 30 Sep 2026 Details →
- 6 Privacy policy www.walor.io Checked 30 Sep 2026 Details →
- 7 Data processing agreement (dpa) www.walor.io Checked 30 Sep 2026 Details →
- 8 Reporting channels & reporter experience — found from sitemap www.walor.io Checked 1 Oct 2026 Details →
- 9 Reporting channels & reporter experience — found from sitemap www.walor.io Checked 1 Oct 2026 Details →
- 10 Legal compliance alignment — found from sitemap www.walor.io Checked 1 Oct 2026 Details →
- 11 Security & anonymity assurance — found from sitemap www.walor.io Checked 1 Oct 2026 Details →