Legal / Subprocessors

Subprocessors

Who touches data, for what, and where, for the product and for this website.

Last updated: Applies to aaes.ai

Product subprocessors

Website operator: AAES LLC, a Delaware limited liability company. Registered address for legal notices: 8 The Green STE B, Dover, DE 19901, United States.

AAES Govern: none for ordinary client-operated runtime traffic. In a client-operated deployment, AAES Govern runs in the client's own environment (a single VM with Docker Compose, Kubernetes, or an air-gapped deployment), and AAES does not receive its runtime traffic. Authorized support transfers are described separately below. The client-hosted AAES Govern runtime makes no telemetry call or online license check, and its outbound calls go to endpoints the client registers.

Software dependencies in the AAES Govern runtime

The AAES Govern daemon builds for Linux, macOS and Windows link these third-party Go modules (checked with go list -deps on November 4, 2026): the AWS SDK for Go v2 and smithy-go for AWS KMS key custody; the pgx PostgreSQL driver with pgpassfile, pgservicefile, puddle and golang.org/x/sync; the go-sql-driver/mysql driver with filippo.io/edwards25519; the microsoft/go-mssqldb driver with golang-sql/civil, golang-sql/sqlexp, google/uuid, shopspring/decimal, golang.org/x/crypto and golang.org/x/net; golang.org/x/image for console appearance images; and golang.org/x/text. Windows builds also use golang.org/x/sys for platform file locking. These are software dependencies, not hosted subprocessors.

Client-configured integrations can still transmit data outside that environment. Agents created in AAES Operate send instructions, conversations, tool definitions and tool results to the client's selected model endpoint. If an operator turns on Cursor, GitHub Copilot or Meta's Muse agent in standalone Operate, those agents send task content to their own vendor (for GitHub Copilot, GitHub) under that vendor's terms. The model provider's role and terms depend on the client's arrangement; it is not an AAES-engaged runtime subprocessor merely because the client configures that endpoint.

The client must assess the provider's processing, retention, locations and transfer arrangements.

AAES Operate keeps instructions and run transcripts on encrypted volumes, separately from the governance journal, as described in the privacy policy.

AAES Operate. In a client-operated deployment, AAES Operate also runs in the client's own environment. It sends instructions, task context, and tool results to the model providers and agent runtimes the client configures; their role and terms depend on the client's arrangement, and the client must assess them. AAES Operate is built on open-source components. The outbound connections AAES Operate makes, including any made by those components, are listed in the evaluation package; verify them before production use. The AAES Govern runtime statements above do not describe AAES Operate.

Optional support may involve a client-authorized, one-off transfer of diagnostic material (logs, screenshots, attachments), agreed in writing before anything is sent, as described in the privacy policy.

The runtime statement above does not cover support transfers: if diagnostic material contains personal data and arrives through a provider listed in section 3 (for example the mailbox host), that provider processes it on our behalf for that engagement under its own processor terms.

AAES Infer provider requirements

Infer is a separate model-access service; public access is not open. The absence of subprocessors for ordinary client-operated Govern traffic does not apply to Infer.

Before an offer accepts customer data, its provider schedule must name the inference provider, hosting and storage providers, authorized subprocessors, processing locations and purposes. It must also state retention, support access, transfer arrangements and the applicable processing terms. No qualified supplier list or live location is established by the nine jurisdictions on the Infer product page.

The prepaid implementation uses Stripe Checkout for company funding. Stripe processes payment details on its checkout page; AAES uses payment references, amounts and status for reconciliation. Stripe may act as a controller or processor depending on the activity, as described in its privacy policy. The payment arrangement and its locations must be disclosed before funding is enabled; a selected inference jurisdiction does not restrict Stripe processing to that location.

Offer-specific providers and notices must be supplied before activation. We do not present planned suppliers as engaged subprocessors. Read the Infer data categories and disclosure requirements.

Website, correspondence and business development providers

These providers support the aaes.ai website, business correspondence and business development. They do not receive ordinary client-operated runtime traffic. If a client authorizes sending diagnostic material through one of them, that provider may also process client data for the support engagement; permitted recipients and applicable processing terms must be agreed before that transfer.

ProviderRoleLocation of processingTransfer safeguards
RenderWebsite hosting and the contact-form endpointGlobal CDN for static-site delivery, which reaches visitors through Cloudflare, one of Render’s listed subprocessors; Singapore for the configured contact-form API. Render is a US-based company. Render regionsEU-U.S. Data Privacy Framework (incl. UK Extension and Swiss-U.S. DPF); Render's DPA incorporates the EU SCCs and UK Addendum. Render DPA
ResendContact-form email delivery, when configuredUnited States (primary processing and storage)EU-U.S. Data Privacy Framework and UK Extension; pre-signed DPA with EU SCCs (Module Two, or Module Three where we act as processor), UK Addendum and Swiss modifications. Resend GDPR overview
PrivateEmail (Namecheap)Mailbox hosting and outbound email for aaes.ai addresses, including hello@aaes.aiPhoenix, Arizona, United States, per Namecheap’s published Private Email locationProcessed under Namecheap's Universal Terms of Service and Privacy Policy; we have not verified a separate transfer mechanism and state none. Namecheap privacy policy
Cal.comDemo and assessment booking and scheduling; creates the Zoom link, the calendar entry and, through its HubSpot integration, the CRM meeting recordUnited States, per Cal.com's privacy policy; some of its subprocessors process data elsewhereEU-U.S. Data Privacy Framework and UK Extension; EU SCCs, UK Addendum and Swiss amendments where the framework does not apply (Cal.com states the Swiss-U.S. framework does not currently apply). Cal.com DPA
ZoomDemo and assessment video calls and, when used and not objected to, Zoom's AI meeting summaryUnited States and other countries, per Zoom's privacy statementEU-U.S. Data Privacy Framework; European Commission Standard Contractual Clauses for EEA, Swiss and UK transfers.
HubSpotContact-form inquiry records, CRM and relevant follow-up, when configuredCanada selected for primary account data hosting; other processing and subprocessor locations are described in HubSpot's subprocessor list. Primary hosting does not restrict every operation to Canada.HubSpot's Data Processing Agreement documents its processing and applicable international transfer safeguards. We do not claim that a regional hosting selection alone establishes a safeguard for every transfer.
WorkOSSign-in for the internal demo environment at demo.aaes.ai and the related webhook events; only aaes.ai accounts get into the demo, but WorkOS may receive sign-in details from anyone who attempts the sign-inUnited States, per WorkOS's data processing addendum; its subprocessors are listed on the WorkOS trust centerWorkOS's DPA incorporates the EU SCCs (Modules Two and Three), the UK Addendum and Swiss amendments. WorkOS DPA
Better StackUptime monitoring of the website and our public status pageUnited States, per Better Stack's data processing agreement; some of its subprocessors process data in Europe or globallyStandard Contractual Clauses; Better Stack's DPA also cites the EU-U.S. Data Privacy Framework. Better Stack DPA

A provider's certification does not by itself establish coverage for every transfer. The transfer arrangements for correspondence are described in full in the privacy policy, section 9.

We used the providers below for business development and no longer use them, as the privacy policy, section 4 explains. We have not verified their processing locations or transfer safeguards, so we state none.

ProviderRoleLocation of processingTransfer safeguards
NeverBounce (past use only)Email address verification for business developmentNot verifiedNot verified
Apollo (past use only)Business contact research and saved contactsNot verifiedNot verified
Hunter (past use only)Email address verificationNot verifiedNot verified
ZeroBounce (past use only)Email address verificationNot verifiedNot verified
Email-Checker.net (past use only)Email address verificationNot verifiedNot verified

Changes to this list

We will update this page before engaging a new provider that processes personal data for the website, correspondence or business development, and before any hosted service accepts client data. The "Last updated" date above records the current revision.

We give clients with a processing agreement at least 30 days’ notice by email before changing the subprocessors that process their personal data, including for support engagements. An AAES-hosted deployment requires disclosures covering its actual providers before client data is processed.