Security & data
The first procurement question, answered plainly.
Outbound tools touch your prospect data and your sending accounts. Before anything else, your security team wants to know where the data sits and who can reach it. Here are the answers.
What we do today
What we do today.
EU data residency
Customer data is stored in an EU region. It's a decision in the data layer, not a toggle in the footer.
Tenant isolation by design
Every workspace is separated by row-level security. One customer cannot see another's contacts, signals, or messages.
Residency in your DPA
We disclose the region and give you residency terms you can sign — built to survive a procurement review.
Warmup-first, paced sending
Sends ramp from a low daily cap with jittered spacing inside working hours, so your domain and LinkedIn account stay healthy.
You hold the kill switch
Turn a campaign off and in-flight sending stops. Approvals, edits, and skips are yours.
What we don't claim (yet)
What we don't claim (yet).
We don't list SOC 2 or ISO 27001, because we don't hold them yet. When they're real, you'll see the certificate. Until then we describe the architecture you can verify, not a badge you can't.
Pre-launch · early access
EU you can prove. Not EU vibes.
Where your data lives, who can see it, and what you can sign — answered plainly.