Built to protect your people data
Pulse holds some of the most sensitive information a company has: who you hire, how you pay them, and how you bill for their work. We treat that responsibility as a foundation, not an afterthought.
Our security commitments
Isolated by tenant
Encrypted in transit and at rest
Authorized on the server
Your data, always exportable
Security designed into the foundation
These are not features we added later. They are the rules the product is built on.
Strict tenant isolation
Every record is scoped to its workspace at the database level. Tenant context is derived server-side on every query, never trusted from client input. There are no cross-tenant access paths.
Authentication you control
Sign in with email magic links or Microsoft Entra single sign-on. Sessions are short-lived and provider configuration can change without a redeploy.
Authorization by default
Role-based access control is enforced on the server for every sensitive action. The interface adapts to your role, but the real boundary lives in the backend.
Encryption in transit and at rest
All traffic runs over TLS. Data is stored on managed Postgres infrastructure with encryption at rest, backed by automated backups.
A HIPAA-minded architecture
Pulse handles sensitive people data, so the platform is designed with healthcare-grade safeguards in mind: least-privilege access, isolation, and careful handling of protected information.
Responsible AI
AI assistance routes through a single governed provider with built-in house-style and safety guards. It explains its reasoning and waits for human review before changing records.
Data ownership and export
Your data is yours. You can export it, and we are transparent about what we store and why. We do not sell your data or share it across tenants.
Security as a hard rule
Tenant isolation, authorization, and data ownership are non-negotiable engineering rules. Changes that would weaken them are blocked in review, not patched later.
The principles behind every release
Tenant ID is always derived from the authenticated session, never from request input.
Plan and permission checks happen on the server. The UI is never the security boundary.
Every new data table that holds tenant-owned data is scoped to its tenant with a foreign key.
AI output is reviewable by a human before it creates business impact.
We prefer the safe sequence: migrate, verify, then roll out.
Have a security or compliance question?
We are happy to walk your team through our architecture, data handling, and access controls in detail.
Contact our team