Before you begin
Files and conversation content travel peer to peer. Each browser keeps its own local history in IndexedDB, separated by network; this is not an account-based cloud archive. A newly connected device can receive up to 100 recent public records from an available peer. Private conversations are excluded, and file or voice payloads are fetched separately when available.
A practical workflow
A record of a file is not a guarantee that the content remains downloadable after every peer leaves. Clearing site data removes the browser’s local copy, not copies already received by another device. On a public or shared computer, agree on retention and cleanup before sharing. Do not use browser history as your only record of an important project or as evidence that another recipient deleted theirs.
History that stays on your device
Messages and received files are kept in your browser’s local database, per network. Clear them whenever you like.
Questions that matter
Where is my chat history stored?
Only in the local IndexedDB database of each browser, separated by network. Nothing is uploaded. You can clear the history at any time, and clearing site data in the browser removes it completely.
Can a newly joined device see earlier messages?
When a direct connection is established, peers share up to 100 recent public records. A device that posted locally while alone can share those records when another device connects. A peer holding the history must still be available; this is not cloud backup. File and voice contents are fetched separately when available, and private conversations are excluded.
Do my messages or files pass through a server?
No. The signaling service only exchanges connection set-up data such as session descriptions and network candidates, keeps it in memory, and has no database. Chat content and files travel only over direct DataChannels. TURN relays are refused, so a server can never forward your data.
Open the page. That is the whole setup.
OKYA Share uses only standard browser technology, so there is nothing to install or configure.
- Join the same network: Connect your devices to the same Wi-Fi or wired LAN, then open share.okya.app in a modern browser.
- Devices verify each other: A lightweight signaling service introduces candidates. Automatic mode verifies a local host-candidate path; devices attested by a configured LAN node use a separate verification path.
- Share freely: Once verified, files, messages and screens flow directly between devices. Close the tab to stop sharing.
Connection and privacy
Messages and files are sent over WebRTC DataChannels, which are always encrypted (DTLS). TURN relays are disabled by design, so content can never be forwarded through a server.
If automatic local-path verification fails, Share shows a clear message instead of guessing. An optional administrator-run LAN node can attest devices separately; those attested connections may use configured STUN, but never a TURN relay. Network restrictions can still prevent a connection.