Glossary · Email & infrastructure
Transactional email
Transactional email is a message triggered by a specific user action or system event — password resets, receipts, verification codes, shipping notices — as opposed to marketing email sent to a list on a schedule.
The distinction matters legally and technically. Marketing email requires opt-in consent, unsubscribe mechanisms, and list-hygiene discipline under laws like CAN-SPAM and GDPR’s ePrivacy rules; transactional email, sent as the direct result of an action the recipient just took, generally does not — a password-reset email does not need an unsubscribe link, because opting out of it means the account stops functioning.
Deliverability infrastructure for transactional email is typically judged on speed and reliability rather than open rates: a verification code that arrives two minutes late is a support ticket, not a missed marketing metric. That shifts the engineering priorities toward low-latency sending, strict authentication (DKIM, SPF, DMARC) to avoid spam-folder placement, and minimal data retention, since transactional messages carry no analytics purpose once delivered.
Ciphera Relay is built for transactional email specifically — password resets, verification codes, receipts — with no marketing-sending capability, no tracking pixels, and delivery metadata retained for 30 days before deletion.