Subprocessor Schedule to the IntraQ Data Processing Addendum
Version: 1.0 Effective date: August 26, 2026 Last updated: August 26, 2026
1. What this Schedule is
This Schedule identifies IntraQ’s current Subprocessors under Section 13 of the Data Processing Addendum (the “DPA”), the function each performs, and the categories of data each may process. It lists only the third parties that process Personal Information contained in Customer Content on IntraQ’s behalf. It also sets out how IntraQ adds or changes Subprocessors and how Customer may object.
2. Current Subprocessors (IntraQ-engaged)
| Subprocessor | Function | Location | Data it may process |
|---|---|---|---|
| Anthropic, PBC | Generative AI — text generation for answers, drafts, and recommendations | United States (default global API endpoints) | Prompt content: user questions, retrieved portions of Customer documents and policies, document titles, organization name, and recent conversation context (unmasked) |
| OpenAI, L.L.C. | Generative AI — text generation; and embeddings for search indexing | United States (default global API endpoints) | Same prompt content as above; and, for embeddings, Customer document content on ingestion and search-query text |
| Amazon Web Services, Inc. | Object storage for uploaded and generated document files and profile photos | United States (US East (Ohio), us-east-2) | Uploaded and generated document files and profile photos (encrypted at rest) |
| MongoDB, Inc. | Primary database for structured records (MongoDB Atlas) | United States (AWS N. Virginia, us-east-1) | All structured records described in the Privacy Policy |
| Upstash, Inc. | Queue job references and session state | United States (AWS us-east-1) | Background-job references (such as document, tenant, and action identifiers) and session data; not document or customer-content payloads |
| Plus Five Five, Inc. (Resend) | Transactional email delivery | United States | Recipient email address and name, and the contents of transactional messages |
| Stripe, Inc. | Payment processing and billing | United States | Plan, subscription, and seat metadata and Stripe identifiers (card data is provided directly to Stripe and does not reach IntraQ) |
| Railway Corp. | Application compute | United States (US East, Virginia) | Request traffic to the Service, which may contain Personal Information |
| Vercel Inc. | Frontend and edge delivery | United States (Washington, D.C., iad1) | Request traffic to the Service, which may contain Personal Information |
Certain of the infrastructure providers above manage their own backup, replication, and object-version retention; IntraQ does not represent that every backup or historical copy resides exclusively in the United States.
3. AI providers — contractual basis and important limitations
- IntraQ engages Anthropic under Anthropic’s commercial/API terms, which incorporate Anthropic’s data processing terms and provide that Anthropic does not train its models on content submitted through the API and is subject to confidentiality obligations.
- IntraQ engages OpenAI under OpenAI’s services/API terms, which incorporate OpenAI’s data processing terms and provide that OpenAI does not use content submitted through the API to develop or improve its services unless the customer expressly agrees.
- Content transmitted to these providers is not masked, anonymized, or de-identified by IntraQ first.
- IntraQ does not represent that either provider operates on a zero-data-retention basis.
Anthropic and OpenAI are the only generative-AI providers in the production Service. Google’s generative-AI models are not used by the Service.
4. Services the customer connects and directs (not IntraQ Subprocessors)
The following are engaged only when Customer chooses to connect them and are governed by those providers’ own terms. Customer directs the data flow; IntraQ accesses them on a read-only basis to retrieve the content Customer authorizes.
- HR systems: BambooHR, Dayforce, UKG, Deel (read-only workforce sync).
- Document sources: Google Drive, Microsoft OneDrive/SharePoint (read-only document retrieval).
- Communication tools: Slack, Microsoft Teams (read-only retrieval).
- Identity providers: Google and Microsoft (sign-in / SAML).
IntraQ classifies these as customer-directed integrations rather than Subprocessors because Customer selects and authorizes them and IntraQ does not engage them to process Customer Content on IntraQ’s own behalf. Google’s role as a sign-in and document-source integration is evaluated on that basis and is separate from Google’s generative-AI models, which are not part of the production Service.
5. Adding or changing a Subprocessor
- IntraQ maintains this Schedule as the current list of Subprocessors and will keep it up to date.
- Before a new Subprocessor begins processing Personal Information contained in Customer Content, IntraQ will provide at least thirty (30) days’ advance notice by updating this Schedule and notifying Customer through the mechanism Customer has elected (email to the Customer’s designated contact and/or an in-product or subscription notice).
- Customer may object to a new Subprocessor on reasonable data-protection grounds within thirty (30) days of that notice. The parties will work in good faith to resolve the objection; if they cannot, Customer may, as its exclusive remedy, terminate the affected portion of the Service and receive a prorated refund of prepaid fees for the terminated portion.
- IntraQ will engage each new Subprocessor under a written contract meeting Section 13 of the DPA.
6. How to receive updates and raise objections
To designate a contact for Subprocessor notices, to request the current Subprocessor list, or to raise an objection, email privacy@intraqai.com.