Compliance

Pipelime is designed to help you send compliant outreach emails.

CAN-SPAM Requirements

The CAN-SPAM Act requires:

Physical Address

A valid physical mailing address may be required in every email. Configure it in Settings → Organization → Physical Address. Pipelime verifies that an address is configured before allowing campaign activation, but does not insert it into email templates automatically. Include it in the template when your outreach policy requires it.

Unsubscribe Mechanism

If your outreach policy requires an opt-out mechanism, add {{unsubscribe_link}} to the template. Pipelime does not append an unsubscribe link automatically.

Honest Headers

Email headers (From, To, Reply-To) must accurately identify the sender. Pipelime uses the authenticated Gmail account's actual email address.

No Deceptive Subject Lines

Subject lines must relate to the email content. Pipelime provides this as a best practice recommendation.

GDPR Requirements

Data Export

Contacts can request an export of all data stored about them:

Pipelime contact export --contact-id cont_123 --format json

Hard Delete

Contacts can request permanent deletion of all their data:

Pipelime contact delete --contact-id cont_123 --hard

This removes:

• Contact record and all fields
• Campaign assignment history
• Activity and engagement data
• Any associated company data references

Consent

Pipelime does not manage consent collection. You are responsible for ensuring you have appropriate consent or legitimate interest before adding contacts to campaigns.

Unsubscribe Handling

When a contact clicks the unsubscribe link:

1. The contact is immediately removed from all active campaigns
2. The email address is added to the blocklist
3. A email.unsubscribed webhook event is fired
4. Future sends to this address are blocked

Unsubscribe is processed within seconds of the click.

Blocklist Enforcement

The blocklist is checked before every email send. See the Blocklist Guide for details.