Sender Pod
The sender chooses a file and addresses the transfer to the receiver’s PodID.
Released in v2.0.15-Stable
Send files straight from one trusted Pod to another. Pod-to-Pod helps people and businesses exchange data without dropping every file into another shared cloud folder.
Direct sharing
Email addresses change. Inboxes get messy. Links get forwarded. Pod-to-Pod is designed around a stable PodID, so a trusted transfer relationship can continue even if someone changes their email address.
The plain-English goal is simple: get the right file to the right pod with fewer standing copies left behind on other services.
Direct pod-to-pod exchange means less cloud custody, fewer forgotten copies, and a smaller target than traditional shared file links.
Transfer flow
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.
The sender chooses a file and addresses the transfer to the receiver’s PodID.
Both sides compare a shared 4-digit safety code before accepting the transfer.
The receiver accepts the ticket and the encrypted background transfer completes between pods.
What this enables
The relationship can be anchored to a PodID rather than an email address, so communication can survive email changes.
Sensitive data can move between pods without becoming a standing copy in a central PokoPod cloud database.
Trusted sender controls and non-discoverable modes can help users decide who is allowed to initiate transfers.
Privacy posture
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.