Processors and service providers that can receive customer or end-user data when Aptiro runs as configured in this repository. Verified against infrastructure as code, platform secret names and backend dependencies. Providers are described by role here. A named list is available on request under NDA. Contractual sub-processor schedules and transfer wording are to confirm with Aptiro.
Customer-chosen integrations (the customer pastes their own API key or connects their own OAuth app) are listed separately: Aptiro sends only what that feature needs, under the customer's own relationship with that vendor.
Platform services (Aptiro-operated)
| Provider (by role) | What it receives | When |
|---|---|---|
| Our cloud hosting provider, in the EU | Application data in the database, object storage (attachments, exports), infrastructure logs and metrics, sign-in identity attributes, and secret values Aptiro stores for organisations | Always, for hosted Aptiro |
| A payment processor | Billing identity, plan and seat quantities, payment method handling on the processor's side, credit top-up checkout metadata Aptiro sends | When the organisation uses Aptiro billing |
| An AI model provider | Prompt content for the features that call a model: account and signal text for scan extraction and scoring; meeting-prep facts (contact names and roles, deals, recent activities, meeting titles); brief wording; company discovery; inferring an ideal-customer profile from a company's own website pages; suggesting how connected CRM pipeline stages map to Aptiro stages | When those features run and a model key is configured on the platform |
| A web search provider | Search queries for buying-signal scans, customer website addresses, and market-news queries derived from account identity | When web search-backed scanning is configured |
| A video platform API | Channel identifiers and public video metadata for the YouTube trigger source | When that source is on and a platform key is configured |
| The UK company register API | Company numbers and search terms Aptiro sends to look up UK companies, officers and persons with significant control | When registry features run and a registry API key is configured |
| An open government trade statistics service | Company names used to look up published trade figures | When trade-statistics trigger sources run |
| An email delivery provider | Email addresses and message content for mail Aptiro itself sends (for example invites), when the platform sender is used | When platform email is sent that way |
| A workplace messaging provider | Channel posts and OAuth tokens when an organisation connects messaging; Aptiro's app credentials are platform-side | When the organisation connects messaging and Aptiro posts |
| Our code hosting and issue tracking provider | Feedback text a member types and sends from the in-app feedback control | When the feedback feature is enabled and someone sends feedback |
| A hosted observability provider, in the EU | Operational traces from the API and the AI assistant connector: route patterns, status codes, timings and outcomes, with the organisation id, the internal user id and role. No email or name | Always, for hosted Aptiro |
Browser telemetry and backend metrics are collected on self-hosted Aptiro infrastructure, so they are not listed as a third-party sub-processor. Operational traces also go to the hosted observability provider above. See security overview.
Google sign-in (where enabled) and Google APIs for Calendar and Gmail, when members connect those features, receive the OAuth and mailbox or calendar data those features need. Sign-in profile data follows the managed identity service and Google; calendar and mail sync use the member's own connection.
Customer-connected providers (customer's own account)
| Provider (by role) | What it receives | When |
|---|---|---|
| The customer's people-data provider | Lookups Aptiro makes with the customer's API key (company website and related search parameters) | When the organisation saves a provider key and a member runs Find people |
| The customer's CRM of record | Objects and fields the CRM integration is configured to sync | When that CRM is connected |
| Customer SMTP | Invite and notification mail the organisation sends through its own SMTP | When the organisation configures SMTP |
| Customer webhook endpoints | Account id, name, website and shared custom fields Aptiro posts during a scan; the endpoint's response documents | When a webhook trigger source is enabled |
| Connected AI assistants | Whatever the signed-in member asks the assistant to read or, if write-back is enabled, activities it logs | When an AI assistant is connected; scoped to that member's permissions |
Not third-party sub-processors
- Aptiro staff admin tools run in Aptiro's own cloud account with a separate identity pool; they are Aptiro operators, not a third-party sub-processor.
Changes
This list tracks what the codebase and Terraform wire up today. A buyer that needs contractual notice of changes should take that in the data-processing agreement (to confirm with Aptiro), not from this page alone.