Sender Pod
The sender chooses a file and addresses the transfer to the receiver’s PodID.
Released in v2.0.8-Stable
Pod-to-Pod
A released desktop feature for users and businesses to transfer data directly between each other’s pods, without storing the file on a central cloud server or relying on an email address as the identity anchor.
No central database
Transfer to the PodID, not to another vulnerable inbox.
Pod-to-Pod is built around a simple idea: the receiver’s PodID remains the stable destination. If a user changes their email address, the PodID can still identify the pod, so file transfer and trusted data exchange can continue without rebuilding the relationship around a new inbox.
Instead of parking sensitive files on a central online server, the transfer is addressed from one pod to another. PokoPod should not need a central database of the file contents to make that exchange useful.
Peer-to-peer direction
The goal is direct pod-to-pod exchange wherever possible: less cloud custody, fewer standing copies, and a smaller target for attackers than traditional server-hosted file sharing.
Transfer flow
Address, verify, transfer.
The desktop client already frames Pod-to-Pod around receiver Pod IDs, generated transfer tickets, a shared 4-digit safety code, and encrypted background transfer.
Safety Check
Both sides compare a shared 4-digit safety code before accepting the transfer.
Receiver Pod
The receiver accepts the ticket and the encrypted background transfer completes between pods.
What this enables
For people and businesses that need data without cloud sprawl.
Stable PodID
The relationship can be anchored to a PodID rather than an email address, so communication can survive email changes.
Peer-to-peer exchange
Sensitive data can move between pods without becoming a standing copy in a central PokoPod cloud database.
Ghost Mode and trust
Trusted sender controls and non-discoverable modes can help users decide who is allowed to initiate transfers.
Privacy posture
Designed to reduce server-side exposure.
Traditional file sharing often leaves data on a service provider’s server, inside a company inbox, or in a cloud link that can be forwarded, indexed, breached, or forgotten. Pod-to-Pod aims to reduce that exposure by making the pod itself the destination.
No central file storeThe design goal is no persistent PokoPod-hosted copy of the transferred file.
No email dependencyThe PodID can remain stable even if the user changes email address.
Direct relationshipBusinesses and users can exchange data pod-to-pod instead of through a central database.