Trust
Security
How PayClarity is built to keep each organization's data its own. This page describes how the product works; it is not a certification.
Each organization's data is separate
- Every table carries the organization it belongs to, and the database itself checks every read and write against the signed-in person's membership and role. A page or request that forgot to check would still be refused.
- Employees see only their own finalized statements.
- PayClarity staff who run the service see organizations, plans and usage counts. They cannot read your employees, pay rules or payroll.
Payroll that cannot quietly change
- Finalized runs and published pay rules are locked. Corrections are new, visible records.
- Every change that affects pay records who made it, when and why, in a history that cannot be edited or deleted.
- The person who prepares a run cannot approve it, unless your organization chooses otherwise.
Credentials and payments
- Logins to your connected systems are kept in an encrypted vault, never in ordinary tables or logs.
- Card details are entered on Stripe's pages and stay with Stripe; PayClarity never sees or stores them.
- Messages from Stripe are accepted only when their signature checks out, and each is applied once.
Where data is kept
PayClarity runs on Supabase, with its database hosted in the United States. Payments are handled by Stripe.
Reporting a problem
If you think you have found a security issue, please contact us with "Security" in the subject, and do not include anyone's personal data.