Privacy Policy

1. There is no account, so there is no account data

MeshLine.net doesn't ask for an email address, phone number, or password. When you join, a random display handle and a local cryptographic node key are generated in your browser. Neither is sent to, or stored on, any server we operate — because we don't operate one.

2. What lives on your device

Your chosen handle, your local room bookmarks, and your message history are stored in your browser's IndexedDB, on your own device. Clearing your browser data or closing a private/incognito tab removes it. We have no copy of it elsewhere, because messages never pass through a server we control.

3. What peers can see about each other

Because MeshLine.net connects browsers directly, the trade-off for having no middleman is that peers see more of each other than they would through a managed service:

• Your IP address is visible to any peer you connect to directly over WebRTC, the same way it would be on a direct video call.
• Public room membership and presence are visible to anyone else in that room.
• Direct messages are sealed with end-to-end encryption, but the fact that two handles are connected is not hidden from the discovery layer.

4. Discovery trackers and fallback relays

To find other peers, your browser announces a room identifier to public WebTorrent trackers, and — if a direct connection can't form — to a Nostr relay used as a fallback signaling path. These are third-party infrastructure we don't control; they can see that a node with your session's temporary identifier is looking for peers, but not the content of your messages.

5. Age requirement

MeshLine.net requires users to confirm they are 18 or older before joining. This is self-reported at join time; we have no independent way to verify age given the absence of accounts, and we don't retain the value you enter beyond your local session.

6. Cookies and analytics

MeshLine.net does not use tracking cookies or third-party analytics scripts. Local storage is used only to persist your own session and preferences on your own device.

7. Changes to this policy

If this policy changes, the updated version will be posted on this page with a new "last updated" date. Since there are no accounts, we have no way to notify you individually.

8. Contact

Questions about this policy can be directed to the project maintainers through the repository listed in the footer of this site.