Built for EU-based SaaS teams

Transactional email that helps you handle GDPR considerations

else.events is hosted in the EU, gives you control over log retention periods and lets you choose your email provider — so you can make informed decisions about where data lives.

GDPR compliance is harder when your email stack is scattered

Email logs stored indefinitely by third-party tools

Marketing platforms and email services often retain logs and content far beyond what your privacy policy states. You have limited control.

Recipient data flows through multiple vendors

When you use separate tools for sending, templating and tracking, recipient email addresses and payload data flow through each one.

No audit trail for transactional sends

Support teams ask "did this user receive the billing email?" — but without structured logs, there is no reliable answer.

Provider lock-in limits your choices

Switching to a provider with better EU data handling means rewriting your email integration from scratch.

One layer that keeps email infrastructure simple and auditable

EU-hosted infrastructure

else.events runs in the EU. Events, templates and logs do not leave EU infrastructure by default.

Configurable log retention

Set how long email logs are kept per plan. Shorter retention for logs that contain personal data where your privacy policy requires it.

Provider-agnostic — bring your own Postmark, SMTP or Resend

Use a provider with EU data processing agreements. else.events routes through your chosen provider — no vendor lock-in.

Minimal payload principle

Only include the data your template actually needs in the event payload. else.events does not enrich or store data it does not receive.

What else.events does — and does not — promise on GDPR

What we do

EU hosting, configurable retention, provider choice, structured delivery logs, DPA available on request.

What we do not claim

We do not claim "full GDPR compliance" on your behalf. Compliance depends on your entire stack, your privacy policy and your legal context. We provide infrastructure that helps.

Your responsibility

Your event payloads, your template content, your provider contracts and your DPA agreements with recipients remain your responsibility.

Frequently asked questions

Is else.events GDPR compliant?
else.events provides EU-hosted infrastructure, configurable log retention and provider choice — all of which help you manage GDPR considerations. Whether your overall setup is compliant depends on your stack, your privacy policy and your legal context. We do not make blanket compliance guarantees.
Where is else.events hosted?
else.events infrastructure runs in the EU. Events you send, templates you store and delivery logs are processed and stored in EU data centres.
Can I get a Data Processing Agreement (DPA)?
Yes. Contact us to request a DPA for your organisation.
How long are email logs kept?
Log retention is configurable per plan. You can set shorter retention periods for logs that contain personal data in line with your privacy policy.
Does else.events process the content of emails?
else.events renders templates with the data from your event payload. The rendered content is passed to your chosen provider for delivery. else.events logs delivery metadata — not full email body content by default.

Email infrastructure that fits your EU compliance posture

EU hosting, configurable retention, your choice of provider. A foundation you can build on.

  • EU-hosted infrastructure
  • Configurable log retention per plan
  • Works with EU-contracted providers like Postmark or SMTP