Sign-in is only the first step
Clerk handles sign-in. NPS checks product access separately, and an approved account requires explicit activation.
Security & trust
Clear access.
Accountable records.
Operational software earns trust in the details: who can access it, how records change, and what a number actually means.
Protected connections
Production website and API connections use HTTPS. Account and work requests require the appropriate authenticated access.
History that keeps its context
Current Personal Work corrections and voids preserve history. An estimated pay value stays distinct from a payment.
Permissions that fit the interface
The public website does not request your location. Field permissions and offline behavior depend on the released client and workflow.
Recovery has limits
There is no published recovery-time guarantee or backup schedule. Do not assume every workflow works offline or every field change has already synced.
Privacy still needs clear boundaries
Website and Early Access retention rules are published in the Privacy Notice. The privacy-request email channel still needs setup and testing before broader enrollment; support-access details also remain to be finalized.
Know what you’re sharing.
Early-access requests use Google Forms. Avoid sensitive operational or personal records in your request.
Read the website and early-access notice for information about collection, services, and the privacy details still to be completed before broader enrollment.
Read the Privacy Notice