Private Peer-to-Peer Text Sharing
Direct browser-to-browser. No servers. No storage. No tracking.
Most sharing tools work by sending your content through a server. You upload, the server stores temporarily, and the other device downloads. This means the service provider can see, log, and inspect everything you share. AmanMaps was built differently: your text travels directly between devices with no intermediary that can read it.
How peer-to-peer sharing works in AmanMaps
When you start a session, your computer and phone exchange connection metadata through a lightweight signaling server — think of it as a switchboard operator connecting a call. This handshake data (SDP offers, ICE candidates) is held in server memory only for the duration of the session and is deleted the moment the connection is established or the session ends.
Once the handshake is complete, the signaling server steps aside. All text content flows directly between your devices through an encrypted WebRTC data channel. The server never sees, stores, or logs a single character of what you share.
Privacy guarantees
- No content stored: Your text never touches a server. Direct device-to-device transfer.
- No accounts: No user database, no profiles, no way to identify you across sessions.
- No analytics: No tracking pixels, no cookies, no fingerprinting scripts.
- Ephemeral sessions: Refresh or close the tab and everything is destroyed. No history, no cache.
- Fragment-based key: Session keys are in the URL #fragment — browsers never send the fragment to servers.
Why this matters
Every time you use a cloud-based sharing tool, you are trusting that company with your data. They might encrypt it in transit, but they still hold the decrypted content on their servers. Peer-to-peer sharing eliminates this trust requirement entirely — the content never exists anywhere except on your devices. If privacy matters to you, this architecture is the gold standard for quick sharing.