Data Processing Addendum
Operiin Data Processing Addendum
Processor and service-provider commitments, customer instructions, and data handling.
- Version
- 2.0
- Effective
- October 24, 2026
- Last updated
- October 24, 2026
- Applies to
- Operiin Training, Scheduling, Workforce, Financials, and Complete; applicable enabled services
Reference-copy notice
This published DPA is provided for reference. An executable DPA is completed through the contracting process. Viewing this page does not execute the DPA.
1. Roles
Customer is the Controller or Business and determines the purposes and means of Customer Personal Data processing.
Operiin acts as Processor, Service Provider, or Contractor where applicable and processes Customer Personal Data according to Customer’s documented instructions.
2. Instructions
Customer instructions include:
The applicable agreement
This DPA
Customer configuration
Authorized support requests
Enabled integrations
Lawful written instructions consistent with the Services
Operiin will notify Customer if Operiin believes an instruction violates applicable data-protection law, unless legally prohibited from doing so.
3. Processing scope
Data categories
Names
Work email
Employee IDs
Roles and employment status
Assigned locations
Availability
Time off
Schedules
Station assignments
Capability and trainer observations
Training assignments, content, and progress
Time and attendance
Adjustments and approvals
Financial and operating records
Business-location addresses and coordinates
Customer-entered competitor business data
User account and session metadata
Audit records
Support communications
AI Navigator prompts and action metadata, when enabled
Integration account and synchronization metadata, when enabled
Customer-uploaded files and media
Data subjects
Employees
Contractors
Managers
Administrators
Authorized customer users
Customer contacts
Processing purposes
Authentication
Scheduling
Time and attendance
Training management
Capability and trainer verification
Financial and demand planning
Operational analytics
Market planning
AI-assisted navigation
Integration synchronization
Security
Audit
Support
Billing administration
4. Sensitive-data limits
The Services are not designed for biometric identifiers, government ID numbers, medical records, genetic information, continuous employee-device location tracking, or other special-category data unless separately agreed in writing.
Business-location coordinates used for store and market planning are permitted and are not treated as continuous employee tracking.
5. Processor obligations
Operiin will:
Process Customer Personal Data only on documented instructions
Maintain confidentiality obligations
Use reasonable security measures
Limit personnel access according to business need
Assist with applicable privacy requests
Maintain applicable audit and access controls
Provide required security-incident notice
Delete or return data according to the agreement
Maintain an accurate Subprocessor Registry
Provide information reasonably necessary to demonstrate compliance
6. U.S. state privacy terms
To the extent the California Consumer Privacy Act or similar state law applies, Operiin will:
Act only for the specific business purposes stated in the agreement
Not sell or share Customer Personal Data
Not retain, use, or disclose Customer Personal Data outside the business relationship except as permitted by law
Not combine Customer Personal Data with unrelated personal data except as permitted
Notify Customer if Operiin determines it can no longer meet applicable obligations
Permit Customer to take reasonable and appropriate steps to help ensure compliant processing
Stop and remediate unauthorized use when required
7. Security controls
Authenticated access
Company and location separation
Role and permission controls
Applicable row-level data policies
Server-side authorization for consequential actions
Private file storage
Encryption in transit
Provider-managed encryption at rest
Audit records
Restricted administrative access
Versioned deployment
Backup and recovery controls
Incident-response procedures
Subprocessor review
8. Security incidents
Operiin will investigate a confirmed Security Incident affecting Customer Personal Data, take reasonable mitigation steps, notify Customer without undue delay, and provide available information about the nature and scope of the incident.
Notice is not an admission of fault.
9. Privacy-rights assistance
Operiin will provide reasonable assistance enabling Customer to respond to applicable requests for access, correction, deletion, portability, restriction, or information about processing.
Customer remains responsible for verifying the requestor and determining the appropriate response.
10. Automated and modeled processing
Operiin provides decision-support and planning outputs. Customer remains responsible for deciding whether its use of a particular output triggers notice, assessment, opt-out, accommodation, human-review, or other legal obligations.
Operiin is not instructed to independently make legally consequential employment decisions.
11. Subprocessors
Customer authorizes the subprocessors identified in the current Subprocessor Registry.
New or replacement subprocessors are handled according to the notice and objection terms in the signed DPA or Order Form.
12. International processing
Operiin is currently offered for United States-based operations unless otherwise agreed.
International processing, international transfers, Standard Contractual Clauses, localization, or country-specific addenda require a separate written agreement.
13. Return and deletion
After termination, Customer may request export of Customer Data.
Operiin will delete Customer Personal Data according to the agreement and applicable retention schedule, except where retention is required for law, security, billing, audit, backup, dispute, or enforcement purposes.
14. Audit information
Upon reasonable written request and subject to confidentiality and security limits, Operiin will provide available information reasonably necessary to demonstrate compliance.
Onsite audits, penetration tests, or extraordinary assistance require reasonable scope, scheduling, confidentiality, security restrictions, and may require a separate written agreement.
Annex A — Processing details
| Item | Description |
|---|---|
| Subject matter | Customer workforce, operating, financial, training, timekeeping, location, and market-planning information processed through Operiin services |
| Duration | The applicable agreement plus approved post-termination retention |
| Frequency | Continuous or as initiated by authorized users and enabled connections |
| Data subjects | Customer employees, contractors, managers, administrators, and authorized users |
| Personal data | Identity, contact, role, location assignment, schedule, availability, time, training, capability, account, audit, support, prompt, and integration metadata |
| Business-location data | Store addresses, business coordinates, assigned regions, and competitor business locations |
| Customer instructions | Agreement, DPA, configuration, enabled features, and authorized support instructions |
| Special exclusions | Biometrics, medical records, government IDs, continuous employee tracking, and other highly sensitive data unless separately agreed |
| Retention | Applicable agreement, Privacy Notice, and retention schedule |
Annex B — Technical and organizational measures
— Tenant isolation — customer workspaces are scoped to their own organization and locations.
— Authentication — access requires authenticated identity before application data loads.
— Authorization and row-level security — database policies restrict records to authorized membership, role, and scope.
— Administrative access — admin-level changes are restricted to approved users and logged.
— Encryption — data is encrypted in transit and at rest using managed infrastructure controls.
— Logging — material user, data, and administrative actions are recorded with actor and context.
— Backup and recovery — managed infrastructure backups with restricted access; procedures maintained as the architecture evolves.
— Incident response — documented procedures for detection, containment, assessment, notification, and corrective action.
— Change management — production changes are versioned and reviewed before deployment.
— Vendor management — subprocessors are evaluated for security, reliability, and service relevance (see Annex C).
— Secure development — code review, typed interfaces, and fail-closed access defaults.
— Vulnerability handling — reported vulnerabilities are triaged and remediated per the Vulnerability Disclosure policy.
— Personnel confidentiality — personnel with data access are bound by confidentiality obligations.