Policies & commitments

We collect only what the service needs to run: account details (name, work email, phone), operational records your organization enters into RigOps, and technical logs used for security and reliability. We do not sell personal data, we do not use your operational data to advertise, and we do not share it with third parties except the infrastructure providers under contract that host the service.

You can request a copy, correction, or deletion of your personal data at any time by writing to {{ emailText }}. Operational records belong to your organization and are governed by its agreement with us; deletion requests for those route through your organization's administrator.

Cookies on this website are limited to what is needed for the site to function. We do not run third-party advertising trackers.

RigOps is provided under a subscription agreement between People Nexus Technologies Pvt. Ltd. and your organization. The agreement defines the service levels we commit to — including uptime targets, support response times (first response within one business day), and maintenance windows announced in advance.

Your organization retains full ownership of the data it enters. On termination, we provide complete exports in standard formats (Excel, PDF, and structured data) and delete production data on a documented schedule. Custom-built platforms are delivered under separate engagement contracts with source-code and IP terms agreed per project.

We never make silent breaking changes: API contracts and data schemas evolve through versioned, documented releases.

Each customer organization is a strictly isolated tenant: data is scoped at every layer of the platform, access fails closed (a user with no assigned scope sees zero records), and every read and write is attributable to an authenticated user. All data is encrypted in transit and at rest.

Hosting region is agreed per contract — including on-premise and private-cloud deployment for operators with data-residency requirements. Backups run continuously with tested restore procedures. A signed Data Processing Agreement, sub-processor list, and full security documentation are available to customers and qualified prospects on request.

The RigOps analyst is read-only by design: it can query and analyze, but has no ability to create, modify, or delete records. It answers only from data the asking user is already authorized to see — the same scope rules that govern the rest of the platform govern the AI.

Answers cite the records they are grounded in, so every claim can be verified against the source. The AI core is provider-neutral: customers choose the model provider (including fully local deployment), and operational data is never used to train shared models.

We state plainly what the AI cannot do, and we treat every AI feature as a decision-support tool — accountable people, not models, approve reports and sign records.