Encrypted message storage
Message content is stored encrypted at rest and only decrypted on authenticated server reads or controlled delivery execution.
Security
The system is designed so delivery logic, billing state, and stored message content remain separate concerns.
No Longer Here is not “secure” because of one feature. It is secure because encryption, recipient verification, billing enforcement, queue processing, and operational logging are kept explicit instead of collapsed into a single opaque workflow.
Recipient verification
Recipients can confirm identity before delivery, but they do not gain access to message content until release conditions are actually met.
Queue-based execution
Reminder and delivery work is processed through queues with retries, stale-lease recovery, and explicit status transitions rather than being mixed into normal page requests.
Audit visibility
Heartbeat events, queue rows, reminder attempts, delivery attempts, and billing events are all recorded so operational behavior can be inspected later.
Scope note
This page describes the current product security model at a high level. It is not a substitute for a formal security review, penetration testing, incident response process, or legal compliance program. Before launch, this should be expanded with real key management, provider inventory, retention policy, access controls, and operational ownership details.