Before you begin
Public sharing is for the connected room, not for everyone on the internet. It still reaches other verified devices on that local network, which may be more people than you intend. Open the intended device’s profile and start private sharing when the content is for one recipient. Check the active conversation immediately before selecting a file or starting a screen share.
A practical workflow
Private conversations keep their messages and file lists separate and are excluded from public-history replay. They do not stop the recipient saving, photographing or forwarding content. Device names can be edited, so confirm the intended person through a known channel when the material matters. Encryption protects the transport; it does not make an untrusted recipient trustworthy.
Private device-to-device sharing
Open a device’s profile to start a private conversation. Messages, files, voice notes, screens and whiteboards go only to that device, with a separate file list.
Questions that matter
What is the difference between public and private sharing?
Public sharing reaches connected devices on the current network. Click a device avatar, then choose private sharing to send only to that device. Each conversation has its own messages and file list. Private messages and files are not included in public history or file catalogs.
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.