The PairOps Platform holds the operating record of a licensed cannabis company: obligations, licenses, training, incidents, and the money around them. A record like that has to be kept safe. This page explains how, in plain terms.
Six properties of the Platform, each enforced by the system rather than by policy alone.
Every record belongs to exactly one company, and the database itself enforces that boundary on every query through row-level security. Isolation is not a feature of the application code that a bug could route around; it is a property of the storage layer. One company can never read another's records.
The Platform is invitation only. There is no open signup. Each person carries a role and per-module permissions, checked by the server on every request; the interface only hides what the server already refuses. Board-level artifacts require owner or admin authority, and everyone can always see the work assigned to them.
Every connection runs over TLS 1.2 or newer, and all stored data is encrypted at rest with AES-256. The most sensitive fields, license numbers among them, are encrypted a second time at the application layer with versioned, rotatable keys held in a separate vault. Reports and exports reference licenses by label; the numbers themselves never appear in an export.
AI on the Platform produces drafts and structured reads for a person to review. It never takes autonomous action on a compliance, financial, or personnel decision, and where it cannot verify something, it flags the gap for a person to check.
Your data never trains AI models and is never shared with another company. Every AI feature carries a daily usage cap.
Unrecognized values are refused loudly. If a rate limiter or safety check cannot complete, the request is denied. Regulatory content enters the Platform only through human review; content that loses its verified status is pulled automatically, and a failure in that process is treated as a compliance incident and alerts immediately.
Acknowledgments are append-only. Completions carry who did the work and when. Closed periods stay closed. Audit exports list document names and dates while the underlying files stay behind expiring, signed links.
The Platform runs on SOC 2 Type II certified cloud infrastructure with automated, encrypted daily backups.
Write to the security desk and a person answers. Nothing on this page is a substitute for asking.