Use short-lived signed links only after the API has authorized the export, selected its fixed storage region, and confirmed that retention has not expired. The browser can then move a large PDF or supporting media directly to or from object storage; the application handles control data, never the file bytes. The hard part isn't signing. It is making deletion state observable enough that an expired fintech export cannot quietly remain downloadable.
Delivery model Pick this when Retention consequence Main operational signal
Application proxy Files are small or every byte must pass an inspection layer One enforcement point, but application capacity scales with transfer volume Proxy duration and aborted-transfer rate
Signed object-storage URL Large exports and evidence media should bypass the application The API must check policy before every signature, while storage lifecycle rules provide a backstop Sign decisions by region and policy result
Managed download gateway Central policy or detailed download…