Short answer: keep receipt exports private, then hand the browser a short-lived presigned GET URL; delete the object with a lifecycle rule after the audit window. A permanent public URL is the wrong default for a fintech export.
Decision matrix for receipt export links
Option Retention control Browser download Operational cost
Private bucket + presigned GET Strong; expiry and lifecycle are explicit Works without exposing the bucket A small signing service and cleanup policy
S3 presigned URL Strong; mature IAM and lifecycle controls Works well AWS-specific configuration and credentials
Cloudflare R2 presigned URL Strong; useful with an R2 account Works well R2 and egress choices shape the bill
Backblaze B2 signed URL Good for download workflows Works, with B2-specific APIs Less broad ecosystem than S3
For a Node.js service exporting CSV, PDF, or ZIP receipts, I would choose the first row and keep the storage contract behind a tiny adapter.…