comPayr is building payroll calculation software for business customers and workforce access. We design the Service to protect payroll, tax, records, and workforce data using layered safeguards appropriate to the Service and its launch stage.

This page is a summary of our current posture and should not be read as a promise of any specific certification, uptime target, or audit status unless separately stated in writing.

We use account-authentication controls, session protections, role-based product access patterns, and related operational safeguards designed to reduce unauthorized access risk.

Public and customer-facing workflows may use MFA, session cookies, account verification, and direct worker-access controls depending on the product flow and customer setup.

We aim to limit access to payroll and workforce data to what is reasonably necessary to operate, support, secure, and improve the Service.

Our launch-stage environment is intended to be U.S.-hosted and U.S.-processed. We use technical and organizational safeguards designed to protect payroll records, generated documents, tax-form preparation data, and related service information.

We rely on specialized third-party providers for categories such as hosting, authentication, analytics, communications, and address support.

We manage those providers through vendor selection, contractual controls, and service-design choices appropriate to the function they perform.

We use operational monitoring, analytics, and error-observability tooling to detect product issues, reliability concerns, and potential misuse.

If we confirm a security incident affecting personal data processed on behalf of a customer, our DPA describes the framework under which we will notify the customer and support its response obligations.

Operational availability updates and customer-facing service notices are published through our Status / service updates page when we decide public notice is appropriate for the incident or degradation involved.

For the public site and core application flows, comPayr is working toward a WCAG 2.1 AA standard as its practical accessibility baseline.

That means accessibility issues are treated as product quality issues, not optional polish. We use automated accessibility checks and targeted manual keyboard and screen-reader review on key public flows.

Security is shared. Customers are responsible for managing user access, protecting credentials, reviewing payroll outputs, maintaining accurate data, and using the Service in a lawful manner.

Customers should also ensure they maintain appropriate internal controls for payroll approvals, workforce administration, and external provider relationships.

For more detail on how comPayr handles personal data and vendor relationships, see our Privacy Policy, Data Processing Addendum, and Subprocessors page.

Questions about security or trust matters may be sent through our public contact flow. Responsible-disclosure style reports should use the dedicated Security reporting page.