PayLocums Security
PayLocums is built for locum tenens staffing agencies that trust us with payroll, timesheets, and billing. This page describes the security controls we have in place today. It is not a certification, and it is not a list of things we plan to add later.
If you are a customer and need our full security documentation, we can share it with you on request under a non-disclosure agreement. Email security@paylocums.com (subject: “Security documentation”).
Hosting and encryption
PayLocums is hosted on Cloudflare, including Cloudflare Workers and the D1 database. All connections to our website and application use TLS (HTTPS). Data in our database and file storage is encrypted at rest by Cloudflare, using provider-managed keys. Tokens we keep for optional integrations, such as email or accounting connections, are also encrypted at the application layer.
Sign-in and access
People who use the PayLocums application sign in without a password, using a one-time code sent to their email or a passkey.
Our internal console — the tools we use to operate the platform — sits behind Cloudflare Zero Trust and uses Microsoft Entra ID single sign-on, with passkey sign-in. Console sessions last one hour. Sign-in to the Cloudflare and Stripe dashboards is also required to go through Microsoft Entra SSO. If a team member’s Microsoft account is disabled, their console access is removed automatically through SCIM provisioning to Cloudflare Zero Trust.
Access inside the application is role-based and limited to what each person needs. Each agency’s data is kept separate, so agencies never see one another’s information.
Payments and bank details
PayLocums does not store bank login credentials, or bank account and routing numbers. Payroll and payment processing are handled by our partners, who collect bank and tax details on their own screens. We also do not store Social Security numbers, tax IDs, or dates of birth.
How we build and review software
We review changes before they go out, and we run automated checks in our continuous integration pipeline, including dependency scanning (Dependabot and npm audit), secret scanning (gitleaks), and static analysis (Semgrep).
Backups and recovery
We keep encrypted nightly backups of the application database and use Cloudflare D1 Time Travel, which lets us restore the database to a point in time if data is damaged.
If something goes wrong
We have a written incident response process. If we become aware of a security incident that results in unauthorized access to Customer Data in our systems, we will notify the affected customer without undue delay, as described in our Terms of Service and Privacy Policy, and we will take reasonable steps to contain and remediate the incident.
Reporting a vulnerability
If you believe you have found a security issue, please email security@paylocums.com with the subject “Security report,” and include what you found and how to reproduce it. Please do not open a public issue, access other customers’ data, or run denial-of-service tests. We acknowledge reports within two business days and aim to fix confirmed issues quickly, with notice to affected customers where Customer Data is involved.
You can also find this contact in our security.txt file.
Contact
PayLocums LLC
Email: security@paylocums.com
Mailing address: 1 E Broward Blvd, Ste 1230, PMB 497783, Fort Lauderdale, FL 33301-3330
Questions about privacy should go to privacy@paylocums.com.