Solun · Learn
Burn-After-Read and Expiration
Why expiring links and burn-after-read reduce exposure for sensitive data.
The safest secret is the one that disappears quickly.
Expiration and burn-after-read cut down the time window where a leak matters.
Expiration windows
Short TTLs are ideal for passwords, API keys, or one-time access links.
Longer TTLs should be reserved for low-risk files where convenience matters more.
Burn-after-read behavior
Burn-after-read deletes the content right after the first successful access.
Be careful with clients that prefetch links, since they can trigger an early burn.
Operational tradeoffs
Short lifetimes require coordination. Tell recipients when to open the link.
If a link expires too early, create a new one instead of extending the old one.
Policy guidance
Teams should set defaults for TTL and burn-after-read based on risk level.
Use a documented policy so everyone shares in the same secure way.