Retention period

How it works

Privacy rules push deletion. Tax and health rules push retention. The transfer system needs a date on the object. A link expiry is not a retention period. The bytes can outlive the link.

Claims files delete at day 14 by policy. Finance files lock for seven years. The same portal stores both with different rules. One bucket policy for all files would break one of the two.

How it differs

Retention is not backup rotation, though they interact.

A user delete that beats a legal retention period is a finding.

Enforce retention in the store, not only in the UI.

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 retention period, 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 retention period 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.