A marketplace that retains signed documents has two different clocks: the access-control clock (who may read an object now) and the deletion clock (when it must disappear). Treating a user folder as both creates a quiet compliance failure. Short answer: keep authorization in Node.js and Express, keep each object private under a tenant-scoped key, record delete_at in a database, and use lifecycle automation as a backstop that you can observe.
The field guide: which retention shape fits a marketplace?
Retention shape Pick this when The catch
Application worker Signed documents have individual legal or contractual deadlines Retries, leases, idempotency, and audit events become your responsibility
Object-storage lifecycle Every object under a prefix shares one age rule A timer cannot see a revoked tenant, a dispute hold, or a database exception
Hybrid policy Most generated images expire uniformly, with occasional holds Two clocks must agree, and their disagreement needs an alert
For per-user AI images, the…