Most transfers go straight between devices. When a network blocks that, peeza's relay carries encrypted bytes it has no key for (one exception, when you ask for it). It never keeps them.
peeza runs one small server, the relay. It has two jobs. First, it helps two devices find each other and agree how to connect. That part is tiny and always free.
Second, when a direct connection is impossible, it forwards the transfer byte for byte. That happens behind a strict NAT, a corporate firewall, or a hotel or guest network that blocks device-to-device traffic.
direct your device ═══════════════════════▶ their device free, never counted relayed your device ══▶ relay (blind) ══▶ their device counts toward your relay nearby your device ══ same network ═══════▶ their device no internet at all
peeza always tries direct first. The relay is the fallback. Nearby transfers never touch the internet.
A direct transfer never touches our servers. It costs nothing, to us or to you. It is never counted, whatever its size or how often you send.
A relayed transfer goes through a server we pay for by the gigabyte. That is the one thing peeza meters: only the bytes that went through the relay. The app shows your relay use this month.
Every transfer is encrypted on your device before it leaves. The relay does not receive the key, with one exception, when you ask for it. You trust our servers in two places: the web page that decrypts in a browser and the first key for a new device.
#, which browsers never send. To your own machines, it's sealed to the receiving device's own key.To route and meter transfers, the relay sees metadata: which devices talk, their IP addresses, when, and how many bytes. For a connected account, also file names, in your dashboard and teams. Never the contents. Full list: what the relay sees. Mechanics: the tech page. Exactly what the relay stores: the privacy policy.