An active reservation can receive without a browser or dashboard session. At
expires_at, the address stops being a usable active API resource and is not revived.
Every message read checks the message’s own expires_at. Logical expiry hides metadata and bytes even if queue retries or physical storage cleanup are delayed. Duplicate inbound delivery processing never extends retention.
The public v1 API intentionally has no delete endpoint. Short-lived content expires automatically, while the issued address remains reserved from future reallocation.