Security and privacy

Private messaging on open infrastructure.

DinoX combines XMPP federation with local database encryption, encrypted file storage, OMEMO, OpenPGP interop and optional Tor routing.

Protection layers

Security features are explicit and inspectable.

Local data encryption

Accounts, messages, settings and cached metadata are stored in an encrypted SQLCipher database. Local media caches are encrypted separately.

OMEMO and OpenPGP interop

OMEMO supports legacy namespace and OMEMO 2 paths. OpenPGP support exists for legacy and experimental XMPP compatibility, not as a claim of formal spec maturity.

Optional Tor routing

Tor and Obfs4proxy support are optional privacy tools for accounts and workflows that need them.

Panic wipe

A panic wipe action can remove local DinoX data and app-scoped OpenPGP material when immediate cleanup is required.

DinoX backup and restore screen

Data ownership

Designed for users who manage their own communication.

DinoX keeps privacy controls visible: read receipts, typing notifications, account routing, certificate trust and backup workflows are user-facing settings.