Data Processing Addendum
Last updated November 26, 2026 · Governed by the laws of the State of Georgia
You decide what employee data to enter and why. We process it only to run the Service for you, keep it secure, use listed subprocessors, tell you promptly about breaches, and delete it when you leave.
1. Scope and definitions
This Data Processing Addendum (“DPA”) forms part of the Terms of Service between the Customer and OnboardOps (“Provider”) and applies to Personal Information in Customer Data that the Provider processes on the Customer's behalf. Terms such as “controller,” “processor,” “business,” “service provider,” “processing” and “personal information” have the meanings given in applicable data-protection law. If a conflict arises, this DPA controls for the processing it covers, and the Terms control otherwise.
2. Parties and processing roles
For Customer Personal Information, the Customer is the controller (or “business”) and OnboardOps is the processor (or “service provider”). Where the Customer is itself a processor for its own clients, OnboardOps acts as a subprocessor and the Customer will ensure its instructions are consistent with its own obligations. For account-level information about the Customer's personnel, OnboardOps acts as an independent controller as described in the Privacy Policy.
3. Roles
The Customer determines the purposes and means of processing employee data (controller or business). The Provider processes it only to provide the Service (processor or service provider).
4. Instructions and restrictions
The Provider will process Customer Personal Information only on the Customer's documented instructions, which are the Terms, this DPA, and the Customer's configuration and use of the Service. The Provider will not:
- sell or share the information;
- retain, use or disclose it for any purpose other than providing the Service (including any commercial purpose of its own), except as the law permits; or
- combine it with other information, except as the law permits.
The Provider will tell the Customer if it believes an instruction violates applicable law.
5. Confidentiality of personnel
Personnel with access to Customer Data are bound by confidentiality obligations and are given access only as needed to operate, secure and support the Service.
6. Security
The Provider maintains technical and organizational measures appropriate to the risk, listed in Annex II, and will not materially reduce them during the term.
7. Subprocessors
The Customer authorizes the subprocessors in Annex III. The Provider will bind each to data-protection terms at least as protective as this DPA and remains responsible for their performance. The Provider will post changes to the list here, and the Customer may object on reasonable data-protection grounds by contacting us through the contact form within 14 days of the change. If the parties cannot resolve the objection, the Customer may stop using the affected part of the Service.
8. Assistance
Taking into account the nature of the Service, the Provider will reasonably help the Customer respond to requests from individuals to exercise their rights, and with security, breach-notification and impact assessments, at the Customer's request. The Customer can use features such as CSV export and printable dossiers to retrieve data. Reasonable additional assistance may be limited where it would require disproportionate effort.
9. Requests from individuals
If we receive a request from an individual about Customer Personal Information, we will not respond except to tell them to contact the Customer, unless the law requires otherwise. We will provide the Customer with reasonable tools and assistance, such as export features and printable records, to find, correct and delete information so the Customer can respond within the time the law allows.
10. Impact assessments and regulators
On request and at the Customer's cost where the work is substantial, we will give the Customer information reasonably needed for a data protection assessment, and reasonable help in dealing with a regulator about our processing under this DPA.
11. Security incidents
The Provider will notify the Customer without undue delay after becoming aware of a confirmed breach of security that leads to unauthorized access to Customer Personal Information, and will provide information reasonably available to help the Customer meet its own notification duties, including the nature of the incident, likely consequences and steps taken.
12. Incident process
On learning of an incident affecting Customer Personal Information, we will contain it, investigate, tell the Customer, share what we know and what we are doing, and cooperate with the Customer's reasonable requests. Our notice does not mean we accept fault. Notifications will go to the Owner contact in the Workspace.
13. Return and deletion
On termination, the Provider will, at the Customer's request, make a staff-directory export available, and will then delete or de-identify Customer Personal Information within a reasonable period, except where retention is required by law. Backups are deleted on their regular cycle. Infraction cases, timeline notes and audit entries are append-only within the product, and are removed as part of workspace deletion.
14. Deletion timeline
After a Workspace is closed, we delete or de-identify its data from the live database promptly, and from backups on the provider's regular cycle, which we expect to complete within 35 days. If the law requires us to keep certain data, we will isolate it and protect it until it can be deleted. Details are in the Data Retention and Deletion Policy.
15. Audits and information
On reasonable written request, no more than once a year, the Provider will provide information needed to demonstrate compliance with this DPA. Because the Service is in beta, the Provider does not currently hold third-party audit certifications, and says so on its Security page.
16. International transfers
The Provider and its subprocessors operate primarily in the United States. Where the law requires a transfer mechanism for personal information from another country, the parties will agree one in good faith before such a transfer occurs.
17. Customer responsibilities
The Customer is responsible for the lawfulness of the data it enters, for notices and consents owed to its staff, for the accuracy of its records, and for using only the access and roles it needs. See the Customer Data section of the Terms and the Acceptable Use Policy.
18. Liability and governing law
Each party's liability under this DPA is subject to the limits in the Terms. This DPA is governed by the laws of the State of Georgia, subject to any mandatory law that applies to the data.
19. Annex I: Details of processing
| Item | Description |
|---|---|
| Subject matter | Hosting and operation of the OnboardOps workforce records, training and discipline service |
| Duration | The term of the Customer's use of the Service, plus the deletion period above |
| Nature and purpose | Storing, retrieving, displaying, applying configured rules to, exporting, emailing and transmitting to configured webhooks the Customer's workforce records |
| Data subjects | The Customer's employees, contractors and other staff, and the Users it invites |
| Types of personal information | Name, work email, phone, emergency contact, staff ID, department, job role, hire date, status, shift availability, training and quiz results, infraction and disciplinary records, notes, typed-name acknowledgments, policy acknowledgments, incident reports, performance reviews and 1:1 notes, uploaded documents, checklist submissions, notifications, audit entries, login credentials (hashed), password-reset tokens (hashed) and session data |
| Sensitive data | None intended. Customers must not enter sensitive categories (see the Acceptable Use Policy). |
20. Annex II: Security measures
- Passwords stored only as bcrypt hashes; signed, HTTP-only session cookies.
- Server-side role-based access checks on every action; confidential notes removed server-side for non-manager roles.
- Workspace identifier on every record and every query to isolate customers.
- Append-only history for cases, timeline notes and audit entries, with hash-chained audit entries.
- HTTPS in transit; encryption at rest as provided by the database and hosting providers.
- Notifications exclude confidential manager notes.
- Uploaded files are served only through an authenticated route that checks the caller's role and the document's restriction, with no-store caching and sandboxing headers.
- Password-reset and invite tokens are single-use, time-limited and stored only as hashes. Changing a password signs out other sessions.
- Access to production systems limited to personnel who need it.
21. Annex III: Subprocessors
| Subprocessor | Service | Location |
|---|---|---|
| Vercel Inc. | Application hosting and delivery | United States and global edge network |
| Neon, Inc. | Managed Postgres database hosting | United States (region as configured) |
| Resend | Transactional email delivery | United States |