Privacy Policy

Overview

We do not run a message database. Chats exist only for the live session on an encrypted WebRTC data channel between devices.

Room links use a random session code — anyone with the link can try to join, so share only with people you trust.

A short signaling handoff helps peers find each other. Chat content never lands on, or sticks around on, BurnTlk servers.

What we do not collect

BurnTlk is built so we do not collect, log, or store IP addresses, user identities, account profiles, or chat content. There is no user database and no message archive operated by BurnTlk.

Peer-to-peer architecture

Conversations ride standard WebRTC peer-to-peer data channels between participants’ browsers. Payloads go device to device and are not written to BurnTlk servers.

Because of that design, BurnTlk has no technical ability to monitor, intercept, record, or hand over chat content. We cannot pull messages from a session that has already ended.

Session links & signaling

Joining needs a room link or code from someone already in the session. Share those only with the people you mean to talk to.

Temporary signaling may be used only to set up the peer connection. It does not store conversation content.

Local device data

Your browser may keep preferences (like theme or language) on your device. Session counters or similar non-personal metrics, if shown, never include message content or identity profiles.