Privacy built around controlled project access.
How the public ORQIV website and secured ORQIV services handle account, project and technical information at a high level.
Public website
Public browsing may create standard technical records such as request, device, browser, security and performance information needed to deliver, monitor and protect the service.
Account & authentication
When a user signs in, account information may be processed to authenticate the user, enforce access controls, support MFA, maintain sessions and protect authorized workspaces.
Project information
Project information is used to provide authorized ORQIV functionality, project-scoped access, workflows, reporting, support and auditability. Customer project information is not intentionally published on the public website.
Access boundaries
Access is intended to remain role-aware and project-scoped. Users should only access information they are authorized to use and should not share credentials or protected project material outside approved channels.
Service providers & infrastructure
ORQIV may rely on controlled infrastructure and service providers to operate authentication, hosting, storage, communications, monitoring or related application functions. Applicable contractual and jurisdiction-specific terms govern those services where required.
Questions & requests
Privacy or data-handling questions can be sent through the official ORQIV support channel. Do not send passwords, API keys or other secret material by email.