Data Processing & Privacy FAQ
What data does LaborIQ collect and use?
See below for the main categories of data we collect.
| Category | Examples | Source |
| Account & login | Name, work email, role, login credentials, SSO | Provided at signup |
| Billing | Billing contact, payment method, invoicing history | Provided by Client |
| Support | Correspondence and logs from support requests | Provided by Client/User |
| Usage data | Feature usage, device/browser type, IP address | Collected automatically |
| Client data | Employee records (hire date, compensation), files | Provided by Client |
What are client data responsibilities?
You (the Client), not LaborIQ, have sole responsibility for the accuracy, quality, integrity, legality, reliability, appropriateness and intellectual property ownership (or right to use) of all data entered into the LaborIQ platform.
How does LaborIQ store employee data?
Where applicable, LaborIQ stores employee data, including personally identifiable information (PII) (e.g., name and address), only within client account reporting views. This PII data is stored for client use and analysis only.
Does LaborIQ support third-party integrations?
You may authorize other HR or payroll systems (for example, through Finch) to connect with LaborIQ and sync employee data in for pay analysis – you’re responsible for making sure you have a lawful basis to authorize that connection. This is a one-way sync that you set up and control.
What specific employee data fields are required for employee management and related LaborIQ features/products (Pay Band Manager™, Pay Analysis™, and Employee Management)?
Necessary Fields: Employee First and Last Name (or other unique identifier), Job Title, Salary, Metro Area, and Department will be the fields used to analyze team pay.
Can I edit data in my payroll system using LaborIQ integrations?
No. LaborIQ’s payroll integrations provide a one-direction sync from the client’s payroll provider to LaborIQ for pay analysis and compensation management purposes only.
How does LaborIQ use AI and LLMs?
LaborIQ’s AI features include things like data search, category matching, job-title mapping, and interactive agent support. We do not use generative AI or LLMs to produce salary recommendations – those come from our own proprietary algorithm, built on employment and economic data across U.S. metro areas.
Where we do use AI, it runs on secured, private infrastructure, and we never use your data to train shared or generalized AI models. AI-assisted outputs are meant to support, not replace, human judgment, so please review them before relying on them.
If you choose to connect your own LLM (for example, Anthropic or OpenAI) through our MCP integration, that connection – and any resulting data access – is something you set up and control.
What are the data security and privacy standards LaborIQ follows?
LaborIQ follows data security and privacy practices in accordance with SOC2 and SOC3.
How is the data protected?
All data is encrypted in transit and at rest.
Where is data hosted (cloud provider and geographic region)?
All data is privately hosted through Amazon Web Services (AWS) in US-East 1 and 2.
What are LaborIQ’s data retention and deletion practices?
We retain Client Data while your account is active. After your term ends, we retain your data for a limited period to support reactivation. Please see Terms of Service and Privacy Policy for more information about LaborIQ data usage policies and procedures.
Does LaborIQ maintain a list of subprocessors (or can you share the subprocessors used to support the platform)?
| Subprocessor | Service Category | Location |
| Direct Subprocessors | ||
| Ably® | Publish/Subscribe Messaging | United Kingdom |
| Amazon Web Services (AWS®) | Cloud Infrastructure | United States |
| Chargebee® | Billing & Revenue | United States |
| Finch® | HR & Payroll Integration | United States |
| Mixpanel® | Product Analytics | United States |
| Salesforce® | CRM | United States |
| Twilio Authy® | Identity & Security | United States |
| Typesense® | Search Infrastructure | United States |
| UserGuiding® | Digital Adoption | United States |
| Indirect Subprocessors | ||
| Hubspot®* | Email & Marketing Automation | United States |
| Quickbooks®** | Accounting & Finance | United States |
| Stripe®** | Payment Processing | United States |
| Last Updated: March 12, 2026 | ||
| * Indirect subprocessor through Salesforce CRM. | ||
| ** Indirect subprocessors through Chargebee billing and revenue management. | ||
Disclaimer: This document is provided for informational purposes to summarize our data practices. It creates no rights or obligations beyond those in our Terms of Service and Privacy Policy. If any text in this Statement is inconsistent with those documents, the Terms of Service and Privacy Policy control.