Consault Subprocessor and Third-Party Provider List
Last updated: 22 October 2026
Consault uses service providers to deliver parts of the Services and lets customers connect third-party services of their choice. The legal role of a provider depends on the feature, account and contract. A provider may be Consault's subprocessor for one use and a customer-directed independent provider for another.
This page should be read with the Consault Privacy Policy.
Consault-selected providers
The following providers are used in the current product.
| Provider | Service purpose | Data that may be processed | Role or note |
|---|---|---|---|
| Anthropic | Claude AI inference for paid-plan agents, the personal assistant's managed usage and supported personal-assistant overage | Prompts, chat content, code, files, tool results and related context | Consault subprocessor when a Consault-managed subscription or API account is used; user-directed provider when the customer connects its own account |
| OpenAI | ChatGPT/Codex inference for paid-plan agents and the personal assistant's managed usage, and OpenAI Realtime voice for calls with the assistant | Prompts, chat content, code, files, tool results, call audio, call transcripts and related context | Consault subprocessor when a Consault-managed subscription or API account is used; user-directed provider when the customer connects its own account |
| Google sign-in, Gemini live voice and meeting processing, memory-related AI processing and Veo video generation | Account identifiers, prompts, text, audio, transcripts, files, media inputs and generated output | Multiple Google services and terms may apply | |
| BytePlus ModelArk | Seedream image generation and Seedance video generation | Prompts, reference media, generated media and technical metadata | Media generation provider |
| Paystack | Payment authorisation, transaction processing, billing events and fraud controls for payments in naira | Name, email, billing metadata, card token/authorisation, masked card details, currency, amount and transaction status | Payment provider; Paystack may act as an independent controller for parts of payment processing |
| Stripe | Payment authorisation, transaction processing, saved payment methods, billing events and fraud controls for payments in US dollars | Name, email, billing metadata, payment method token, masked card details, currency, amount and transaction status | Payment provider; Stripe may act as an independent controller for parts of payment processing |
| Cloudflare | Object/media storage, delivery, network, bot protection (Turnstile) on sign-up, sign-in and public forms, and optional app analytics | Generated media, object metadata, IP address, device, browser and network signals, and app analytics where enabled | Storage, network and bot-protection provider |
| TechBeaver Cloud | Hosting Consault services, runners, files and the production data plane in Europe, and app hosting for the apps customers publish with Consault | Account data, Customer Content, code, files, credentials, app builds and runtime data, service logs and backups when enabled | Primary infrastructure and app hosting provider, hosted in Europe |
| Railway | Fallback app hosting: customers' published apps run on Consault's Railway account when TechBeaver Cloud isn't available | App builds, environment configuration, app runtime data, deployment logs and metrics | App hosting provider, used only as a fallback |
| PostgreSQL on TechBeaver Cloud | Primary application database | Account data, workspace records, messages, billing records, operational data and encrypted credentials | Self-managed database software on Consault's TechBeaver infrastructure, rather than a separate subprocessor |
| Resend | Authentication codes, service notices and transactional email | Name, email address, message content, delivery events and IP metadata | Email delivery provider |
| Grafana Labs | Monitoring: service metrics, logs, uptime and alerts | Identifiers, activity, device data, errors and limited Customer Content that appears in logs | Monitoring provider |
| Sentry | Error tracking and incident diagnosis | Error reports, stack traces, identifiers, device and browser data, and limited Customer Content that appears in errors | Error-tracking provider |
| Self-hosted Mem0-compatible service | Long-term assistant memory | Selected user facts, instructions, preferences and relevant conversation context | Runs on Consault-controlled infrastructure when enabled; underlying AI processing may still use Google Gemini as separately listed above |
Consault counts visits to its website and web app itself, without cookies and without identifying visitors (Privacy Policy, section 12). The counts are stored in Consault's PostgreSQL database on TechBeaver Cloud in Europe and are not sent to any analytics provider. The country of a visit comes from Cloudflare, which already carries Consault's traffic as listed above; no other data goes to Cloudflare for counting.
Consault's optional product analytics is internally built and stored in Consault's PostgreSQL database on TechBeaver Cloud in Europe. It does not add a separate analytics provider. Optional product analytics will remain off at launch until an appropriate user choice is available. If the provider or approach changes, this list and the Privacy Policy must be updated before production data is sent to the new provider.
Customer-directed and optional services
The customer may connect or instruct Consault to use providers such as the following. These providers process data under the customer's agreement, settings and instructions. They are not automatically used for every customer.
| Provider or category | Purpose | Data that may be sent |
|---|---|---|
| GitHub | Repository access, issues and software collaboration | Identity, repository content, commits, branches, issues and credentials/tokens |
| Atlassian Bitbucket, Jira and Confluence | Repository, ticket and documentation workflows | Identity, repositories, issues, pages, comments and credentials/tokens |
| Microsoft | Entra sign-in and Microsoft Teams meetings | Account identifiers, meeting details, participant information, audio and related connection data |
| Google Workspace and Google Meet | Sign-in and meetings | Account identifiers, meeting details, participant information, audio and related connection data |
| Zoom | Meeting participation | Meeting details, participant information, audio and related connection data |
| Meta/WhatsApp | Messages and notifications | Phone number, profile identifiers, message content, files and delivery data |
| Telegram | Messages and notifications | Telegram identifiers, message content, files and delivery data |
| Railway | App deployment and operations | Repository/build content, environment configuration, deployment logs, metrics and credentials |
| TechBeaver | App deployment and operations | Repository/build content, environment configuration, deployment logs, metrics and credentials |
| Vercel | App deployment and operations | Repository/build content, environment configuration, deployment logs, metrics and credentials |
| Render | App deployment and operations | Repository/build content, environment configuration, deployment logs, metrics and credentials |
| Customer-selected AI provider | AI inference through the customer's own subscription or account | Prompts, messages, files, code and tool context selected for the task |
| Customer's app, infrastructure and databases | App operations, support and administration | App-user data, operational records, logs, metrics and authorised actions |
Provider changes
We may add or replace providers as the Services evolve. We will update this page and provide notice of a new subprocessor where required by contract or law. Enterprise customers may request a data processing agreement that describes the applicable notice and objection process.
Questions about providers or transfers can be sent to [email protected].