A password reset and a product announcement can go to the same address in the same week, but they do not have the same purpose or necessarily the same legal basis. This GDPR email compliance guide shows SaaS teams which messages need permission, what evidence to keep, and how to build the controls into campaigns, workflows, and transactional systems.

GDPR email compliance means processing personal data lawfully and transparently, using each address for a defined purpose, and respecting people’s rights. Marketing messages must also meet applicable direct-marketing and e-privacy rules. Service messages still involve personal data, but their purpose and basis may differ. Your email provider can support these controls; it cannot make your organization compliant by itself.

What GDPR email compliance means

The General Data Protection Regulation (GDPR) governs the processing of personal data. It applies to organizations established in the European Union (EU) and can apply to organizations elsewhere that offer goods or services to people in the EU or monitor their behavior. The relevant question is whether personal data is processed in a covered context—not whether a business sends email.

An address that identifies a person, an account ID linked to that address, or an event log tied to an account can be personal data. A contact record combined with campaign opens or clicks may reveal how someone interacts with a service. Treat recipient data and activity data as potentially identifying unless you have established otherwise.

The organization deciding why and how to use the data is generally the controller. An email service provider (ESP) processing data on the organization’s instructions may act as a processor. The European Commission describes these roles and the GDPR’s application in its GDPR guidance. Actual roles follow the processing and contractual arrangement, not just the label a vendor uses.

Marketing emails vs. transactional emails

Classify each template by purpose before deciding how to send it. A receipt, password-reset link, security alert, or confirmation of a user-requested account change supports a specific service interaction. A newsletter, discount, product announcement, or invitation intended to encourage a purchase is marketing.

MessageTypical purposeExample control
Password resetRestore access requested by the userSend the reset instructions; do not add an unrelated offer
Payment receiptDocument a completed transactionInclude transaction details needed by the recipient
Product newsletterPromote updates or encourage engagementUse the appropriate permission or other lawful route and provide an unsubscribe path
Renewal offerEncourage a purchase or upgradeTreat as promotional even if sent near a billing event

The label “transactional” does not settle the question if a message contains promotional content. For example, adding a paid-plan placement to a password-reset email can affect how the message is treated under applicable direct-marketing and national e-privacy rules. Keep service information and promotion distinct instead of relying on a template name to establish its purpose.

GDPR also applies when processing addresses for transactional messages. A company may need an address to provide a requested service, but that does not automatically justify reusing it for unrelated campaigns. For teams using one sending API, keep message types, audiences, and suppression rules separate even when the infrastructure is shared.

When you need consent—and what valid consent looks like

Consent is one GDPR legal basis, not the only one. Depending on the processing, contract necessity, legal obligation, or legitimate interests may be relevant. But a GDPR legal basis does not by itself answer whether a particular marketing email is permitted: direct-marketing rules and national e-privacy requirements also matter.

Where consent is required, it should be freely given, informed, specific, and shown through a clear affirmative act. The person should know which organization is asking, what kind of messages they will receive, and how to withdraw. A pre-checked box, silence, or marketing permission bundled into unrelated service terms makes it difficult to show a clear choice.

Use a distinct, unchecked control for optional marketing, such as: “Email me product updates and occasional offers from Acme. I can unsubscribe at any time.” Put the relevant notice beside the control, identify the organization, and do not make marketing permission a condition of an unrelated service. If a third party supplied the address, do not assume public availability or possession of a list is permission to email it. The European Commission’s guidance on third-party data for marketing says organizations should establish that the data was collected lawfully and can be used for advertising.

Cold email has no single blanket answer. The recipient, country, purpose, data source, GDPR basis, and national e-privacy rules all matter. A legitimate-interest assessment alone does not automatically permit unsolicited marketing. Decide the permissible route before sending, rather than treating a publicly visible address as consent.

What to include in a compliant email

A recipient should be able to identify the sender, understand why the message arrived, and act on it. For marketing, use a recognizable sender identity, an honest subject and purpose, relevant content, and an obvious unsubscribe or objection route. Do not make someone log in or explain their decision to stop promotional email.

Use this pre-send checklist:

  • Does the sender name and address identify the organization?
  • Does the message match the purpose described when the person signed up?
  • Is the content relevant to the audience and clear about why it was sent?
  • Is the unsubscribe or objection path easy to find and use?
  • Will the request stop other campaigns and automated workflows that could email this person?

An unsubscribe link that suppresses only one newsletter but leaves a promotional onboarding sequence active is not an effective control. Propagate the request to every system that can send marketing, and promptly stop processing the person’s data for direct marketing when they object. Keep a minimal suppression record so a future import does not reactivate the address accidentally.

How to collect and prove permission

A checkbox is useful only if your team can later show what the person agreed to. Store who consented, when and how they did so, the purpose and wording displayed, and subsequent changes or withdrawal. Keep evidence connected to the contact without collecting unrelated form data indefinitely.

For example, an application might store this consent event:

{
  "contact_id": "ct_4821",
  "email": "alex@example.com",
  "purpose": "product_updates",
  "status": "granted",
  "consent_text_version": "signup-marketing-v3",
  "source": "pricing-page-signup",
  "recorded_at": "2026-10-14T09:42:00Z"
}

When the person unsubscribes, record the change rather than keeping only the latest yes/no value. For example, set status to withdrawn, record withdrawn_at and source such as campaign_unsubscribe, then publish the suppression event to campaign and automation systems. That audit trail helps answer which notice was shown and which message categories it covered.

Keep marketing consent separate from acceptance of terms. If the wording, audience, or purpose changes materially, assess whether the existing permission covers the new use instead of silently broadening it. The signup form and the stored event should describe the same choice.

Data rights, retention, and list hygiene

A rights request can involve more than the main contact table. A person may ask to access or correct information, request deletion, or object to marketing. Map where addresses, consent events, campaign activity, and support records live, then assign an owner to coordinate the response. The European Commission’s information for individuals explains rights that include access, rectification, erasure, and objection.

Set a retention purpose for each data category. A signup form may need an email address and consent state, but not a birth date or job title unless the product has a defined need for them. Review stale or invalid contacts and remove or anonymize records when there is no continuing purpose to retain them.

Unsubscribe records need a deliberate exception to ordinary list cleanup: deleting every trace of an address can let a later import add it back to marketing. Retain only the minimum suppression information needed to prevent future sends, restrict its use to that purpose, and include it in your deletion and retention procedures. That suppression entry is not permission for unrelated processing.

Security and choosing an email provider

Review an ESP as a processor handling personal data, not just as a delivery pipe. Examine its processing terms, security controls, access practices, subprocessors, data locations, transfer arrangements, and retention by data type. The European Commission identifies documented instructions, confidentiality, security measures, and assistance with GDPR obligations as relevant processor-contract topics.

Retention disclosures are concrete evidence to compare, not universal rules. Mailgun’s published GDPR overview says it stores message bodies for up to 7 days and message metadata for 30 days; it says suppressions remain until removed, with removed suppressions potentially held in backup for up to 30 days. Those are Mailgun disclosures, not Volanea’s retention schedule or a GDPR-mandated retention period.

For Volanea, every email is sent over Amazon SES, using shared Amazon SES infrastructure; we do not offer dedicated IPs. Volanea provides a contact graph with one-click unsubscribe, a reputation guard that slows sending when a list may harm the sender domain, and send records, delivery, open, click, bounce, and unsubscribe statistics alongside event logs. These are useful operational controls, but they do not replace your decision about purpose, collection, consent, or retention.

Volanea’s public product information does not specify where contact records, message bodies, or event logs are stored, or their retention periods. Ask us for the details relevant to your processing before putting EU personal data into the service. Volanea does not hold SOC 2 or ISO 27001 certification. A BAA is available on request at hello@volanea.com; that does not mean Volanea is HIPAA certified.

We also provide a concrete development safeguard: Volanea sk_test_ keys render and log messages but never deliver them. Use them to exercise template rendering and event-handling paths without accidentally sending to real recipients. Production keys and access should still be managed separately, and your team should test suppression propagation across each live campaign and workflow path.

A practical GDPR email compliance checklist for teams

For a SaaS product sending receipts, onboarding messages, and a monthly newsletter, build the controls into both product behavior and team operations:

  1. Classify every template. Record whether it is transactional, marketing, or mixed-purpose, and document what the content is meant to accomplish.
  2. Map purpose and basis. Tie each data field and send to its purpose, GDPR legal basis, and applicable e-privacy requirements.
  3. Capture permission where required. Use a separate affirmative choice, preserve the notice text version, and create a timestamped consent event.
  4. Preserve evidence. Store grants, changes, and withdrawals with their source; do not rely only on a current boolean field.
  5. Synchronize suppression. For example, map an unsubscribe event to contact_id, email, status, and source, then block campaigns, queued sends, imports, and automated workflows from reactivating it.
  6. Route rights requests. Name an owner who can locate data in your application, ESP, analytics tools, and support systems.
  7. Set retention and access rules. Define why each record is retained and limit access to contact data, credentials, and send logs.
  8. Review the provider relationship. Read processing terms and assess security, subprocessors, data locations, transfers, and retention before sending personal data.
  9. Test development paths. Use non-delivering sk_test_ keys for rendering and logging, and test that real unsubscribes reach every production sending path.

Volanea combines transactional email, campaigns, and automations on one API, so teams can coordinate those systems while preserving separate purposes and suppression behavior. Our contact graph’s one-click unsubscribe and event logs can support that implementation; the controller still owns the legal basis, notice, audience, and rights-request process. For campaign list acquisition, see our guide to automatic email opt-in and deliverability risks. For triggered sequences, our behavior-based welcome email guide covers workflow planning.

FAQ

What counts as personal data under GDPR when sending emails?

An email address is personal data when it identifies or can be linked to a person. Names, account IDs, IP addresses, message metadata, and campaign activity can also qualify when they relate to an identifiable individual. For example, an address paired with a click event and an account ID remains personal data even if the ESP does not store the person’s full name.

Is it illegal to send marketing emails without permission?

Not every situation follows the same rule: GDPR legal bases and national e-privacy rules both matter. However, an available address or a legitimate-interest assessment alone does not automatically authorize unsolicited promotional email. Before sending, identify the recipient category, country, message purpose, data source, and applicable direct-marketing rule.

Does Volanea provide a dedicated IP or a HIPAA certification?

No. Volanea sends through shared Amazon SES infrastructure and does not offer dedicated IPs. Volanea is not HIPAA certified; a BAA is available on request at hello@volanea.com. A BAA request and the email infrastructure are separate considerations from GDPR role, retention, and data-location review.

What happens when a Volanea test key sends an email?

A Volanea sk_test_ key renders and logs the message but does not deliver it. That makes it useful for checking a template or the application’s event handling without emailing a real recipient. Use production credentials only in the live sending path, and test that a real unsubscribe suppresses every campaign and workflow that can contact the address.

If you’re building email into a SaaS product, start with a sending setup that can support both operational messages and campaign controls while keeping your compliance decisions explicit. Start free with 1,000 emails a month.