Subprocessors

Maxis Technology Inc. uses the following subprocessors to operate Alchemize Scout at scout.alchemize.io. AI subprocessors are authorized to process Customer Data only to provide the Service to that Customer and may not train models on Customer Data.

Subprocessors

Subprocessor	Role	Region / location	Data typically processed
Amazon Web Services, Inc. (AWS)	Hosting and compute (ECS Fargate), load balancing (Application Load Balancer), object storage (S3 bucket `alchemize-scout-uploads`), related AWS control-plane services used to run the Service	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
Anthropic, PBC	AI inference (classification / AI scan features)	Anthropic-hosted	Portions of Customer Data and prompts needed for the feature
OpenAI, L.L.C.	AI inference (in-product AI chat and related features)	OpenAI-hosted	Portions of Customer Data and prompts needed for the feature

Notes

Soft-launch AI code paths use Anthropic and OpenAI only (no Google / xAI defaults).
Clerk on soft-launch may still be on a development instance until the production Clerk cutover; Clerk remains a subprocessor either way.
Cloudflare may appear in connection with Clerk bot-protection / Turnstile; it is not used as Scout's primary CDN (live traffic is served via ALB in us-east-1).

Changes

Maxis will update this page when subprocessors change materially and, where required by the Data Processing Addendum, provide notice.

Questions: use the contact form on scout.alchemize.io.