Back to home

Last updated September 7, 2026

Service providers and subprocessors

These companies help AgentMarkit run the site, host agents, process payments, send service email, and provide optional connections.

Core service providers

Cloudflare

What it does: Website delivery, security, serverless request processing, key-value and database storage, and operational logging.

Information involved: Account and setup records, contact-form records, request and security data, limited machine metadata, and messages while they are routed between the web chat and the user's agent.

Cloudflare privacy policy

Agent37

What it does: Provisions and hosts the cloud machine where a hosted Hermes agent runs, maintains infrastructure, and provides encrypted machine backups.

Information involved: Machine identifiers and configuration, agent workspace files, prompts, outputs, memory, installed credentials, connected-service data, and infrastructure logs.

Agent37 privacy policy

Stripe

What it does: Checkout, payment processing, subscriptions, fraud prevention, and billing records.

Information involved: Billing contact details, payment method, purchase, customer and subscription identifiers, and payment status. AgentMarkit does not receive the full card number.

Stripe privacy policy

Resend

What it does: Transactional email, including magic sign-in links and service notices.

Information involved: Recipient email address and service-message content.

Resend privacy policy

Optional connections

Composio

What it does: Manages the Google OAuth connection and routes the two approved Gmail metadata tools when a test user chooses that feature.

Information involved: Google OAuth tokens, a pseudonymous user and session identifier, connection records, tool requests, and filtered Gmail metadata while the request is performed. Composio may retain connection or execution records under its service settings and privacy policy.

Composio privacy policy

Model providers chosen by the user

What they do: Generate the agent's responses.

Information involved: Prompts, relevant agent context, and tool results sent to the chosen model. The provider and configuration may differ by user. We identify the model choice during setup. Optional Google data may be sent only to provide the personalized feature the user requested and may not be used for generalized or non-personalized model training.

Other integrations chosen by the user

What they do: Perform the connection or action the user selects, such as calendar, chat, task, or document functions.

Information involved: Credentials, requests, and results needed for that integration. We identify additional providers and requested access before a connection is enabled.

Provider changes

AgentMarkit may add, replace, or remove providers as the service changes. We will update this page before a new provider begins handling personal information for a materially different purpose. Where required, we will give additional notice.

Questions about a provider or data location can be sent through the privacy contact form.