Safe & Private Sharing

Safe & Private Sharing

Sharing a file takes ten seconds; un-sharing it can be impossible. This topic is about keeping control after you press send: password-protecting a file before it leaves your device, links that expire on their own, the real difference between a public link and a restricted one, and the habit of checking who still has access to what you shared months ago. None of it needs specialist software — it needs the right settings, chosen in the right order, before the file goes anywhere. Everything here is written for ordinary files and ordinary services — the same Drive, Dropbox and email accounts you already have — not for enterprise security departments.

Guides in this topic

Guides in this topic

The three controls that matter

Safe sharing rests on three controls, and every guide in this topic is really about one of them. The first is a password — ideally on the file itself, so protection travels with it wherever it gets forwarded. The second is expiry: a link that stops working after a few days cannot be rediscovered in an old inbox next year. The third is revocation: the ability to see who has access and remove it, which only exists if you shared with named people or through a service that keeps an access list. A public, permanent, unprotected link has none of the three — which is fine for a restaurant menu and a poor idea for a passport scan.

Safety is a sequence, not a setting

The order matters as much as the tools. Protect the file first, then choose the channel, then send the password through a different channel than the file itself — a password in the same message as the file protects nothing. Confirm the recipient got it, and when the job is finished, close the access instead of leaving it open out of politeness. The pillar guide in this topic turns that sequence into a checklist you can run through in a minute, and the focused guides cover each step in depth: passwords per file format, encryption in plain words, expiry settings service by service, and the special care that identity documents, contracts and tax papers deserve.

One honest limit applies to every method in this topic: no setting can control a copy someone has already downloaded. Revoking a link stops future access; it does not reach into a laptop across town. That is why the guides keep returning to the moment before sending — checking the recipient, choosing the least access that does the job, and asking whether the file needs to travel at all. Prevention is the strong control here; everything after the download is damage limitation, and it is better to know that plainly than to trust a setting to do something it cannot.