Sub-Processors
Updated October 10, 2025
This Intempt Sub-Processors Page is incorporated into the Intempt Data Processing Addendum ("DPA") and the Agreement. This page explains how Intempt engages Sub-Processors to process Customer Data in connection with the Intempt services (the "Services").
Contents
- Infrastructure Sub-Processors
- Feature-Specific Sub-Processors
- Intempt Affiliate Sub-Processors
- Updates to Sub-Processor Page
- Questions / Contact
1. INFRASTRUCTURE SUB-PROCESSORS
To help Intempt deliver the Services, we engage Sub-Processors to support our infrastructure. By agreeing to the DPA, you agree these Sub-Processors may process Customer Data to the extent necessary to provide their services.
Current hosting / data center region: United States (Intempt currently operates US-only data residency.)
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| Amazon Web Services, Inc. | Hosting & infrastructure | Core Intempt platform hosting (compute, storage, networking), including Amazon S3 (file storage/uploads) and other AWS infrastructure services used by Intempt |
Notes
Vault (secrets management): Intempt uses Vault for secrets management. If Vault is self-hosted by Intempt on AWS, it is not a separate Sub-Processor (AWS remains the infrastructure Sub-Processor). If Intempt later uses HashiCorp-managed Vault/HCP, HashiCorp would be added here.
No Cloudflare: Intempt does not use Cloudflare as a Sub-Processor at this time.
2. FEATURE-SPECIFIC SUB-PROCESSORS
Some features and integrations require additional Sub-Processors. Some Sub-Processors apply by default, and some apply only if and when you enable a feature or install an integration. In either case, you may choose not to use the applicable feature or integration.
Where feasible, Intempt will inform you before you enable a feature or integration that requires an opt-in Sub-Processor (e.g., via UI, docs, or implementation guidance).
A) Messaging, communications, and telephony
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| SendGrid, Inc. | Email delivery | Email sending (campaign and/or transactional delivery) |
| Twilio Inc. | SMS / messaging / telephony | SMS delivery; telephony and call recording (if enabled) |
| Google LLC | Push notifications (FCM) | Android push notifications via Firebase Cloud Messaging (FCM) |
| Apple Inc. | Push notifications (APNs) | iOS push notifications via Apple Push Notification service (APNs) |
B) Customer support & communications
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| Intercom, Inc. | Customer support / chat | Support communications and customer messaging (if you contact Intempt support or use Intercom-powered support features) |
C) Payments / billing
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| Stripe, Inc. | Payment processing and billing | Processing subscription payments and billing-related data (e.g., billing contact information and payment metadata) |
D) AI / ML (feature-driven)
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| OpenAI, L.L.C. | AI service provider | AI/LLM features (including embeddings), when enabled/used |
| Anthropic, PBC | AI service provider | AI/LLM features, when enabled/used |
E) Meeting bot / note-taking (feature-driven)
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| Recall.ai | Meeting bot note-taking and storage | Call/meeting note-taking features and related storage (if enabled/used) |
F) Integrations (opt-in)
If you enable the following integrations, the relevant third parties may process Customer Data as part of providing that integration:
| Sub-Processor | Purpose | Applicable Service |
|---|---|---|
| HubSpot, Inc. | CRM / marketing automation integration | HubSpot integration (syncing and workflows, as configured) |
| Shopify Inc. | eCommerce platform integration | Shopify integration (catalog/customer/event sync, as configured) |
| Slack Technologies, LLC (a Salesforce company) | Team messaging integration | Slack integration (notifications and workflow actions, as configured) |
| Twilio Segment (Segment.io, Inc.) | Customer data platform integration | Segment integration (event/user forwarding and ingestion, as configured) |
| Webhook endpoints you configure | Customer-chosen recipients | Webhook integrations (data sent to endpoints you provide and control) |
Important: For webhooks, Intempt acts on your instructions to deliver data to destinations you configure. Those destinations are not "Intempt Sub-Processors" (they are typically your vendors or systems).
3. INTEMPT AFFILIATE SUB-PROCESSORS
At this time, Intempt does not use affiliate entities as Sub-Processors for processing Customer Data.
4. UPDATES TO SUB-PROCESSOR PAGE
Due to the nature of our business and our ongoing efforts to improve the Services, our Sub-Processors may change from time to time. For example, we may replace a Sub-Processor to consolidate and minimize our vendor footprint, or we may add a Sub-Processor if doing so enhances our ability to deliver the Services.
Where required under the DPA, Intempt will provide advance notice of new or replacement Sub-Processors and permit Customer to object on reasonable grounds, as described in the DPA (typically at least 30 days in advance, except where a shorter timeline is necessary for urgent security or operational reasons).
5. QUESTIONS / CONTACT
Questions about this page or Intempt's privacy practices: hey@intempt.com