End-to-end encrypted, by default

Messages only
your phone can open.

Every message is sealed on your device before it leaves. Switch a chat to Direct and — once your contact agrees — it travels phone to phone with nothing in between. Our server introduces you, helps the connection along, and holds sealed bytes it cannot open until they're delivered. It never sees a single message.

Server can be fully compromised — no one reads your chatsDirect P2P — opt-in per chat, and only if they allow it

rian_

Connected · peer-to-peer

udah sampe rumah?
udah, aman 🔒
langsung ke hp kamu, gak lewat server
Encrypted on your device. Server saw only that you two connected.

A message leaves your phone.

Nothing on the way can read it.

It just arrives.

Design pillar

A fully compromised server still can't read a thing.

Most chat apps make the server the message bus — it sees, stores, and forwards everything. Bisiq inverts that: your phone is where messages are sealed and opened, and nowhere else. The server proves who you are, tells you who's online, helps two phones reach each other, and wakes a sleeping one. When it does carry a message, it carries a sealed envelope it has no key to — and deletes it as soon as it lands.

Every message is encrypted on your device before it leaves, with keys that never leave your device unencrypted — even if our infrastructure were seized outright, there is no plaintext to find.

The server never sees

  • Message content — ever
  • Your private keys
  • A readable message history

What it does see

  • Your username & public keys (so people can reach you)
  • That you and a contact connected, and roughly when
  • Sealed messages awaiting delivery — deleted once collected
  • Coarse location — only if you turn Near Me on

Honest limit: routing a message requires knowing who it's for, so "who talked to whom" is metadata a coordinator server can't fully hide — content is what stays private.

What you get

Built private from the ground up

Not a privacy setting bolted onto a normal chat app — the whole architecture starts from "the server should never need to know."

01 / SEALED

End-to-end encryption

Every chat is sealed on your device with modern authenticated encryption before it ever leaves. Not even Bisiq holds a key that can open it.

A message encrypting into unreadable ciphertext.
A message encrypting into unreadable ciphertext.
A message encrypting into unreadable ciphertext.
02 / DIRECT

Direct P2P connections

Switch a chat to Direct and your contact is asked to allow it. Once they do, your phones talk over a channel of their own and the server steps out of the way entirely.

03 / OPT-IN

Near Me, entirely opt-in

Discover people nearby when you choose to be visible, with ghost mode and a precision dial. Off by default.

04 / AWAKE

Offline delivery, still sealed

Contact offline? The sealed message waits in a blind mailbox we can't open, a content-free push wakes their phone, and it's deleted the moment it lands.

05 / PER-MEMBER

Encrypted group chats

Groups use the same per-member encryption as 1:1 chats — every message is sealed individually for every person in the room.

06 / YOURS

Your history stays on your phone

Chats live in an encrypted local database, keys held in your device's secure hardware. Moving phones? Transfer everything device-to-device, never through us.

Under the hood

How a message actually gets there

Bisiq delivers two ways, and they make different promises. Here is exactly what each one does with your message — including what our server holds, and for how long.

The default. Works whether or not your contact is awake.

serveryouyour contact

Encrypted on your device — the server is never given a key.

Talk privately. Starting now.

Bisiq is on Google Play today, with iOS on the way. No message of yours will ever pass through a server that can read it.

Get it on

Google Play

Coming soon

App Store

Want early access on iOS? hello@bisiq.app

Questions

Frequently asked