Self-destructing messages: what actually gets deleted
"Disappearing" means very different things across chat apps. Some hide a message, some expire it eventually, and some genuinely remove it. Knowing which one you are using is the difference between privacy and the feeling of privacy.
Four levels of "deleted"
- 01
Hidden
The message vanishes from the interface but the row stays in the database, often indefinitely. Nothing was deleted — it was styled away.
- 02
Expired
A time-to-live marks the message as inactive and a cleanup job removes it later. Better, but there is a window where the content is still readable server-side.
- 03
Hard-deleted
The row is removed on a specific trigger. This is real deletion, though you are still trusting that it ran.
- 04
Hard-deleted and verified
After deleting, the server queries again to confirm nothing matches, logs the outcome, and shows the result. This is the level Frendko targets.
Five questions to ask any disappearing-message tool
- What exactly is deleted — the message body only, or the conversation record too?
- What triggers deletion: a timer, an action, or a background job that may lag?
- Is deletion verified afterwards, and can I see the result?
- What is kept for analytics or abuse handling — and does it include IP addresses?
- Can a third party join, be invited, or be added later?
How Frendko answers them
Deleted
Messages and the room record are both hard-deleted — there is no archived conversation object left behind.
Trigger
Timer expiry, invite expiry, or either person pressing End chat. All three run the same purge path.
Verified
The server reads back after deleting, logs the outcome to an audit trail, and shows you a receipt with the count and timestamp.
Kept
Anonymous aggregates only: counts, durations, extensions, and a 2-letter country code. No content, no codes, no IP addresses.
One honest caveat: Frendko is not end-to-end encrypted, and nothing stops the person you are talking to from taking a screenshot. Full detail lives on the security and privacy page.
No account, no install. Create a room and send the 6-digit code.
See a purge receipt yourselfCommon questions
- Do self-destructing messages really get deleted?
- It depends on the product. Some only hide the message in the app while the record stays on the server, some expire it on a schedule, and some hard-delete the row. Only the last one removes the data, and only a read-back check can show it happened.
- Are deleted messages still on the server?
- They can be. Disappearing from a screen is a client-side change; the server copy, backups, logs and analytics are separate. Ask what is hard-deleted, on what trigger, and whether deletion is verified.
- Does the other person still have my message?
- No deletion feature can stop a screenshot, a photo of the screen, or a copy-paste. Self-destructing messages reduce what a server keeps — they do not control the other human.
- What does Frendko delete when a chat ends?
- The messages and the room record are hard-deleted from the database, then the server reads back to confirm nothing remains and writes an audit entry. You see a receipt with the number of messages deleted and a verified timestamp.
- What does Frendko keep afterwards?
- Only anonymous aggregates: counts, durations, number of extensions and a 2-letter country code. No message content, no room codes, no participant identifiers, and no raw IP addresses.