Frequently asked questions

No. Every AI call goes through Pulse360's own server-side routes to the Claude API as a per-request call, not a training pipeline. Support tickets, CRM fields, and other connector data are explicitly marked as untrusted external data before they reach a prompt, so they can't be mistaken for instructions either.

In Supabase, on Postgres, with row-level security scoping every table to your workspace. No workspace can query another workspace's data. Connector credentials for your own workspace are encrypted at rest, not stored as plain environment variables. Only the public demo workspace uses an older env-var setup, and it holds no customer data.

Pulse360 sets only strictly necessary cookies, the session cookie that keeps you signed in. No advertising or tracking cookies, no third-party analytics scripts. Full detail is in the Privacy Policy.

Yes. Every connector settings page has a self-serve Disconnect control that removes the stored credential immediately and stops future syncs. It doesn't retroactively delete account data already synced from that connector. The action is logged to an audit trail so there's a record of when it happened.

Zendesk, Intercom, Salesforce, HubSpot, Pipedrive, Stripe, and Metabase sync natively. A generic webhook receiver and Zapier/Make cover anything not on that list.

About an afternoon to connect your first tool and see your first synced accounts. There's no implementation call, no onboarding project plan.

Yes, Pulse360 is solo-built. You'll hear back from the founder directly. There's no support tier to route through.

Those platforms gate pricing behind a sales call and are built for CS teams of ten or more. Pulse360 publishes real pricing and scales from one person to a team of eight, with setup measured in hours instead of weeks.