Payroll data is the most sensitive data a small business holds.
So this page is split into what is actually built, what the architecture is designed for, and what PayPulse does not claim. You will not find a certification badge here that we have not earned.
Built and working today
You can verify every item on this list inside the demo.
Role-based access control
Four roles with explicit permission sets. A location manager is scoped to one location and cannot read pay rates — enforced by the data layer, not hidden by the interface.
Least-privilege data access
Every screen reads through a single repository that filters by role before anything reaches a component.
Sensitive-field masking
Tax identifiers, bank accounts, and the company EIN are masked everywhere they appear, including in exports.
Audit logging
Approvals, exception acknowledgements, timecard decisions, and incident actions are recorded with actor and timestamp.
No real identifiers in the demo
The seeded company is fictional. There are no real Social Security numbers, bank accounts, or people in this data set, and none should ever be added.
No secrets in the repository
The demo runs with no environment variables and no credentials. There is nothing to leak because there is nothing connected.
Designed for, not delivered
The architecture supports these. None of them exists in this build, and the wording here is deliberate.
Multi-factor authentication
The user model carries an MFA flag and the role system is built for step-up authentication on approval actions. There is no authentication in this build at all.
Encryption in transit and at rest
The architecture assumes TLS everywhere and encrypted storage with field-level encryption for identifiers. This demo stores nothing on a server.
Session timeout
A 30-minute idle timeout is the design target for a product handling payroll data. The demo has no sessions.
Export controls
Exports are gated to owner and payroll-admin roles today. Watermarking, export logging, and download expiry are planned.
Secure document access
Pay stubs and tax documents would be served through short-lived signed URLs scoped to the requesting worker.
Penetration testing and third-party audit
Required before any real payroll data enters the system. Not done, because there is no system to test yet.
Integrations
Where a licensed provider would connect
Payroll is a regulated business. These are the seams a production build would fill with licensed partners. None of them is connected here.
- Payment rails / ACH originatornot connected
- Payroll tax engine & filing agentnot connected
- Bank account aggregationnot connected
- Identity & bank verificationnot connected
- Benefits carrier feednot connected
- Accounting ledger syncnot connected
What this page does not claim
- No SOC 2, ISO 27001, or any other certification
- No third-party security audit or penetration test
- No insurance coverage or financial guarantee
- No regulatory approval or money-transmitter licensing
- No compliance guarantee of any kind
A payroll product that overstates its security posture is worse than one that has none, because people trust it with real money and real identifiers. This is a demonstration build and should be treated as one.