--- title: "Every route a file can take · Privatta" description: "Phone or computer, same office or the other side of the world: the file makes the same short trip, from your device to theirs." url: "https://royalsoftworks.com/products/privatta/routes/" source: "https://royalsoftworks.com" format: "markdown" note: "Markdown rendering of the HTML page at `url`. Same content, same canonical URL." --- Privatta · 1 of 4 # Every route a file can take. Phone or computer, same office or the other side of the world: the file makes the same short trip, from your device to theirs. Every route · Local + Remote ## Phone to laptop. Laptop to phone. Anywhere to anywhere. Windows or Linux on one side, the phone in your pocket on the other. In the same office or on the other side of the planet, the file takes the same short trip: from your device to theirs, with nothing in between. MobileDesktop DesktopMobile MobileMobile DesktopDesktop Local Remote A file travels directly from a mobile device to a desktop device, over the local network, with no server holding it. SAME NETWORK · FROM A DESKTOP, NO INTERNET INVOLVED To Mobile To Desktop From Mobile Mobile → Mobile Local Remote Mobile → Desktop Local Remote From Desktop Desktop → Mobile Local Remote Desktop → Desktop Local Remote 8/8 Two device families, two directions, two distances — every combination works. When the phone is the one sending, it connects with a one-time key, so it needs the internet even inside the same building. For your IT team - **Transport** — Across the internet, and whenever the phone is sending: a WebRTC data channel with DTLS encryption, negotiated directly between the two devices. From a desktop on the same network: HTTPS (TLS) straight to that machine - **Pairing** — QR scan on the LAN; across the internet, a single-use 32-char connection key (5-minute expiry) plus a 6-char security code sent by a different route - **Pull-only** — Every route is pull-only — the receiving device requests each file; no push path exists in the protocol - **NAT** — Internet connections are found with public STUN servers and no relay ever carries the file, so two devices that are both behind strict (symmetric) NAT cannot reach each other If both ends run Privatta, the route exists — and nothing sits in the middle. [Buy Privatta](https://royalsoftworks.com/pricing/#subscriptions) [Pick your edition](https://royalsoftworks.com/products/privatta/editions/) [![Privatta - Share files securely, machine to machine, locally | Product Hunt](https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=1193785&theme=light&t=1784490042426)](https://www.producthunt.com/products/privatta?embed=true&utm_source=badge-featured&utm_medium=badge&utm_campaign=badge-privatta) [![Smol Hunt Top 2 Daily Winner](https://r2.direasy-multi-tenant.focusapps.app/uploads/616d0b1a-3979-4b8c-94d1-b4f1fedd3ead/1783046772211/bzmx0zi15su/top2-light.svg)](https://smolhunt.com/projects/privatta) [Previous Privatta overview](https://royalsoftworks.com/products/privatta/) [Next Why the file stays yours](https://royalsoftworks.com/products/privatta/why-it-stays-yours/)