Skip to content
Rainmaker
Log inTry it free
Try it free · 14 daysPricing
Trust center

Outbound that can be audited.

Most tools hide how they pick people and what they actually send. We surface every decision, every source, and every guardrail. That is what accountable AI outbound means.

Articles of record

Rules the system enforces before any human sees a draft.

These are not aspirations.

01

No source, no send

The source guardrail requires every factual sentence to cite at least one existing SourcedClaim. Dangling citations or unsourced factual content mark the touch blocked - it cannot send, in any mode.

02

Buyer Persona, not lookalikes

The Reader builds segments from your actual buyers - titles, pains, triggers, disqualifiers, language patterns - rather than companies that resemble you. Campaigns are created per approved segment.

03

Copilot by default, with a hard stop

By default you approve each batch; with Autopilot on, the agent sends on its own inside daily budget caps. Every send gets a dispatch-time suppression re-check. A draft with an unsourced claim stops and never sends until a person fixes it.

04

Deliverability guardrails

Every address is verified before it is emailed, and each mailbox has a daily sending cap. For mail sent through Rainmaker's own sending service, the campaign pauses automatically when bounces pass 3% or complaints pass 0.1% after a minimum sample. Mail sent from your own connected mailbox reports bounces to that mailbox.

05

Global, permanent opt-out

Confirmed unsubscribes write to a global opt-out registry across all workspaces. Consumer rights - delete, know, opt out - use double opt-in and a logged, privileged scrub routine.

06

Verifiable outcome billing

The $25 fee triggers only on a qualified meeting: accepted RSVP, scheduled start passed, not cancelled or disputed. Append-only ledger rows with idempotency keys, capped at 20% of subscription.

Compliance, written into the machine

The Gatekeeper always adds

✓Clear sender identification: every message goes out under a real sender name
✓RFC 8058 List-Unsubscribe with one-click support
✓A truthful subject line and a working unsubscribe link

Additional enforced controls

✓Workspace-approved US and European market policies
✓Privacy, source-notice and retention gates for Europe
✓Global opt-out registry plus double opt-in rights
✓Automatic pause on high bounce or complaint rates for mail sent through Rainmaker's own sending service
✓Append-only ledgers for all usage and reversals

Full operational detail - tenancy isolation, seams, scrub routines - and the DPA live inside the product. The commitments here are intentionally high-level.

Where your data sits

HostingEU/EEA/UK/CH residents filtered before any paid enrichment; unknown geography quarantined.EU only
Lead dataCaches scoped per workspace at the database level. No cross-customer pooling.Isolated
Opt-outsA confirmed unsubscribe suppresses that address across every workspace.Permanent
PaperworkDPA available today, signed the same week. SOC 2 audit is on the roadmap.DPA today
Sub-processorsListed by name with what each one receives. Ask and we'll send the current list.On request

Recipient rights

Any recipient can exercise their rights at any time. Full privacy and opt-out tools are available without signing in.

Read the privacy notice →

Opt-out confirmations and data requests use double opt-in, so nobody can suppress or delete someone else's address.

Compliance questions

Is cold email legal, and what do we enforce?

The questions buyers and their lawyers ask, answered with the mechanisms that run in the product.

What is the no-source-no-send rule?+
Rainmaker will not include a factual claim in an outreach email unless it can be traced to a verifiable source. If no source is found, the draft is blocked rather than sent unverified: it shows in your approval queue marked as blocked, and it cannot be approved or sent. This runs on every draft, again at approval and again before dispatch.
How does the hard stop work?+
By default you approve each batch before it sends; with Autopilot on, sourced drafts send on their own inside your rules. Any draft with a claim the agent cannot source stops in your approval queue, marked as blocked: you edit it (the edit is checked again), request a redraft or reject it. Nobody can approve it as it stands, and Autopilot never does.
Does Rainmaker comply with GDPR for cold B2B email?+
Cold B2B email is legal under GDPR on a legitimate-interest basis when it is relevant to the recipient's professional role and includes a clear opt-out. Rainmaker includes an opt-out link in every email and suppresses opted-out addresses permanently across all accounts.
What happens when someone opts out?+
The address is added to a permanent suppression list shared across every Rainmaker account. No account on the platform will contact it again.
How does Rainmaker handle bounces and spam complaints?+
Every address is verified before it is emailed, and each mailbox has a daily sending cap. For mail sent through Rainmaker's own sending service, high bounce or spam-complaint rates pause the campaign automatically until someone reviews it. Mail sent from your own connected mailbox reports bounces and complaints to that mailbox, so watch it there.
What happens if the AI writes something factually wrong?+
It cannot send. Every factual claim must link to a verifiable source before dispatch. If none is found, the sentence is blocked - not flagged for review.

From the blog

All posts →

“If a sentence cannot be sourced, it does not leave the system.”

Paste your domain and read what it lets through - and what it blocks - on your own market.

- RainmakerThis is the marketing view of our commitments. The full operational and technical detail lives in the product docs for customers. Every commitment above is enforced before any message is shown to a human.