Classify the file first
A public brochure and an employee tax document do not deserve the same workflow. Before selecting a service, decide whether the file is public, internal, confidential or legally regulated. This classification tells you whether a public bearer link is acceptable, whether named-user access is required and whether the file should be shared at all.
Make a smaller copy whenever possible. A cropped screenshot may be safer than an entire dashboard export. A redacted extract may answer the question without exposing the rest of a report. Check that redaction removes underlying text and comments rather than merely placing a black shape over them.
Understand the access models
Bearer links
An unlisted or secret URL grants access to whoever possesses it. It can be forwarded, pasted into the wrong chat, stored in browser history or recorded by a corporate proxy. A long random token makes guessing difficult, but it does not stop copying.
Named-user access
Requiring an account can limit access to specific identities and produce an audit trail. It also introduces account recovery, offboarding and permission-management work. Review group memberships rather than assuming the original invite list remains correct.
Encrypted archives
A well-encrypted archive can protect the file after download, but only if the password is strong and sent through a different channel. Do not put the password in the same message as the link. Encryption does not conceal filenames and sizes in every archive format, and it does not revoke copies already downloaded.
Set a real lifecycle
Expiry should match the task: hours for a one-time handoff, days for a review cycle, or a documented longer period for shared project material. Verify whether “expiry” disables only the link or deletes the stored object. Deletion policies, backups and legal holds may keep a copy after the interface says the item is gone.
The NIST security and privacy controls catalogue provides a broad framework for access control, audit and information handling. For services that accept uploads, the OWASP File Upload Cheat Sheet explains why type validation, storage separation and malware defences matter.
Use a repeatable handoff
- Confirm the intended recipient through a known channel.
- Create a minimal, clean copy and remove metadata.
- Choose named access for sensitive material; avoid anonymous public links.
- Set the shortest practical expiry and disable resharing where possible.
- Send any password separately and ask the recipient to confirm receipt.
- Revoke the link after the task and record any required retention.
No control can retrieve a copy that a legitimate recipient has already saved. The goal is to reduce accidental exposure, keep access proportionate and make the end of sharing as deliberate as the beginning.