How PocketTransfer keeps your files on your own network
Short answer
Files move directly between your iPhone and your computer over your local network. They never pass through a PocketTransfer server: there is none. Each computer needs your approval, and your iPhone asks before anything is saved.
The connection uses local HTTP without encryption, so use it only on a private Wi-Fi network you trust.
No encryption. PocketTransfer uses local HTTP without encryption. Other people on the same network can see the data being sent. Do not use it on a public or shared Wi-Fi network.
What protects a transfer
-
No PocketTransfer server
Your iPhone itself serves the page you open in the browser. Your files never pass through a PocketTransfer server: there is none.
-
A code for each computer
The iPhone shows an 8-digit code. Type it in the browser, check that the same code is shown, then tap Approve on the iPhone. Codes expire, and a code is canceled after 5 wrong attempts.
-
Your iPhone asks before saving
When a computer sends files, the iPhone shows their names and asks you to Accept or Decline. Nothing is saved until you accept.
-
No account
No account and no sign-in, on the iPhone or on the computer.
-
Only while the app is open
Keep PocketTransfer open until the transfer finishes. Locking the screen or switching apps disconnects the browser, so the connection ends when you leave the app.
What to do
- Use a private Wi-Fi network you trust, such as your home network.
- Tap Approve only if the code in the browser is the same as the code on the iPhone, and only for a computer you recognize.
- Check what the iPhone asks you to accept before you tap Accept.
- Guest and public networks are a poor fit. They also often keep devices apart.
What is outside the connection
Free mode shows ads from Google AdMob, and Premium is bought through Apple, so those use Google's and Apple's servers. Neither is used for your files. PocketTransfer asks for tracking permission only for personalized ads. This website uses no cookies and no analytics. Read the Privacy Policy.
Related pages
Last updated