Subprocessors
Last updated: July 8, 2026
Magu Studios, Inc ("AgentMark") uses the third-party subprocessors listed on this page to deliver the AgentMark service. A subprocessor is a third party we engage that may process customer data on our behalf. This page is the authoritative, current list; our Privacy Policy describes how we handle personal data more broadly.
We update this page before a new subprocessor begins processing customer data, and we record every change in the change log below. To be notified when this list changes, email hello@agentmark.co with the subject "Subscribe to subprocessor updates".
Infrastructure and data hosting
These subprocessors host or transport the data you send to AgentMark.
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Cloudflare, Inc. | API gateway and edge network. Terminates TLS and routes and buffers telemetry ingestion (Workers, Queues, R2). | All API traffic; trace payloads in transit and during ingestion buffering | Global edge network (US company) |
| Supabase, Inc. | Application database and authentication. | Account data (name, email, credentials), organization and app metadata, prompts, datasets, encrypted environment variables | United States |
| ClickHouse, Inc. | Analytics data store for telemetry (ClickHouse Cloud). | Traces, spans, scores, and usage events | United States (GCP us-central1) |
| Vercel, Inc. | Dashboard and website hosting. | Dashboard traffic and request logs | United States |
| Fly.io (Fly Machines) | Runtime for managed code deployments. | Deployed handler code, build artifacts, runtime environment variables | United States |
AI processing
These providers power specific AI features of the service. We do not use your data to train AI models, and we use these providers through commercial API terms that prohibit them from training their models on your data.
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Google LLC (Gemini API) | Automated topic clustering and summarization of traces (the Topics feature). | Trace content processed for topic classification and naming | United States |
| Anthropic, PBC | Internal platform incident diagnosis (alerting agent). | Diagnostic context for platform incidents, which may include trace metadata | United States |
Business operations
These subprocessors support billing, communication, and reliability of the service.
| Subprocessor | Purpose | Data involved | Location |
|---|---|---|---|
| Stripe, Inc. | Payment processing and billing. | Billing contact and payment details | United States |
| Resend, Inc. | Transactional email delivery. | Recipient name, email address, notification content | United States |
| PostHog, Inc. | Product analytics for the dashboard. | Product usage events, account identifiers (name, email), organization association | United States |
| Better Stack, Inc. | Logging, uptime monitoring, and alerting. | Application logs, error reports, request metadata | United States |
| Functional Software, Inc. (Sentry) | Error tracking for the API gateway. | Error reports and stack traces with request metadata | United States |
Customer-configured integrations
Integrations you choose to connect (GitHub, GitLab, Slack, or your SAML identity provider) receive data only after you configure them, under your own agreements with those providers. They are not subprocessors, and disconnecting them stops the data flow.
Change log
| Date | Change |
|---|---|
| July 8, 2026 | Initial publication. |
Questions
If you have questions about a subprocessor, or your agreement with us requires advance notice of subprocessor changes, contact hello@agentmark.co.