Local does not mean encrypted.
Nearby LAN chat, files and AI can use direct local TCP paths. Do not assume every payload has end-to-end encryption. Use networks and devices you trust. WebRTC transport has separate security.
KNOW WHAT YOU SHARE.
Connecting devices is useful. Understanding the connection is just as useful. This page explains the project’s data paths and permission boundaries.
MAKE SHARING INTENTIONAL
Nearby LAN chat, files and AI can use direct local TCP paths. Do not assume every payload has end-to-end encryption. Use networks and devices you trust. WebRTC transport has separate security.
Supported capture and streaming features require the relevant operating-system permission and device-owner approval. Screen sharing has a separate capture flow. Stop sessions when done.
Nearby AI sends your request to the selected host’s configured engine. A cloud provider may receive prompts if that host is configured to use one. Choose the host and engine deliberately.
Optional Firebase RTDB carries discovery, presence, pairing and signaling data. The public source supplies no shared maintainer backend. Production deployment needs authentication and appropriate database rules.
LOCAL DATA & DEVICE ACCESS
READ THE IMPLEMENTATION
The source and current release notes explain implementation details and known limits. This overview is not a claim that every transport is private or every background delivery case is solved.
YOUR NEXT CONNECTION STARTS HERE.
For Android & Windows. Built in the open.