What typically leaves your organisation's Aptiro workspace, and what stays inside it. This describes the shipped product behaviour verified in code and Terraform. Legal wording for international transfers is to confirm with Aptiro. Providers below are named by role; a named list is available on request under NDA.
Stays in your organisation's Aptiro data
Unless a feature below sends it out, the following live in Aptiro's database and object storage for your organisation only:
- Accounts, contacts, deals, pipeline, activities, tasks, sequences, comments
- Custom fields and field-group visibility rules
- ICP, scores, briefs and trigger records Aptiro has already written back
- Attachments on accounts and deals (private bucket, org-scoped access)
- Roles, membership and settings rows for your organisation
- Audit log rows (on entitled plans), without request bodies or secrets
- Secret references only; the secret values sit in the secret store under your organisation's prefix
Hidden field groups are enforced in the scoped database client, so a member who cannot see a field does not receive it from the API.
Leaves the organisation (to a processor or connected system)
| Flow | What goes out | Destination |
|---|---|---|
| Sign-in | Email / Google profile used for authentication | Our cloud hosting provider's identity service (and Google, if Google sign-in) |
| Billing | Customer and subscription data needed to charge | A payment processor |
| AI features | Prompt content for scan extraction and scoring; meeting prep (contact names and roles, deals, recent activities, meeting titles); brief wording; company discovery; website ICP inference; CRM stage-map suggestions | An AI model provider (when configured) |
| Web search | Signal-scan queries, customer website addresses, and market-news queries | A web search provider (when configured) |
| YouTube source | Channel id / public video metadata requests | The video platform API |
| UK company register | Company number or search term; reads officers and persons with significant control | The UK company register API |
| Trade statistics | Company names used in published trade lookups | An open government trade statistics service |
| Find people (provider) | Website / company lookup parameters | The customer's own people-data provider |
| Mail sync | OAuth to the member's mailbox; mail metadata Aptiro stores after sync | |
| Calendar sync | OAuth; event create/update/list for the member's calendar | Google Calendar |
| Messaging notifications | Message content Aptiro posts | The customer's connected messaging workspace |
| Platform email | Invite and similar messages Aptiro sends | An email delivery provider (or the organisation's SMTP, if set) |
| Webhook trigger source | Account id, name, website, shared custom fields | Customer's HTTPS endpoint |
| AI assistant | Queries and answers for the signed-in member | The connected assistant over Aptiro's connector |
| In-app feedback | Text the member types | Our code hosting and issue tracking provider |
| Browser telemetry | Scrubbed errors, vitals and route patterns; org id and a hash of the user id (not email or name) | Self-hosted collectors on Aptiro infrastructure |
| Operational traces | Route patterns, status codes, timings and outcomes from the API and the AI assistant connector; org id, the internal user id and role (not email or name) | Self-hosted collectors, and a hosted observability provider in the EU |
| Connected CRM | Configured CRM objects | The customer's CRM of record |
Exports a member downloads (reports, subject-access JSON, audit export) leave through that member's browser. They are not sent to a third party by Aptiro unless the member forwards them.
Model providers and training
Aptiro's scan, prep, brief and assistant paths send the prompts and tools those features need. They do not offer a bulk "upload my whole org to the model" export. Provider retention and training policies are the provider's; contractual wording is to confirm with Aptiro.
What staff can see
Aptiro staff use a separate admin app. Support actions that change credits are mirrored onto the customer audit log as Aptiro support. Staff do not use the customer's sign-in pool. Operational access to production infrastructure follows Aptiro's cloud and CI roles, not a shared customer password.