Private file sharing

How it works

The file stays in the owner's store. Recipients authenticate. A download makes a copy revocation will not reach. Sharing without an identity check is public sharing with a softer label.

A project folder admits four emails. Removing one email stops the next open. The file they downloaded yesterday remains on their laptop. The owner deletes the live object and the other three lose access too.

How it differs

Private sharing is not a one-time transfer. Updates are visible. A sent ZIP is not.

A link set to anyone-with-the-link is not this term.

Check the share dialog before you send.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For private file sharing, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive private file sharing files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.