Security & Compliance
Operiin Subprocessor Registry
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
Security & Compliance
Operiin Subprocessor Registry
This page identifies third-party service providers that may process customer data while supporting Operiin Core, Optional Modules, billing, security, communication, and application delivery.
Current Subprocessors
| Provider | Service | Role | Data Handled | Region | Modules | Status | Added |
|---|---|---|---|---|---|---|---|
| Supabase | Database, authentication, storage | Processor | User accounts, schedules, competencies, operational data, uploads, audit records | Primary project region: United States | All | Current | 2026 |
| Cloudflare | DNS, CDN, security protection | Processor (network security & delivery) | Network traffic and request metadata | Global network | All | Current | 2026 |
| Resend | Transactional email delivery | Processor | Email addresses and delivery metadata | Primary region: United States | All | Current | 2026 |
| Stripe | Payment processing | Payment services — independent controller for certain payment data under its own terms | Billing information and payment metadata | Primary region: United States | Billing | Current | 2026 |
| Vercel | Application hosting and delivery | Processor | Application delivery metadata | Primary region: United States | All | Current | 2026 |
Region note: where a primary project region is listed, network delivery, security telemetry, support access, or provider-controlled processing may occur in additional regions as described in the provider’s documentation and applicable agreement. Legal role classifications reflect review of each provider’s current terms and may differ per processing activity.
Subprocessor Standards
Need-to-Know Access
Subprocessors receive only the information reasonably required to perform their services.
Contractual Safeguards
Subprocessors are expected to maintain confidentiality, security, and data-handling obligations appropriate to their services.
Security Review
Operiin evaluates subprocessors for security, availability, operational reliability, and service relevance.
Ongoing Monitoring
Material vendor changes are reviewed periodically and may be reflected on this page.
Optional Module Processing
Optional Modules (Multi-Unit Management, Executive Intelligence, Data Intelligence & Reporting, Security & Audit, SSO / Identity, and Additional Identity Provider) may expand the categories of customer data processed inside Operiin, such as audit activity, reporting exports, multi-location records, identity-provider metadata, or executive-level summaries.
If an Optional Module requires a materially different subprocessor, Operiin may update this registry before or when that provider becomes applicable.
Customer-Controlled Services
Certain features, such as SSO / Identity configuration, may depend on customer-controlled identity providers, domains, or internal access policies. Those customer-controlled systems are not Operiin subprocessors.
Subprocessor Change Policy
Operiin may add, replace, or remove subprocessors as the platform evolves.
Material changes are reflected on this page — with a change effective date and, for contracted customers, notification through the account contact — before becoming effective where practicable. Removed providers remain listed with a removed status through their wind-down period.
Contracted customers with a DPA in place may object to a new subprocessor on reasonable, documented data-protection grounds within the notice period by contacting legal@operiin.com. Each provider’s own privacy and security documentation is available on that provider’s public trust pages.
Questions
Questions regarding subprocessors may be directed to: