BURN IN OYA
Disappearing messages, with Burn.
Not every exchange needs to become a permanent conversation history. Burn is OYA’s deletion mechanism for disappearing messages. Here is what it does, when it happens and what it cannot guarantee.
Three things to understand
Read
View the message you have received.
Decide
Saving within OYA depends on permissions and the participants’ agreement.
Finish
Without agreed saving, the flow can trigger Burn.
When does a message disappear?
Opening a message does not mean that all its content is instantly erased everywhere. For a disappearing message that has not been retained, closing it or moving to the reply flow can trigger Burn. You can also trigger Burn without replying, using the gesture shown in the app.
Text messages, voice notes and attachments have different viewing flows. Follow the on-screen instructions rather than assuming one timer applies to every kind of content.
Saving content is a shared decision
Saving offered within OYA requires the sender’s permission and the recipient’s agreement. A pending request is not yet consent. A refusal does not authorise saving the content within OYA.
Depending on the content and flow, the sender may offer saving before sending or receive a one-off request. Passport preferences affect the options offered. Check that the app actually confirms saving before relying on a retained copy.
Local reply context, not a full conversation history
After a reply is sent, an ordinary text can be used as a local reminder when the next message from that contact opens. It is replaced after the next reply; no conversation history is displayed on the profile.
This reminder excludes Moscow Mode messages, voice notes and attachments. Distinguish between burning the message, this local context aid and explicitly agreed saving.
If the connection is interrupted
When a Burn is queued on this phone, the message is hidden locally to prevent it from appearing again. Server confirmation is retried during a later synchronisation.
Disappearance from the screen does not prove that the server has already completed the operation or that every other device has synchronised.
Limitations you should know
When the server operation succeeds, Burn removes the encrypted content from the message row. It does not guarantee irreversible erasure of every copy: metadata, relay envelopes, backups or temporary content in memory and cache may remain.
A photo of the screen taken with another device, a copy already saved or a file exported to another app is outside Burn’s control. Deleting a message is not the same as deleting your account.
Burn is a deletion mechanism, not a promise of “zero traces”. Only share sensitive content with a recipient you trust.
Read the privacy policy (French)
Questions about Burn
Does Burn delete a message as soon as I read it?
Reading alone does not prove immediate erasure everywhere. The trigger depends on the flow and any agreed saving; follow the instructions shown in OYA.
Can a message be kept?
Yes, when the saving flow supports it and the required permissions and agreement are in place. Wait for confirmation that it has been saved.
Does Burn prevent every screenshot or copy?
No. It cannot stop someone photographing the screen with another device or remove copies held outside OYA.
Does Burn erase every backup?
No. Burn is not a guarantee of immediate erasure of backups, metadata or relay envelopes. Read the privacy policy for retention limitations.
Oya!