Subprocessors and service providers
AskAny relies on a small core service stack and invokes additional providers only when their feature is used. The current architecture routes AI models through OpenRouter and connected-app tools through Composio.
Selected model requests pass through OpenRouter to the downstream model provider.
Connected-account auth, tool discovery, and external app execution.
Data categories vary with the product feature and context you choose to use.
Last reviewed: 10 September 2026
Core service providers
The table describes data that may be involved when the relevant service is used. It does not mean every category is sent on every request.
| Provider | Purpose | Data categories | Notes |
|---|---|---|---|
Google Cloud Platform (Google LLC) Hosting & storage | Host AskAny services and durable application storage. | Account data, retained chats, uploaded files, generated media, and technical service data. | Processing can occur in supported service regions under applicable contractual safeguards. |
OpenRouter, Inc. AI model routing | Route model and generation requests to the model/provider selected for the request and return usage/cost metadata. | Prompts, selected conversation context, files/media supplied for the request, model parameters, outputs, request/usage metadata. | OpenRouter then transmits inputs to the selected downstream model provider. OpenRouter states it does not use Inputs or Outputs for model training; downstream provider practices can differ. |
Sampark Inc. (Composio) Connected-app platform | Connected-account authentication, toolkit/tool discovery, credential lifecycle, and execution of user-requested external app actions. | Connection/account identifiers, authorization credentials handled by Composio, tool arguments, requested app data, action results, and related technical metadata. | Used only for connected-app features. The underlying app/service also receives the data or action necessary to fulfill the user’s request. |
Stripe Payments & subscriptions | Checkout, free-trial/subscription lifecycle, invoices, refunds, and fraud prevention. | Name, email, billing identifiers, subscription status, invoice data, and transaction metadata. AskAny does not store full card numbers. | AskAny subscription billing is separate from OpenRouter model usage. |
Brevo (Sendinblue) Transactional email | Deliver account, verification, billing, support, and service messages. | Recipient details, email content, delivery status, and technical email metadata. | Processing follows Brevo’s service terms and contractual safeguards. |
Google Analytics 4 (Google LLC) Optional website analytics | Understand public website usage and improve product/conversion pages. | Consent-based identifiers, page/event data, browser/device data, and IP-derived signals with IP anonymisation configured. | Loaded only when the required analytics consent has been given. |
Usercentrics Cookiebot Consent management | Record and apply website cookie preferences. | Consent choice, consent identifier, timestamp, domain, and browser/device data. | Consent records are retained as needed to remember and demonstrate the user’s choices. |
Google Fonts / public asset delivery Website assets | Deliver fonts and public-page resources. | IP address, user agent, request time, and requested asset information. | No AskAny chat content is intentionally sent for public asset delivery. |
OpenRouter routes to the model you select.
OpenAI, Anthropic, Google, xAI, Mistral and other model providers may receive selected request content when one of their models is chosen through OpenRouter. Because the OpenRouter catalog and routing options can change, this page does not pretend a static provider list is exhaustive.
Learn about model routingComposio connects to the app you authorize.
When you connect and invoke a supported service—such as Gmail, Slack, Notion, GitHub, Google Calendar or another available toolkit—Composio and the underlying service process the data required for that tool action. Those services can also apply their own account terms and privacy practices.
Learn about integrationsProvider updates
We update this page when a material service-provider change affects how customer data is processed. Model-provider and connected-app catalogs can change more frequently than the core subprocessors above; the selected service at the time of a request determines the relevant downstream terms.