Confidential file transfer

How it works

Confidential is a handling label. The mechanics are private access, encryption, a short link window, and a delete date. A public link with a long random path is obscurity, not this label.

HR sends a 15 MB compensation file to two named accounts, expiry 48 hours, lifecycle delete on day seven. A forward by one recipient downloads once. The other account is disabled the same day. The log shows both events.

How it differs

Confidential is not a protocol. The same SFTP server can carry public builds and this file. The folder policy differs.

A preview service that renders the file on a third-party domain is another copy.

Disable preview for this class.

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 confidential file transfer, 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 confidential file transfer 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.