Logs with personal data should not accumulate indefinitely
Email delivery logs contain recipient addresses, event types and timestamps. Retaining them forever without a policy is a privacy risk.
Logs, retention and privacy
else.events logs delivery events per email send. Retention periods are configurable by plan — short enough for privacy, long enough for debugging and support.
Email delivery logs contain recipient addresses, event types and timestamps. Retaining them forever without a policy is a privacy risk.
"Did the customer receive the billing email?" is unanswerable without delivery logs. Support teams need a short, structured log window.
GDPR-aware teams need to be able to state how long email metadata is retained and why. "Forever" is not a valid answer.
DSAR (Data Subject Access Request) responses are simpler when email log retention is time-bounded and predictable.
Basic plans retain logs for a shorter period. Pro and Premium plans allow longer retention for compliance and audit needs.
else.events logs event type, recipient address, delivery status and timestamp — not the full rendered email body by default.
Every log entry links an incoming event to its resulting email send and delivery status. Useful for support ("the invoice email was delivered at 14:03") and debugging.
If a user requests data deletion, their delivery log entries can be removed within your configured retention window.
Debug failed sends, answer support questions and keep personal data bounded — all with configurable retention.