Security
You own everything
Pulse touches.
Pulse runs on a machine your IT manages, under your own AI platform organization, with a CRM user you create and can switch off. We configure it and hand it over. Your customer data never lands on our devices or in our accounts.
| Part | Owner | Notes |
|---|---|---|
| Host machineA managed, encrypted machine with a dedicated local user for Pulse | Your IT | A managed, encrypted machine with a dedicated local user for Pulse |
| AI platform organizationYour team or enterprise plan. Pages and scheduled runs live here | You | Your team or enterprise plan. Pages and scheduled runs live here |
| CRM integration userA read-only role. You hold the credentials | Your CRM admin | A read-only role. You hold the credentials |
| Marketing tool connection (optional)Narrow scopes; the token sits in the host machine's keychain | Your CRM admin | Narrow scopes; the token sits in the host machine's keychain |
| Pulse codeA pinned, reviewed release, installed by you after reading its notes | Us | A pinned, reviewed release, installed by you after reading its notes |
| Company configurationStages, fields, quotas and people rules | Us, with your sales ops | Stages, fields, quotas and people rules |
| Page sharingNamed people only | Your sales leader | Named people only |
Offboarding us needs no cleanup on our side, because nothing of yours was ever on it.
Pulse security
On a machine your IT manages (encrypted disk, automatic updates, screen lock), under a dedicated local user, inside your own AI platform organization. The workspace stays on that machine's local disk. Your customer data never lands on our devices or in our accounts.
Daybook security
No. It reads only. It can't send, reply, forward, move or delete mail or chats, and it never accepts or changes calendar invites.
Your security team gets the details in writing.
The install guide, the data the integration user reads, and every release's notes, before anything is connected.