Alchemize Scout — Subprocessors
Version: scout-subprocessors-2026-10-05-v1.2.1
Effective: October 10, 2026
Replaces: scout-subprocessors-2026-09-29-v1.2
Changelog: v1.2.1: internal infrastructure details (storage and load-balancer names) removed; vendors, purposes, and regions unchanged. v1.2: legal entity name corrected to Maxis Inc.; AI routing through OpenRouter and bring-your-own-key (BYOK) terms; AI usage overage pricing; source-system connection and profiling terms; sign-in and activity data retention.
Maxis Inc. uses the following subprocessors to operate Alchemize Scout at scout.alchemize.io. AI subprocessors may process Customer Data only to provide the Service to that Customer and may not train models on Customer Data.
| Subprocessor | Role | Region / location | Data typically processed |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Hosting, compute, load balancing, and object storage used to run the Service; Amazon Bedrock AI model hosting may be reached through OpenRouter | us-east-1 | Customer Data, uploads, account and application data |
| Neon, Inc. | Managed Postgres database | us-east-1 | Account, organization, metadata, analysis references |
| Clerk, Inc. | Authentication and identity | Clerk-hosted | Account identity (name, email, auth identifiers) |
| Stripe, Inc. | Payment processing | Stripe-hosted | Billing and subscription metadata (not full card numbers) |
| Resend, Inc. | Transactional email (notifications@scout.alchemize.io) | Resend-hosted | Account email addresses and notice content |
| OpenRouter, Inc. | AI inference routing (default AI path when Customer has not configured its own AI provider key). Routes requests only to zero-data-retention model endpoints, which may be hosted by the AI providers listed below | OpenRouter-hosted; upstream endpoints in provider regions | Portions of Customer Data and prompts needed for the feature. No training on Customer Data; prompt logging disabled; zero data retention |
| Microsoft Corporation (Azure) | AI model hosting reached through OpenRouter | Microsoft-hosted | Portions of Customer Data and prompts needed for the feature |
| Google LLC (Vertex AI) | AI model hosting reached through OpenRouter | Google-hosted | Portions of Customer Data and prompts needed for the feature |
| Anthropic, PBC | AI inference for certain AI features, directly or through OpenRouter | Anthropic-hosted | Portions of Customer Data and prompts needed for the feature |
| OpenAI, L.L.C. | AI inference for certain AI features, directly or through OpenRouter | OpenAI-hosted | Portions of Customer Data and prompts needed for the feature |
Notes
- Default AI path: unless Customer configures its own AI provider key, AI requests go to OpenRouter, which routes them only to zero-data-retention endpoints hosted by providers listed on this page. Only providers listed on this page process Customer Data on the default AI path.
- Customer-provided AI keys (BYOK): If Customer configures its own AI provider key (BYOK), AI requests go to Customer's chosen provider under Customer's agreement with that provider. That provider is not a Maxis subprocessor. Scout does not send that organization's AI requests to Maxis's AI subprocessors unless an organization administrator opts in to Maxis-provided AI fallback.
- Cloudflare may appear in connection with Clerk bot-protection / Turnstile; it is not used as Scout’s primary CDN (Scout's traffic is served from AWS in us-east-1).
Changes
Maxis will update this page when subprocessors change materially and, where required by the Data Processing Addendum, provide notice.
Contact: scout.alchemize.io contact form.
