Legal · Privacy
How OpsRail Command Center handles data during demos, pilots, and early product evaluations.
How your data flows through the product during an early evaluation.
Early-evaluation document
This page is provided for early evaluation and pilot discussions and should be reviewed by legal counsel before production use. It is not a substitute for a formal Data Processing Agreement, Business Associate Agreement, or jurisdiction-specific privacy notice.
Section 01
OpsRail Command Center is designed for operational analysis of Medicare Advantage supplemental benefit workflows. Early pilots should use synthetic, masked, or de-identified operational files. This policy explains how data flows through the product during demos, pilots, and early evaluations.
Section 02
Section 03
For MVP and pilot evaluation, you should not upload any of the following. The product is designed to deliver operational value without them:
See the Data Requirements page for the complete schema and the fields that can be hashed instead of sent raw.
Section 04
Section 05
The product may send structured incident evidence to OpenAI or another configured AI provider to generate briefs or copilot answers. Raw uploaded files do not need to be sent to the AI provider for the MVP brief generation flow.
AI outputs are grounded in structured evidence but may be incomplete or inaccurate, and should be reviewed by qualified users before being shared or acted upon. The deterministic incident engine remains the source of truth.
Section 06
We do not sell user data.
We may share limited data with service providers needed to operate the product — such as hosting, database, analytics or logging, and AI providers — solely to deliver the service. We may also disclose information if required by law or to protect the integrity and safety of the service.
Section 07
During pilots, uploaded files, parsed records, incidents, and briefs may be retained for the duration of the evaluation unless deletion is requested. Pilot data can be deleted upon request, subject to reasonable backup and log retention limitations.
Section 08
We use reasonable technical and organizational safeguards appropriate for an early MVP, including:
Honest disclosure: the MVP is not yet SOC 2 or HITRUST certified. See the Security posture page for the current pilot-readiness overview.
Section 09
The recommended pilot mode uses synthetic, masked, or de-identified operational files. If a future production workflow involves PHI, additional agreements, safeguards, access controls, and potentially a Business Associate Agreement may be required before any PHI-bearing data is processed.
Section 10
Section 11
OpsRail Command Center is intended for business users — typically operations, compliance, and benefits professionals — and is not directed to children. We do not knowingly collect information from children.
Section 12
This Privacy Policy may be updated as the product evolves. Material changes will be reflected by updating the “Last updated” date at the top of this page.
Section 13
Questions about this Privacy Policy or how data is handled during a pilot? Reach out to hello@opsrail.app.
Companion documents