One app. Private cloud. Private chat.
IDZ encrypts files & messages on your device - only you can open them.
Sign in without email or phone. No ads or tracking.
iOS, Android, Mac & Windows → https://t.co/beyI2l7MJy
#privacy#encryptedchat
Send big files. Right in chat.
With IDZ, photos, videos & PDFs go straight to your contacts, end-to-end encrypted and stored privately. No email or phone required. No ads or tracking. On iOS, Android, Mac & Windows.
https://t.co/fxKUdMnZWb
#privacy #encryptedchat
Thanks for the follow-up!
Crypto libraries: yes, we use established libraries for all cryptography (e.g., libsignal for messaging). No hand‑rolled crypto.
Linux / UNIX‑likes: no current Linux/OpenBSD builds on the roadmap, but it’s feasible if there’s enough demand. We’ll gauge interest.
Audit ETA: the review has just completed. We’re aiming to publish a public summary this month.
Key transparency: we’re finalising the approach now for delivery in Q4. We’re evaluating Signal‑style Key Transparency (immutable audit log). We may keep Safety Numbers as an out‑of‑band fallback. No blockchain‑based approach planned.
Curve choice: P‑256 (secp256r1) was chosen for legacy code compatibility. Those constraints are gone; we’re open to moving (e.g., to Curve25519/Ed25519) where appropriate. No migration date yet.
PQC: plan is to rely on a library implementation of PQXDH using CRYSTALS‑Kyber (ML‑KEM) for the KEM. SNTRUP isn’t in our current plan, but we’ll track standards and libraries.
Happy to answer anything else. Cheers!
Thanks for the follow-up!
PFS (vs. Noise): we use libsignal (X3DH + Double Ratchet). That gives forward secrecy and post‑compromise security. While we don’t run a Noise handshake, the guarantees are comparable to Noise’s payload‑security goals (confidentiality, integrity, FS/PCS).
Closed vs open source: we kept the core closed so far until we complete the crypto review. Now that it’s done, we plan to open‑source the codebase next year.
Audits & verification: the crypto review (and white‑box pentest) by Cure53 has just concluded. We do intend to publish a public summary in due course. It will be referenced/published on the website.
Safety Numbers vs Signal’s Key Transparency: we’re finalising this choice now. There’s a good chance we’ll implement a Key Transparency server; we may also keep Safety Numbers as a manual/OOB fallback. Goal: user‑verifiable identity with minimal friction.
Curve choice: we used secp256r1 (P‑256) for legacy code compatibility in an earlier project. We’re no longer constrained by that and are evaluating a move (e.g., to Curve25519/Ed25519) where appropriate. Note that libsignal already uses X25519 for the messaging protocol.
PQC: our plan is to follow Signal’s work on post‑quantum ratchets (SPQR) and adopt their primitives as they land upstream, i.e., a hybrid with a NIST PQ KEM (e.g., ML‑KEM/Kyber) and complementary PQ signatures as the ecosystem stabilises.
Let me know if you have any further questions :)
🔐 No tracking. No profiling.
IDZ seals every file and message before it leaves your device.
No email or phone number at sign-up. No ads. No trackers.
One app for secure cloud + encrypted chat on iOS, Android, Mac & Windows.
Try it free: https://t.co/e1sqQmH0r4
Thanks for the thoughtful questions!
Primitives & stack:
ZCloud: ChaCha20‑Poly1305 (AEAD).
Auth/sharing: ECDSA + ECIES on NIST P‑256.
KDF: HKDF. Hash: SHA‑256.
Master‑Key QR: BIP‑39.
Codebase: clients in Flutter/Dart; backend in Python.
PFS (messaging):
ZChat uses the Signal Protocol (X3DH + Double Ratchet), not Noise. This provides forward secrecy and post‑compromise security. It also mitigates KCI via ephemeral DH, signed pre‑keys, and authentication checks.
Noise mapping:
We don’t implement a Noise handshake, but Signal’s session gives comparable payload‑security properties (confidentiality, integrity, FS/PCS).
Storage vs. chat:
ZCloud (encrypted storage) uses symmetric AEAD at rest; PFS doesn’t apply to stored files by design. Keys are derived with HKDF.
Cryptography audit & a white‑box pentest by Cure53 has been completed.
Server trust model & key transparency:
Chat is end‑to‑end encrypted. Safety Numbers (for out‑of‑band key verification / key transparency) are planned for v3.5.0 (Q4 2025) to make identity verification user‑verifiable.
I hope you found this helpful, but let me know if you need any further information!
@unixpill Totally fair ask. Security deserves specifics. Our site/FAQ explains things in plain English for everyone, but we’re happy to go deep. What would you like to know? We are happy to share details here.
Private by default.
IDZ encrypts files & chats on your device, only you can open them. Sign up without email or phone number. No ads or tracking.
On iOS, Android, Mac & Windows.
https://t.co/e1sqQmHygC
#privacy#encryption
Keys stay on your device. Zero-knowledge by design. No tracking or profiling.
IDZ = private cloud + encrypted chat.
https://t.co/e1sqQmHygC
#privacy#encryption
IDZ keeps your documents encrypted and easy to find across all your devices. Move your sensitive files to a place built for privacy.
Sign up today: https://t.co/e1sqQmHygC
🛡️ Create your ID without giving up your identity.
No names, no numbers, no tracking - just pure privacy with IDZ.
Start now → https://t.co/e1sqQmH0r4
#StayAnonymous#PrivacyFirst
IDZ locks every file & message before it leaves your phone.
No emails. No passwords. Zero trackers.
Private storage & secure chat - download now ➜ https://t.co/fxKUdMnZWb
#PrivacyFirst #ZeroKnowledge
🔐 Secure Cloud. Encrypted Chat. True Privacy.
IDZ encrypts every file & message on your device before upload. No emails, phone numbers, ads, or trackers. Your keys, your control.
Download it free at https://t.co/fxKUdMnZWb