Email Compliance

CronDB takes email compliance seriously. Every sequence includes built-in safeguards to help you stay compliant with CAN-SPAM, GDPR, and other email regulations.

CAN-SPAM Requirements

The CAN-SPAM Act requires all commercial emails to include:

1. Accurate header information — Your "From" name and email must be truthful
2. Non-deceptive subject lines — Subject must reflect the email content
3. Identification as an ad — If applicable, disclose that the message is an advertisement
4. Physical postal address — Your business address must be included
5. Opt-out mechanism — A clear way for recipients to unsubscribe
6. Honor opt-outs promptly — Within 10 business days

CronDB handles items 5 and 6 automatically. You are responsible for items 1-4.

Automatic Unsubscribe Footer

Every email sent through CronDB sequences includes an unsubscribe footer:

If you'd prefer not to receive these emails, unsubscribe here.

This footer is:

• Always present — Cannot be removed from sequence emails
• Customizable — You can edit the text (but not remove the link)
• Tracked — Clicks are logged and the contact is immediately suppressed

Customizing the Footer

1. Go to Sequences → Settings → Compliance
2. Edit the unsubscribe footer text
3. Include the {{unsubscribe_link}} variable (required)
4. Optionally add your physical address

Example custom footer:

You're receiving this because your domain was recently registered.
Not interested? {{unsubscribe_link}} | {{company_address}}

List-Unsubscribe Header

CronDB automatically includes the List-Unsubscribe and List-Unsubscribe-Post email headers in every outgoing message. These headers allow email clients (Gmail, Outlook, Apple Mail) to display a native "Unsubscribe" button at the top of the email.

This is an industry best practice that:

• Reduces spam complaints (recipients use the button instead of reporting spam)
• Improves deliverability (email providers trust senders who include this header)
• Satisfies Google and Yahoo's 2024 sender requirements

Preference Center

When a recipient clicks unsubscribe, they land on a preference center where they can:

1. Unsubscribe from this sequence — Stop this specific campaign
2. Unsubscribe from all — Block all future emails from your account
3. Adjust frequency — Receive less frequent emails (if you offer this option)

The preference center is hosted by CronDB and requires no setup. It automatically uses your branding (logo, colors) from your account settings.

Suppression List

The suppression list contains all email addresses and domains that should never receive emails:

Automatic Additions

CronDB automatically adds to the suppression list:

• Contacts who click unsubscribe
• Email addresses that hard bounce (invalid address)
• Domains that send abuse complaints

Manual Additions

1. Go to Sequences → Settings → Suppression List
2. Click + Add
3. Enter email addresses or domains (one per line)
4. Click Save

You can also upload a CSV file of addresses to suppress.

Suppression List via API

curl -X POST \
  -H "Authorization: Bearer cdb_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["user@example.com"], "domains": ["example.com"]}' \
  "https://api.crondb.com/v1/suppression/add"

Suppression Is Global

The suppression list applies to ALL sequences. Once an address is suppressed, it will not receive emails from any sequence in your account.

Email Validation

Before sending, CronDB validates each recipient email:

Check	Description	Action if Failed
Syntax	Valid email format	Skip and flag
MX Record	Domain has mail server	Skip and flag
Disposable	Known disposable email domain	Skip and flag
Role-based	Generic addresses (info@, admin@)	Warning (still sends)
Catch-all	Domain accepts all addresses	Warning (still sends)

Disposable Domain Detection

CronDB maintains a database of known disposable email providers (Guerrilla Mail, Temp Mail, etc.). Emails to these domains are automatically skipped to protect your sender reputation.

GDPR Compliance

For prospects in the EU:

• Lawful basis — You must have a legitimate interest or consent to email
• Data access — Prospects can request their data via the preference center
• Right to erasure — Unsubscribing triggers data removal from active sequences
• Data processing — CronDB processes data as a processor under your direction

GDPR Responsibility

CronDB provides the tools for compliance, but you are responsible for ensuring your outreach has a lawful basis under GDPR. Cold outreach to EU prospects should be based on legitimate interest with a clear business context.

Bounce Handling

Bounce Type	Description	Action
Hard bounce	Invalid address (user unknown)	Remove from sequence, add to suppression
Soft bounce	Temporary issue (mailbox full)	Retry up to 3 times over 48 hours
Block bounce	Sender blocked by recipient	Pause and alert

Next Steps

• Warmup — Protect your sender reputation
• Email Notifications — Get alerted on compliance issues
• Creating Sequences — Build compliant sequences from the start

---

Try it now →