Stage 2 of 12
Legal and Policies for an Email Service Provider
The documents an ESP needs before its first signup: a legal entity, terms of service, an acceptable use and anti-spam policy, a DPA with a sub-processor list, a privacy policy and a working abuse@ mailbox. This guide covers what each must say when many customers send from your platform. It is not legal advice.
By Cem Hurturk, founder of Octeth Updated 12 min read
- Drafting terms
- AUP
- Privacy policy
- DPA
On this page
This guide is not legal advice. It explains which documents an ESP needs and the decisions inside them, based on the ESPs we run and build. Laws differ by country and change. Have a lawyer review your documents for the countries you sell into before you rely on them.
Finish this stage before the first signup. Your signup form asks customers to accept the terms, your review process enforces the acceptable use policy, and EU customers will ask for your DPA before they upload a list.
The documents and what each must cover
| Document | Who it binds | What it must cover for an ESP |
|---|---|---|
| Terms of service | You and each customer | Account review, shared IPs, plan limits, suspension, data ownership, no delivery guarantee, liability |
| Acceptable use and anti-spam policy | Each customer’s sending | Consent, refused senders, sender identity, unsubscribe, authentication, complaint and bounce limits, enforcement |
| Data processing agreement (DPA) | You as processor, the customer as controller | The Art. 28(3) GDPR terms, sub-processors, transfers, breach notice, deletion |
| Sub-processor list | Companies that reach subscriber data | Company, what it does, country |
| Privacy policy | Your own customers and visitors, and subscribers who look you up | Both roles, legal bases, retention, rights, contacts |
| abuse@ and role mailboxes | Anyone reporting your customers’ mail | A working address and a person who reads it |
All of them name one legal entity, so start there.
Set up the legal entity
A brand is not a legal person. The terms, privacy policy, DPA and invoices must name the company that operates the brand. The GDPR requires the controller’s identity and contact details in the privacy notice (Art. 13(1)). CAN-SPAM requires a valid physical postal address in every marketing email you send (FTC compliance guide). A registered PO box or private mailbox counts.
Decide three things with the entity:
- Which company contracts. Use the brand name everywhere except where the law needs the company: legal documents, invoices and the footer of your own marketing email.
- Governing law and courts. Pick the law in the terms and where disputes go. This is a lawyer question, because it decides which consumer and data protection rules apply in practice.
- How much you publish. Publish what the law asks for. One build we did names the company and a mailing address only, with no company number or owner names.
Write the terms of service
Generic SaaS terms miss what makes an ESP different: one customer’s sending affects every other customer. Cover these points.
- Business use only. State who may sign up and the minimum age.
- Account review. Say that you review new accounts, may start them at low limits and may decline them without giving a reason. Creating an account is not acceptance.
- Shared IPs. Explain that customers share sending IPs, and that this is why the acceptable use policy is enforced.
- Dedicated IPs. If you offer them, state that they stay yours, cannot move to another provider, and that you may move a customer back to shared IPs to protect delivery.
- No delivery guarantee. Mailbox providers decide inbox placement. Say that you do not guarantee inbox placement, open rates or any sending result.
- Uptime. Decide whether you publish an SLA with service credits or promise no uptime level. An SLA helps you sell to larger customers. No SLA keeps your exposure small while you are new.
- Plan limits. Match the overage rule you chose in stage 1: hard stop or billed overage.
- Suspension and termination. List when you may limit, pause or close an account: policy breaches, risk to shared IPs, overdue payment, a request from a mailbox provider or blocklist operator, and suspected fraud. Reserve the right to act first and explain later for serious cases.
- Reselling. Agencies will want to send for their clients. Allow it only with your written approval, so you can review each client.
- Customer data. The customer owns its lists. State the export window after an account closes, and that you keep suppression records of unsubscribed, bounced and complained addresses even after the customer deletes them.
- Liability and indemnity. Set a liability cap and require the customer to cover claims and fines that come from its own sending. Your lawyer sets the cap.
- Changes. State how much notice you give before price changes and material changes to the terms.
Write the acceptable use and anti-spam policy
The acceptable use policy (AUP) is the rulebook your account review enforces. You can put the anti-spam rules in the AUP or in a separate anti-spam policy. Two documents with overlapping rules drift apart, so we recommend one document that serves as both, linked from your terms.
Why the policy is stricter than the law
Your customers send to recipients in many countries, so one rule has to work under all of them.
| Law | What it requires | Source |
|---|---|---|
| CAN-SPAM (US) | Honest headers and subject lines, the message identified as an ad, a postal address, a clear opt-out honoured within 10 business days and working for at least 30 days after sending. It applies to business-to-business email too. Prior consent is not among its requirements. | FTC |
| UK PECR | Marketing email to individuals needs their consent, or the soft opt-in for existing customers who bought, or negotiated to buy, something similar and could opt out at collection and in every message. Corporate subscribers can be emailed. The sender must not hide its identity and must give a valid contact address. | ICO |
| CASL (Canada) | Consent (express or implied), sender identification and an unsubscribe mechanism. Unsubscribes take effect within 10 business days, and the mechanism must work for at least 60 days after sending. | CRTC |
| GDPR (EU) | Processing needs a legal basis (Art. 6). Consent must be freely given, specific, informed and unambiguous (Art. 4(11)). Pre-ticked boxes and silence are not consent (Recital 32). The controller must be able to show consent, and withdrawing it must be as easy as giving it (Art. 7). | gdpr-info.eu |
The ICO says its PECR guidance is under review after the Data (Use and Access) Act 2025. Check it again before you publish.
CAN-SPAM alone would let a customer email people who never opted in. On shared IPs that mail hurts everyone, so the AUP sets one rule for all customers: opt-in only, with records that prove it. Set the complaint and bounce limits to match the mailbox provider rules in stage 6 and the thresholds you enforce in stage 8. Under CAN-SPAM, both the company whose product is promoted and the company that sends can be held liable. Your terms should make the customer carry that risk for its own mail.
If you offer SMS, add SMS rules to the same policy. Require prior express consent, honouring STOP and HELP, quiet hours and sender registration where carriers require it, and make the customer responsible for telecom law compliance.
AUP template
A skeleton to adapt. Replace the bracketed parts, and have your lawyer review the result.
Show the AUP template
ACCEPTABLE USE POLICY
Effective date: [DATE]. Part of the Terms of Service at [TERMS URL].
1. Why this policy exists
Customers share sending IPs. One sender's bad list hurts everyone's delivery.
The same rules apply on dedicated IPs.
2. Account review
We review every account before full-volume sending.
We may ask about your business, your list source and your opt-in method.
We may start you at low limits, review again later, or decline the account.
3. Consent
Send marketing only to people who opted in to your mail with a clear action.
A box ticked in advance, or a line buried in your terms, is not opt-in.
Each list is yours alone: no addresses that opted in to someone else.
Keep proof of consent: date, source, wording and IP address. Show it on request.
Re-confirm addresses you have not mailed for [PERIOD].
4. Refused senders and content
Purchased, rented, scraped or appended lists.
Unsolicited mail, including cold outreach.
[CATEGORIES YOU REFUSE].
Phishing, malware and anything illegal where you, we or the recipient are.
5. Senders that need extra review
[CATEGORIES YOU ACCEPT WITH CLOSER MONITORING].
We may ask for licences, sample emails and landing pages.
6. Sender identity
From, Reply-To and subject lines must be accurate.
Every marketing message carries your physical postal address.
Send only for your own organisation unless we approve otherwise in writing.
7. Unsubscribe
Every marketing message has a working unsubscribe link and one-click unsubscribe.
Honour unsubscribes within [PERIOD]. Never re-add suppressed addresses.
8. Authentication
Every sending domain has SPF, DKIM and DMARC aligned with the From domain.
9. Complaint and bounce limits
Spam complaints below [RATE]. Hard bounces below [RATE] per campaign.
No spam trap hits. We suppress bounced, complained and unsubscribed addresses.
10. Enforcement
We may contact you, hold campaigns, lower limits, pause sending,
suspend or close the account. Serious breaches end the account at once.
11. Reporting abuse
Report mail that breaks this policy to [ABUSE ADDRESS], with full headers.
12. Changes
We email account holders before material changes take effect.
Write the DPA and the sub-processor list
For subscriber data your customer is the controller, because it decides why and how the data is used. You are its processor (Art. 4(7) and 4(8)). Art. 28 requires a contract between you that sets out the processing and binds you to:
- process only on the customer’s documented instructions
- bind your staff to confidentiality
- take the security measures of Art. 32
- follow the rules for sub-processors
- help with data subject requests
- help with security, breach notice and impact assessments
- delete or return the data when the service ends
- give the information needed to show compliance, and allow audits
You can make the DPA part of the terms, so customers accept it at signup, and send a signed copy to customers who ask. One build we did works this way.
Decisions inside the DPA
- Abuse prevention as an instruction. A processor acts only on documented instructions. A multi-tenant ESP uses sending data from all accounts to suppress complained addresses, spot spam traps and enforce the AUP. One model writes that use into the DPA as part of the customer’s instructions. Some ESPs instead act as an independent controller for abuse prevention and suppression data and say so in the privacy policy. Ask your lawyer which model fits.
- Breach notice. The processor tells the controller without undue delay, and the controller tells the authority within 72 hours where feasible (Art. 33). Put a fixed period in the DPA that leaves your customer time to meet its own 72 hours.
- Sub-processor changes. Under a general authorisation you must tell customers about added or replaced sub-processors and give them a chance to object (Art. 28(2)). Give notice before the change takes effect and state the objection period. Keep an emergency clause for replacing a failed provider at short notice, and have your lawyer word it. Your sub-processors must sign the same data protection terms, and you stay liable for them (Art. 28(4)).
- Transfers outside the EU. The EU-US Privacy Shield is invalid since the Court of Justice ruling of 16 July 2020 (C-311/18 press release). Use the standard contractual clauses of Decision (EU) 2021/914: module two from your customer to you, module three from you to your sub-processors, where the data leaves the EEA. The EU-US Data Privacy Framework (Decision (EU) 2023/1795) covers only US organisations that have certified. Do not claim it unless you are on the list.
- Security annex. List the measures you have in place today, not the ones you plan.
Who belongs on the sub-processor list
A sub-processor is any company that can reach your customers’ personal data. For an ESP that usually means the app and database host, the MTA host, DNS and network security in front of the app, the payment processor, and the mail service that stores support and privacy requests. Split the list into subscriber data and account, billing and website data, so customers see quickly who touches their lists.
Self-hosted software whose vendor has no access to the data is not a sub-processor. That changes the moment vendor staff get server, database or support access, for example for installs, upgrades or debugging. If Octeth maintains your Octeth server under Octeth Care, Octeth has that access, and the Octeth Care DPA covers it.
Publish the company name, what it does for you and the country. Leave out IP ranges, AS numbers and hostnames.
Write the privacy policy
An ESP holds personal data in two roles, and the privacy policy has to explain both.
- As controller, for data about your own customers and visitors: account and contact details, account review answers, login and security logs, billing, support messages and website analytics.
- As processor, for subscriber lists. Tell subscribers that requests about their data go to the sender, and that you pass them on if the sender cannot be reached.
Art. 13 lists what the policy must state: who you are and how to contact you, purposes and legal bases, legitimate interests where you rely on them, recipients, transfers and their safeguards, retention, the data subject’s rights, how to withdraw consent and how to complain to a supervisory authority.
Give each purpose its legal basis. Running the account is contract. Account review and abuse monitoring are legitimate interests, because they keep shared IPs usable for every customer. Billing records are a legal obligation. Your own marketing email and non-essential cookies need consent where the law asks for it.
Write retention as a table and use the same periods in the DPA and the terms: deletion after an account closes, backups, security logs, billing records and abuse records. Change all three documents together.
Two more decisions:
- Data protection officer. A DPO is required when core activities include regular and systematic monitoring of people on a large scale (Art. 37). Ask your lawyer whether open and click tracking across your customers’ lists counts. If you appoint one, publish the contact details. A DPO mailbox without a name is enough.
- EU representative. A company with no establishment in the EU that offers services to people there must appoint a representative in writing, unless its processing is occasional and low risk (Art. 27). An ESP processes subscriber data every day. Decide this before you market to EU customers.
Set up abuse@ and the role mailboxes
RFC 2142 says abuse@ at your domain must be valid and supported, and that every host running an SMTP server needs a postmaster@ mailbox. Mailbox providers, blocklist operators and recipients use abuse@ to report your customers’ mail.
Create these before launch: abuse@, postmaster@, support@, privacy@, security@ and legal@. At launch one person can read all of them. One build we did forwards every address on its domain to the owner’s inbox through a catch-all. When the team grows, route each role to the person who handles it. The mail service that stores these messages goes on your sub-processor list.
Publish a report-abuse page that asks for the full message headers, because the headers tell you which account sent the mail. Say when you reply, and count the time in work days so the promise has a fixed meaning.
Connect the documents to the app
The documents protect you only if customers see them and the platform follows them.
- Signup pages. Link the terms, the privacy policy and the AUP from signup, login and password reset. In Octeth these links come from the brand settings. Set them before you open signups.
- Footers. Each plan’s footer adds the unsubscribe link your AUP promises to campaigns, journeys and list transactional mail. API and SMTP relay sends do not get it from the footer: there the opt-out link comes from the sender domain’s unsubscribe link setting, which is off by default. Test each send path and check what it carries.
- Postal address. Your AUP makes each customer put its own postal address in its mail. Your own newsletters and system marketing carry your company’s address.
- One effective date. Use one effective date across all your policies, set on the day a revision goes live. Customers then see one version of the rules.
- No placeholders. Keep drafts behind a draft banner and noindex until no placeholder is left.
Decide on legal review
Templates and AI drafts get you a structure. They do not tell you whether a clause holds up in your jurisdiction. One build we did launched its documents without a lawyer review, by the owner’s decision, and turned each open drafting question into a recorded decision. It marked two triggers for a review: the first customer who asks to negotiate the DPA, and the first larger customer. If you skip a review at launch, write down when you will get one.
Before you move on
- You know this guide is not legal advice, and you have decided who reviews your documents and when.
- The terms, privacy policy, DPA and invoices name the company that operates the brand, with its postal address.
- Your terms state account review, shared IP rules, suspension rights and that inbox placement is not guaranteed.
- Your acceptable use policy requires opt-in consent and proof of it, lists refused senders and states complaint and bounce limits.
- Your DPA covers every Art. 28(3) GDPR term and says how cross-account abuse prevention is covered.
- Your sub-processor list names every company that can reach subscriber data, with the country, and nothing about your network.
- Your privacy policy covers both roles: controller for account data, processor for subscriber data.
- Retention periods match across the privacy policy, the DPA and the terms.
- abuse@, postmaster@, privacy@ and support@ receive mail, and someone reads them.
- Signup pages link the terms, privacy policy and acceptable use policy. Campaigns and journeys carry an unsubscribe footer, and you have decided how API and SMTP relay mail carries an opt-out link.
- No placeholder is left in any published document.
What we've seen go wrong
A transfer clause that no longer worked
Legal pages carried over from an older website can still hold a clause that relies on the EU-US Privacy Shield. The EU Court of Justice invalidated the Privacy Shield in July 2020. Replace such a clause with the 2021 standard contractual clauses. Old policy text ages with the law, so date every document and review it.
The software vendor listed as a sub-processor
In one build, the first sub-processor list named the software vendor as an operations provider, based on an internal note that the vendor ran the app. A check showed the operator installs each release from a package the vendor publishes, the license is verified on the server, and vendor staff have no login, so the row was removed. Decide sub-processor status by who can reach the data, and check it again when access changes.
Network details in a public document
In one build, the sub-processor work recorded the sending network's AS number and address ranges. The owner decided that public documents name only the hosting company and the country, which is what the sub-processor list needs. IP ranges, AS numbers and hostnames stay private.
Security measures nobody had confirmed
When we drafted a DPA for one build, the security facts for the annex were not confirmed, so the annex listed only the measures in place instead of promising more.
Related glossary terms
We build ESPs
Rather have us build this?
Your legal documents stay with you and your lawyer. We build and run the platform they govern: servers, sending and the Octeth setup.