Trust

Security& trust.

OpCor is the software operating layer for critical operations: process, work orders, safety, compliance and supply. That data is operational and often sensitive, so security is built into how the platform is designed, hosted and changed.

Last reviewed: 2026-10-07

Section 1

Data protection

Encryption in transit. All traffic to and from the application is served over HTTPS/TLS. Connections between the application and its database run over TLS as well, validated against the database provider's certificate authority. Plain-text transport is not used.

Encryption at rest. Customer data is stored in a managed database and managed object storage that encrypt data at rest at the provider level.

Tenant isolation. OpCor is multi-tenant. Every data query is scoped to the requesting customer's account, so one customer's data is not returned in another customer's context. Tenant scope is derived from the authenticated session, never from a value the caller supplies, and that rule is enforced at each module's data-access layer, at the module-entitlement gate, and on the AI assistant plane. This was audited end-to-end in July 2026 and verified by live cross-tenant testing against separate tenants.

File storage. Uploaded documents and attachments are stored in private object storage and served only through short-lived, signed URLs generated per request: links are not public and expire automatically. Session credentials are never placed in file URLs.

Upload validation. Uploaded files are validated by inspecting their actual contents, not the file name or the type the browser reports, before any further processing.

Section 2

Access control

Authentication. Users authenticate with credentials; sessions are carried as signed, expiring tokens. Passwords are stored only as salted hashes, never in plain text.

Session revocation. Sessions can be revoked. Changing a password, an administrator resetting a password, deactivating an account, or changing a user's role invalidates that user's existing sessions on their next request: access ends promptly rather than lasting until a token expires.

Role-based authorization. Access follows least privilege through defined roles (standard user, company administrator, and platform administrator). Administrative actions are restricted to the appropriate role and are scoped to the administrator's own organization unless they hold platform-level authority.

Administrative access. Access to production infrastructure (servers, database, storage) is limited to a small number of authorized operators. Application environments connect to the database using least-privilege, per-environment credentials rather than an administrative account. Staff access to a customer's data is recorded in an access log.

Section 3

Infrastructure, availability & recovery

Hosting. OpCor runs on a major cloud provider's infrastructure in US regions, on a managed database cluster and managed object storage, behind a hardened reverse proxy. The database cluster accepts connections only from our own application hosts and a restricted administrative address.

Backups. The managed database is backed up automatically on a daily schedule with multi-day retention and point-in-time recovery, enabling restoration to a chosen moment if needed. A backup is also taken automatically before any schema change is applied. A nightly, encrypted copy of the database and of every customer file is also kept off-site with a separate storage provider, independent of our hosting provider. A file has been restored from it with the hosting provider out of the loop, and matched exactly. Backups are kept for up to about 30 days.

Disaster recovery. We maintain a written disaster-recovery runbook covering restore procedures and the recovery path for the database and application.

Separation of environments. We operate isolated production and staging environments with separate databases and separate database credentials, so changes are validated away from customer data before release. Staging contains no customer data.

Section 4

Secure development & change management

Version-controlled, reviewed changes. All changes are made through version control. Nothing reaches production without flowing through staging first.

Continuous integration. Every change runs an automated test suite and a type-checking gate in CI before it can be released; a failure blocks the release.

Supply-chain integrity. Our build pipeline verifies dependency integrity against signed registry metadata and hard-blocks any deployment on a signature mismatch, defending against tampered or hijacked dependencies. We receive automated security advisories for our dependencies and remediate them in batches, prioritising anything reachable from user input; a formal remediation cadence is on our roadmap below.

Security review. The application undergoes internal security review, including a full-application audit completed in July 2026 whose findings were remediated and verified in production.

Section 5

Monitoring & auditability

Security- and operations-relevant events (administrative changes, key actions across modules) are recorded to an audit trail. Application and server logs are collected for operational visibility and troubleshooting. Errors and availability are tracked with dedicated monitoring services. Error reports carry the affected user and company, and are scrubbed of customer data at the source.

Section 6

Data handling

Retention & deletion. Deletions are handled as recoverable soft-deletes for a retention window, after which data is permanently removed from storage. Customers can request export or deletion of their data.

Sub-processors. OpCor relies on a small set of vetted service providers in the categories below. A current list of them by name is available on request at info@opcor.ai.

  • Cloud hosting: application hosting, managed database, and object storage (US), including this website.
  • AI providers: AI-assisted features, under terms that do not allow them to use your data to train their models.
  • Transactional email: platform email (e.g., invitations and password resets).
  • Off-site backup storage: encrypted copies of the database and customer files.
  • Error monitoring: receiving user and company identifiers and no customer records.
  • Availability monitoring: receiving no customer data.
  • Website services: email from our website forms, appointment booking, and visit counts without cookies. These do not receive platform customer data.
Section 7

On our roadmap (transparency)

We believe in being clear about what we're still strengthening rather than over-claiming. In progress:

  • Multi-factor authentication enforced across all administrative/provider consoles.
  • A formal, scheduled cadence for remediating dependency advisories (we receive and triage alerts today; the fixed cadence is not yet in place).
  • A disaster-recovery restore exercised by someone other than the engineer who built it.
  • A third-party penetration test ahead of broader scale.
  • Alignment of our controls to the SOC 2 Trust Services Criteria (we are not yet SOC 2 attested).
Section 8

Security contact & responsible disclosure

If you believe you've found a security issue, please contact info@opcor.ai. We welcome responsible disclosure and will acknowledge reports promptly.