Skip to content
CUNICULA

SimpleX Chat

Decentralized encrypted messenger with no user IDs, connecting through invitation links or QR codes.

simplex.chat

Decentralized encrypted messenger with no user IDs, connecting through invitation links or QR codes.

Common useMessagingMessagingOperator dataUnknown
Identity checksNo routine KYCNo document check recorded · identity exposure level 0/4
Evidence and riskVerified evidenceCautionMaterial claims checked against current sources.; those sources show trade-offs worth reading.
Last reviewedReviewed 8 Nov 2026KYC checked 8 Nov 2026 · verified jurisdiction · Source → official documentationHow to cite this pageSource coverageVerified evidenceRecorded riskCaution
Evidence and facts

Evidence and facts

CUNICULA SCORE 4.0
39/100Reviewed evidencePrivacy 17/25 · Control 18/20 · Transparency 12/20 · Security 12/25 · Accountability 8/10 · Cap 39 · Method
JURISDICTIONUK
OWNED BYSimpleX Chat Ltd develops the software and operates preset services; Companies House lists Evgeny Poberezkin as PSC with 75% or more shares.
CAUTIONNo global user IDs does not mean no metadata: the Nov 1 policy permits temporary anti-abuse IP/session information, iOS push tokens and queue counts, directory/support data, and six-year optional badge payment records. UK-incorporated SimpleX Chat Ltd operates preset services; users can choose relays, but instant iOS push remains centralized. Terminal clients before v6.5 had CVE-2026-52103; update old CLI installations. The 2026 audit is reported completed but its report is not public.
INCIDENTTerminal notification command injection before SimpleX v6.5
monitoring · potential high · published 2026-05-10
CVE-2026-52103 concerns incoming-message command injection in terminal desktop notifications before v6.5. The researcher identifies v6.5 as the fixed release but did not verify macOS patch robustness. This is potential endpoint execution, not a demonstrated breach of the messaging network. Researcher disclosure, CVE record, v6.5.0 release
AUDITED BYTrail of Bits - 2022 implementation; 2024 protocol design (historical scopes)
OPERATOR DATAUnknown
SOURCE COVERAGE
Verified evidenceDIRECTLY TESTED8/21Reviewed 8 Nov 2026 · Source → official documentation
LAST CHECKED2026-08-27
LAST UPDATED2026-08-27

Specs

DOCUMENT CHECKNone recorded
IDENTITY EXPOSURELevel 0/4
KYC TRIGGERSNo phone number, username, global account or document KYC required for normal messaging. Contacting support by email exposes ordinary email metadata to mail providers.
FEEFree private messaging; optional paid supporter badges and planned channel/business services.
NETWORKSFOSS, Mobile, Desktop, Terminal
CATEGORIESMessaging
TORNot listed
REGIONSGlobal availability
Review analysis, source material, related services, and history

Analysis

OVERVIEW

No global user IDs and selectable/self-hosted relays distinguish SimpleX; historical Trail of Bits implementation and protocol-design reports are public.

LIMITS

No global ID is not no metadata: temporary anti-abuse IP/session data, iOS push tokens, directory/support and badge payments exist. Update pre-v6.5 terminal clients for CVE-2026-52103; the 2026 audit is reported completed but unpublished.

USEFUL FOR

Messaging without a phone-number account, while accepting endpoint and relay/push/payment boundaries.

Ownership and funding

Ownership and funding chain

Corporate identity

Registry records; Provider statements. Not audited. Each claim links its own source. Some claims have a recorded direct primary-record retrieval; see the individual citations.

LEGAL ENTITY
SIMPLEX CHAT LTDverifiedregistry record ↗
REGISTRATION NO.
13691484verifiedregistry record ↗
INCORPORATED IN
United Kingdom (England and Wales)verifiedregistry record ↗
INCORPORATED ON
2021-10-20verifiedregistry record ↗
REGISTERED ADDRESS
20-22 Wenlock Road, London, England, N1 7GUverifiedregistry record ↗
ULTIMATE OWNER
Evgeny Poberezkin (PSC, ownership of shares 75% or more)verifiedregistry record ↗
OFFICERS
  • Evgeny Poberezkin (Director, appointed 2021-10-20)
  • Evgeny Poberezkin (Secretary, appointed 2021-10-20)
verifiedregistry record ↗
Corporate identity research · reviewed 2026-11-08

We wrote about this

Frequently Asked Questions

Is identity verification required?

No identity verification is recorded for typical use. No phone number, username, global account or document KYC required for normal messaging. Contacting support by email exposes ordinary email metadata to mail providers.

Where is it available?

Recorded availability: GLOBAL.

Is the operator based in a Five Eyes country?

Yes. The recorded jurisdiction is UK, a Five Eyes country (US, UK, CA, AU, NZ). This is jurisdiction context and does not by itself establish that a service is safer or less safe.

How are identity, operator, and evidence fields reported?

Identity exposure is level 0 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is verified evidence, last reviewed 2026-11-08, and recorded risk is caution.

Related Services

Compare

Sources and history

Terms and privacy policy

No changes to the document we watch since we started checking on 9 Aug 2026. Last checked 9 Aug 2026.

Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.