Messages that delete themselves.
Send a note or message with a built-in expiry. Khamli turns it into a 4-character code and permanently wipes it when the timer runs out — no account, no trace.
What self-destructing messages are
A self-destructing message is text that is designed to disappear after a set period. Unlike a normal chat message — which lives in a thread, on a server, or in a backup indefinitely — a self-destructing message has a hard expiration after which it is permanently deleted.
The idea is to shrink the window in which a message can be read, copied, or leaked. What used to linger forever now exists for minutes or hours, then is gone.
How Khamli implements it
When you send a message on Khamli you choose an expiry: 30 minutes (the default), 2 hours, 12 hours, or 24 hours. The text is stored in a Neon PostgreSQL database and hard-deleted — not archived, not soft-deleted — once that timer runs out. The 4-character code that mapped to your message is removed at the same time.
Important: Khamli deletes on a timer, not on first read. The recipient can open the message more than once while it is live.
When to use one
- Sharing a temporary link or access code that shouldn't persist.
- Sending a quick note to someone you don't want to add to your contacts.
- Passing a code snippet, address, or detail you'd rather not leave in a chat log.
- Any one-way handoff where permanence is a liability, not a feature.
What it is not
Khamli's messages are encrypted in transit (HTTPS/TLS) but are not end-to-end encrypted, and they are not “burn after reading” — the recipient can reopen them until the timer expires. Anyone with the code during that window can read the message, so share the code carefully and avoid sending credentials or illegal content.
Frequently asked questions
What is a self-destructing message?＋
It is a message that is automatically and permanently deleted after a set amount of time — in Khamli's case, 30 minutes to 24 hours, chosen when you send.
Does the message delete after one read?＋
No. Khamli deletes the message when its timer runs out, not on first read. During the window the recipient can open it more than once. If you need strict burn-after-reading, this is the key difference to understand.
How do I send a self-destructing message?＋
Type your message, choose an expiry (30 min / 2 hr / 12 hr / 24 hr), and send. You get a 4-character code to share. When the timer ends, the message is hard-deleted.
Can the recipient see the message after it expires?＋
No. Once the timer runs out, the code stops working permanently and the message is deleted from the database. Entering an expired code returns nothing.
Is Khamli end-to-end encrypted?＋
No. Traffic is encrypted in transit over HTTPS (TLS), but Khamli does not apply client-side end-to-end encryption. The message is stored on the server until its expiry.
Send a message that deletes itself.
Share with Khamli