What burn-after-read means
Burn-after-read means the secret is destroyed after it is opened. In the simplest version, a link works only once. After the first successful view, the server removes the stored ciphertext so the same URL cannot be used again.
That approach is helpful when you want to send something sensitive through a channel that may be logged or forwarded, such as email, chat, or a ticketing system. Even if the link is copied, the underlying secret is temporary.
When to use read limits
One-time access is the strictest model, but it is not always the best one. Sometimes a team member needs to open a secret more than once during a short handoff. In that case, a small read limit such as three or five opens can be a better fit.
The right choice depends on the risk you are trying to control. If you are sending a temporary password or a recovery code, one read is usually enough. If you are distributing a deployment key to a tiny team, a small limit can make the flow easier without making the secret permanent.