Subprocessors

This page lists the third-party service providers (“subprocessors”) that AITECH INTEGRATION LLC (“Integer Demand”) uses to provide the Service. We require each subprocessor to commit to confidentiality, security, and data-protection obligations no less protective than those in our Data Processing Addendum.

We will give at least 30 days' advance notice of any new subprocessor for the core Service. To receive notifications, send your account email to privacy@integerdemand.com.

Core Service subprocessors

Used to operate the core Service for all customers.

In addition to the third-party subprocessors below, Integer Demand operates internal Data Master and Production/Logistics backends on the same hosting infrastructure (managed cloud platform + Neon). These are first-party services operated by AITECH INTEGRATION LLC, not third-party subprocessors, and are therefore not listed in the table.

Managed cloud platform

• Purpose: Application hosting and runtime
• Categories of data: All Customer Data and account data, in transit and at rest in compute environment
• Processing location: United States

Neon (Databricks-affiliated)

• Purpose: Managed PostgreSQL database for the primary application database
• Categories of data: All Customer Data and account data at rest
• Processing location: United States

Stripe, Inc.

• Purpose: Payment processing, subscription billing, invoicing
• Categories of data: Billing and contact information, subscription metadata
• Processing location: United States; global

OpenAI

• Purpose: AI-assisted features (LLM inference), accessed via a managed AI integration proxy
• Categories of data: Prompts and supporting content for AI features. Under OpenAI's published API data-usage policy, API inputs and outputs are not used to train OpenAI's general-purpose models by default, and Integer Demand has not opted in to any OpenAI data-sharing, fine-tuning, or feedback program.
• Processing location: United States

AgentMail

• Purpose: Inbound and automated handling of email sent to Integer Demand's @integerdemand.com addresses
• Categories of data: Email address, headers and message content of senders, including third-party correspondents who write to our inboxes
• Processing location: United States

SMTP email provider

• Purpose: Transactional and product emails (account, security, billing)
• Categories of data: Email address, message content
• Processing location: United States

Production-log service

• Purpose: Error and performance telemetry for the application
• Categories of data: Application diagnostic events, error stack traces, request metadata (no Customer Data)
• Processing location: United States

Customer-initiated integrations

Engaged only when you choose to enable the relevant connector. If you do not enable a connector, Integer Demand does not transmit your data to that provider.

Google Drive

• Purpose: File access if you connect Google Drive
• Categories of data: Files you share through the connector
• Processing location: Global

Shopify, WooCommerce

• Purpose: E-commerce data ingestion if you enable the connector
• Categories of data: Order, product, inventory data from your store
• Processing location: Global

BigQuery, Snowflake, Redshift, Databricks, ClickHouse

• Purpose: Data-warehouse ingestion if you enable the connector
• Categories of data: Data you choose to query through the connector
• Processing location: Per the warehouse you operate

MySQL, SQL Server

• Purpose: Operational database ingestion if you enable the connector
• Categories of data: Data you choose to query through the connector
• Processing location: Per the database you operate

Salesforce, HubSpot

• Purpose: CRM data ingestion if you enable the connector
• Categories of data: Data you choose to sync through the connector
• Processing location: Global

Airbyte, Fivetran, Zapier, Make

• Purpose: ETL / automation handoff if you enable the connector
• Categories of data: Data you choose to route through the connector
• Processing location: Global

PayPal

• Purpose: Alternative payment processing if enabled
• Categories of data: Billing metadata
• Processing location: Global

International transfers

Where transfers from the EEA, the United Kingdom or Switzerland are involved, we rely on the EU Standard Contractual Clauses, the UK IDTA / Addendum, and our subprocessors' Data Privacy Framework certifications where available. See our Privacy Policy and DPA for details.

Questions or objections

If you have questions about a subprocessor or wish to object to a new subprocessor on reasonable data-protection grounds during the 30-day notice window, contact privacy@integerdemand.com.