Trust starts with clear boundaries and supportable claims.
This page describes the current OperationOS public website. It does not extend security or certification claims beyond what is established for this website.
Protect the paths where information enters the website.
Collect for a defined purpose
Public forms ask for information tied to a specific action, such as requesting RecruitOS access or sharing website feedback.
Keep privileged credentials on the server
Privileged configuration used by the feedback storage path is kept in server-only code. Public browser code uses publishable configuration for the waitlist workflow.
Validate before processing
Public submission paths check required input and expected formats before processing. These controls reduce avoidable input errors but do not remove every security risk.
Website services should be visible in the privacy explanation.
OperationOS uses service providers to host the website, process form submissions, send waitlist email, store feedback, and understand website usage. The Privacy Policy explains these activities at a practical level.
Read the Privacy PolicyConsequential recommendations require human review.
RecruitOS can organize candidate information and explain recommendation context. The people responsible for hiring review that context and decide what happens next.
Send security concerns through the established contact path.
Include enough detail to understand the concern, but do not send passwords, credentials, or sensitive personal information by email.