Prepare the package before choosing a delivery method
Start with the version the client is meant to receive. Open the documents, check the dates, and remove unrelated material from the selection. A useful transfer title describes the purpose of the package without exposing unnecessary sensitive details on a nearby screen. If the meeting produces another revision, make it clear which package replaces the earlier one. Sending quickly does not help if the recipient leaves with the wrong files.
Decide who should receive this copy
The person in front of you may be the intended recipient, an assistant collecting documents, or a colleague using a shared phone. Ask which account should receive access and whether the person is authorized to take the files. Check the displayed account before sending. A familiar device name can help you locate a phone, but the name alone is not a reason to trust it. In a group meeting, make a separate access decision for each recipient.
Use a short checklist while you are together
Agree on the handoff before either person taps Send. The following questions work whether you are using an account invitation, a secure link, or a supported in-person sharing flow.
- Is this the final package, and does its title match what we discussed?
- Is this the account or device that should receive it?
- How long will access be needed, and when should the recipient download the files?
- Can the recipient open the package now, or should we arrange a later check?
- Who should they contact if the access window closes before they finish?
Choose a delivery path that works today
ZipPigeon’s website already supports encrypted transfers with account recipients or secure links. An account invitation can suit a known repeat recipient. A secure link can be practical when that person needs a different access path, but anyone who obtains the full link and its decryption key may be able to use it within its limits. Send it through an agreed channel, check the destination, and avoid pasting it into a room-wide conversation just to save a few seconds.
What Nearby is intended to simplify
ZipPigeon Nearby is coming soon in compatible iOS apps. Both people will use a signed-in, unlocked workspace and opt in to sharing. They will select a participating device, confirm the account and pairing code on their first connection, and exchange an offer that the receiver must accept before access is released. A valid remembered pairing can remove the repeated code comparison on later visits. Public browser Nearby controls are planned for after app-store availability; there is no announced release date.
Leave time for the actual download
An accepted offer and a downloaded file are different outcomes. Nearby uses ZipPigeon’s encrypted upload and delivery service, so both people need internet access even when they are in the same room. A weak connection at reception may delay the upload or the receiver’s download. If the appointment ends first, agree on how you will confirm completion. Do not tell the client that the files are on their device just because access was delivered.
Close access deliberately, without promising to erase copies
Choose an expiry that leaves enough time for the task, then review transfers that no longer need to stay open. Revocation and expiry can stop future service access; they do not recall a document that has already been downloaded, photographed, or copied elsewhere. For material that needs a specific retention policy, agree on that policy with the recipient. A controlled handoff helps establish the boundary, while the recipient remains responsible for the copy they keep.