SaaS email template

Account deletion email — clear confirmation, no data surprises

Fire user.account_deleted with the deletion date and data retention information. else.events sends a clear, trustworthy confirmation that reduces support questions.

Why account deletion emails matter

Users do not know what happens to their data

"Account deleted" with no mention of data retention leaves users wondering whether their personal data was actually removed.

No export confirmation if data was exported

If the user requested a data export before deletion, the confirmation email should acknowledge that the export was sent.

No timeline for complete data removal

If backups retain data for 30 days after deletion, say so. Users and privacy-aware teams need this information.

Hardcoded in the account deletion flow

Account deletion email logic in the deletion handler makes it hard to update copy or add GDPR-required information.

Deletion confirmation, data timeline and export link — from the payload

deletion_at and data_purge_at from the payload

Include the deletion date and the date when data is fully purged from backups. The template renders both clearly.

Data export link from the payload if applicable

If the user requested a data export, include the export_url in the payload. The template renders a "Download your data" link.

Support contact for questions

Include a contact or support URL. Users with questions about their data have a clear path to ask.

Managed outside your account service

Update deletion email copy, add GDPR information or change the support link without touching the deletion flow.

Template variables for the account deleted email

  • {{ user.name }}Recipient name (last communication — account is deleted)
  • {{ user.email }}Account email address being deleted
  • {{ data.deleted_at }}Date the account was deleted
  • {{ data.data_purge_at }}Date when data is fully removed from backups
  • {{ data.export_url }}Data export download link (if applicable)
  • {{ data.support_url }}Contact link for data or deletion questions

Frequently asked questions

What subject lines work for account deletion emails?
"Your [App] account has been deleted", "Account deletion confirmed — [date]", "We have deleted your [App] account". Factual, no emotional tone.
What data retention information should I include?
At minimum: when the account was deleted, when data is purged from backups (if applicable) and a contact for data questions. Consult your privacy policy for what must be disclosed.
Should the deletion email include a reactivation option?
Only if your product supports account reactivation within a window. If accounts are permanently deleted, do not include a reactivation link — it is misleading and potentially a GDPR issue.
What if the user asks us to delete their data after receiving this email?
Include a support contact link in the email. If data_purge_at is included, the email itself informs the user when full deletion occurs. For DSARs, direct the user to your data protection contact.

Account deletion emails that answer the questions users have

Deletion date, data purge timeline and support contact — all from the event payload.

  • Data purge date shown clearly
  • Export link from payload if applicable
  • Support contact for data questions