Security
How Pulse360 handles data — in plain language.
Where your data lives
Pulse360 is built on Supabase, a managed Postgres database hosted on AWS. Every workspace's data is isolated from every other workspace at the database level (row-level security), so one customer can never see another's data.
Encryption
All traffic between your browser and Pulse360 is encrypted in transit (TLS). Data is encrypted at rest in the database, and connector credentials (API keys and tokens) are additionally encrypted at the application layer before storage.
No data shared with third parties
We do not sell your data, and we do not share it with third parties for marketing or advertising. The only outside parties involved are the infrastructure and AI providers required to run the product itself, plus any integration a workspace admin explicitly connects. The full, current list of every subprocessor is in our Privacy Policy.
How AI insights are generated
AI insights and QBR briefs are generated server-side only, by calling Anthropic's Claude API — never from your browser. Only the account data needed to generate that specific insight is sent, on request, and it is processed under Anthropic's API terms.
This demo runs on seeded data
You're currently browsing the public demo workspace, which runs entirely on fictional, seeded demo accounts — no real customer data is stored here. AI insights and QBR briefs you see in this demo are pre-written mock responses, not live Claude API calls, so nothing you view here is sent to any AI provider. Sign up for your own workspace to connect real tools and generate real AI insights.
Questions about security
For anything not covered here — including questions from your security or compliance team, or a request for our Data Processing Agreement (DPA) — reach us directly at hello@getpulse360.com.