Skip to document
OPER•I•IN
PricingAbout UsFAQ
01Pricing→02About Us→03FAQ→

Trust Center

  • Overview
  • Security
  • Privacy Notice
  • Terms of Service
  • EULA
  • Data Processing Addendum
  • Subprocessors
  • Data Location & Hosting
  • Compliance & Governance
  • Acceptable Use
  • Availability & Support
  • Vulnerability Disclosure

Security

Built for separated company workspaces.

Archived source-rendered publication captured October 24, 2026. This is a historical reference, not proof of the terms accepted by a particular customer. Original dates and placeholders are preserved.

Version
legacy-2026-10-24
Effective
Not specified in archived document
Last updated
Captured October 24, 2026
Applies to
Archived pre-revision publication
Current version (2.0)

On this page

  1. Built for separated company workspaces.
  2. Organization-Level Segregation
  3. Row-Level Security
  4. Role-Based Access
  5. Audit Logging
  6. File Isolation
  7. Fail-Closed Access
  8. Control Matrix
  9. Security Architecture
  10. Authentication
  11. Membership Verification
  12. Location Scope
  13. Admin Restrictions
  14. Illustrative Default Role Model
  15. Incident Response
  16. Vendor Management
  17. Backup and Recovery
  18. Audit Controls
  19. User Actions
  20. Data Changes
  21. Administrative Actions
  22. Investigation Support
  23. Monitoring and Enforcement
  24. Service Integrity
  25. Security Program Roadmap

Security

Built for separated company workspaces.

Operiin is designed so each company's data remains isolated by organization, location, user role, and access permission.

Organization-Level Segregation

Each customer workspace is scoped to its own organization and locations. Data queries require organization membership before records are returned.

Row-Level Security

Database access is controlled through row-level security (RLS) policies tied to authenticated user membership and organization scope. If scope cannot be verified, no customer records are returned.

Role-Based Access

Owners, admins, district managers, general managers, assistant managers, and employees receive different read/write permissions.

Audit Logging

Key actions are logged with actor, timestamp, organization, location, record type, and change context.

File Isolation

Imports and uploads are stored in organization-scoped paths. File access requires organization and permission match.

Fail-Closed Access

If organization, membership, location, or role scope cannot be verified, access is denied. The system does not default to permissive access.

Control Matrix

Each material control maps to a purpose, an enforcement mechanism, an evidence source, and an honest status. Last control review: July 2026 · Owner: Platform engineering.

AreaControlPurposeStatusEnforcementEvidence
Identity & authenticationAuthenticated identity requiredNo application data loads without a verified session.ImplementedManaged authentication with session verification on every application route.Unauthenticated requests to protected routes are redirected or denied.
Authorization & tenant isolationOrganization-scoped accessPrevent cross-organization record access.ImplementedAuthenticated organization-membership and role checks on data access paths.Fail-closed denials when membership or scope cannot be verified.
Database & row-level controlsRow-level security policiesEnforce tenant boundaries at the database layer, not only in application code.ImplementedRLS policies tied to authenticated membership and organization scope on production tables holding tenant data.Policy-enforced access denials independent of application logic.
Application securityServer-side permission re-checksPrivileged operations re-verify authority on the server.ImplementedRole and ownership verification inside server actions and API routes before writes.Owner-gated billing and administrative operations.
Encryption & transportEncryption in transit and at restProtect data moving to and stored within the service.Provider-managedTLS for transport; at-rest encryption via managed infrastructure providers.Provider security documentation (see Subprocessor Registry).
Logging & auditabilityAudit-event captureMaterial actions remain traceable to an actor and context.ImplementedAudit records for authentication, data changes, permission changes, and administrative actions.Retained audit records supporting investigation and review.
Secure change managementVersioned, reviewed deploymentProduction changes are attributable and reversible.ImplementedVersion-controlled source with reviewed deploys through the hosting pipeline.Deployment and commit history.
Availability & recoveryManaged infrastructure backupsRecover service data after infrastructure failure.Provider-managedManaged database backups within the configured project.Provider backup configuration.
Availability & recoveryRecovery testing programDemonstrate restore procedures work as documented.PlannedScheduled restore exercises as production architecture matures.To be published with the assurance roadmap.
Incident responseDocumented incident processConsistent handling of suspected security events.ImplementedDocumented lifecycle: detect, triage, contain, investigate, recover, notify, review.Public summary below; internal playbook maintained privately.
Vendor & subprocessor managementSubprocessor inventoryKnow which providers touch customer data, and in what role.ImplementedPublished registry with service, legal role, data categories, and region.Subprocessor Registry page.
Vendor & subprocessor managementFormal vendor-risk reviewsPeriodic reassessment of provider posture.PlannedRecurring review cycle per provider.To be published with the assurance roadmap.
Customer administrationCustomer-controlled users, roles, and locationsThe customer decides who can access what.Customer configuration requiredInvitation, role-assignment, and location-scope tools inside the customer workspace.Customer administration settings.
Independent assuranceSOC 2 / ISO 27001 certificationThird-party attestation of the control environment.Not claimedNo independent certification is claimed unless expressly published here.See the assurance roadmap on the Trust Center overview.

Security Architecture

Authentication

User access requires authenticated identity before application data is loaded.

Membership Verification

Each request is checked against organization membership and assigned role.

Location Scope

Multi-location users only see locations assigned to their permission scope.

Admin Restrictions

Admin-level changes are restricted to approved users and logged for review.

Illustrative Default Role Model

Actual permissions may vary by customer configuration, enabled modules, organization hierarchy, and contractual scope.

RoleRead ScopeWrite Scope
OwnerAll locationsAll · billing · users
AdminAll locationsOperations · settings
District ManagerAssigned locationsAssigned locations
General ManagerOwn locationSchedule · competency · availability
Assistant ManagerOwn locationLimited schedule · limited competency
EmployeeOwn schedule · own trainingOwn availability

Incident Response

Operiin maintains an incident-response process for identifying, assessing, containing, remediating, and reviewing suspected security events affecting the service or Customer Data. The public lifecycle below summarizes it; the detailed internal playbook — detection thresholds, contact trees, containment procedures, and tooling — remains private.

01 Detect and receive — monitoring signals, audit review, customer reports, and the vulnerability-disclosure channel.

02 Triage and classify — assess severity, scope, and affected organizations.

03 Contain — restrict access or disable affected credentials where needed, preserving evidence.

04 Investigate — review audit records and affected organization scope.

05 Eradicate and recover — remediate the cause and restore normal service.

06 Notify affected customers where required by law or agreement.

07 Document lessons and corrective actions in a post-incident review.

Customer notification standard: when Operiin determines that a confirmed security incident affects Customer Data, Operiin will notify affected customers without unreasonable delay and in accordance with applicable contractual and legal obligations. Service disruptions are additionally reflected on the status page. Customers are responsible for onward notification obligations that apply to their own organization.

Vendor Management

Operiin uses subprocessors for hosting, authentication, database services, storage, payment processing, monitoring, email, and application delivery.

View Subprocessor Registry →

Backup and Recovery

  • — Production systems utilize managed infrastructure backups.

  • — Recovery procedures are maintained and reviewed as the production architecture evolves.

  • — Backup access is restricted to authorized personnel.

  • — Recovery testing may be performed as operational requirements evolve.

Specific backup architecture and retention periods may change as infrastructure evolves. Operiin does not represent that independent disaster-recovery certification or a fixed recovery objective applies unless stated in a signed agreement.

Audit Controls

User Actions

Authentication events, login activity, session events, and account changes.

Data Changes

Schedule edits, competency verification, trainer status changes, sales imports, and settings changes.

Administrative Actions

Permission changes, location assignments, membership updates, and account administration.

Investigation Support

Logs support incident response, security review, compliance review, and misuse investigation.

Monitoring and Enforcement

Operiin maintains audit records relating to user activity, permission changes, data imports, exports, schedule modifications, competency updates, trainer verification activity, and administrative actions.

These records may be reviewed for security, compliance, misuse detection, service integrity, investigation of policy violations, and legal compliance.

Service Integrity

Operiin maintains controls to protect customer data, operational records, access permissions, audit logs, and platform calculation outputs.

Security Program Roadmap

Operiin continuously evaluates security, compliance, audit, and operational controls as the platform grows.

Future certifications, audits, or assessments may be pursued based on customer demand, business requirements, and operational maturity.

Platform overviewPricingTrust CenterSystem statusSupportVulnerability disclosureSign in

© 2026 Wenraw Distributors, DBA Operiin.