Short answer: keep every receipt export private, issue a short-lived presigned GET link for each download, and delete the stored file on a policy-driven schedule of at least one day rather than treating link expiry as deletion.
That distinction is the design. A property manager may need a CSV today, while an auditor may need the original PDF months later. The URL's lifetime controls access through one link; the object's retention period controls how long the evidence exists. Mixing those clocks can either expose a tenant document for too long or destroy an audit record too early.
Keep it private.
Give the receipt four explicit states
A useful receipt pipeline has four states: the export job owns a unique object key, the generated file is uploaded with private access, an authenticated application request obtains a temporary download link, and a lifecycle rule eventually removes the object.…