Processing chain
Subprocessor transparency
Inventory of suppliers that may process personal data when Aixy provides the service.
How to read this list
This is the current architecture inventory while the stronger GDPR claim remains disabled. Only suppliers verified as active in production and covered by incorporated data-processing terms may appear as confirmed subprocessors in the final list. “Conditional” means the supplier processes data only when the related feature is enabled. Customer-selected model, telemetry and MCP providers vary by account and instruction and may be direct customer recipients rather than Aixy subprocessors.
Amazon Web Services
CorePurpose: compute, networking, databases, encryption, logs, backups and operational analytics.
Primary location: Frankfurt, Germany (eu-central-1).
Public terms reviewed: AWS GDPR and DPA information.
Before publication: retain account acceptance, verify contracting entity, services, support access and transfer safeguards.
Cloudflare
CorePurpose: DNS, edge delivery, website hosting and same-origin dashboard routing.
Location: global edge network.
Public terms reviewed: Cloudflare Customer DPA.
Before publication: retain account acceptance and verify active products, log settings and transfer safeguards.
Datadog
VerifyPurpose: infrastructure and product observability without prompts or responses.
Configured site: Datadog EU; production account and support-access model still require verification.
Public terms reviewed: Datadog DPA.
Before publication: confirm production activation, account acceptance, retention and transfer mechanism.
Resend
ConditionalPurpose: invitations, password resets and operational notification email.
Data: recipient address, message content and delivery metadata.
Public terms reviewed: Resend DPA.
Before publication: confirm production activation, account acceptance, contracting entity, retention and transfer mechanism.
Google Workspace
VerifyPurpose: company email, including privacy, support and design-lead correspondence.
Location: global processing and support locations; the current Business Starter edition does not provide a selectable Workspace data-region policy.
Public terms reviewed: Google Cloud Data Processing Addendum and Google Workspace subprocessors.
Before publication: retain corporate account and CDPA acceptance evidence, then complete the transfer, retention, support-access and deletion assessment.
Stripe
ConditionalPurpose: subscription checkout, billing portal and payment status.
Data: billing contact and transaction information; Aixy stores only a bounded subscription projection.
Public terms reviewed: Stripe DPA.
Before publication: confirm production activation, account acceptance, controller/processor allocation and applicable Stripe entity.
Customer-selected model providers
By instructionPurpose: perform the inference request selected by the customer.
Location: depends on provider, account, endpoint and region selected by the customer.
Before use: record the provider, role, region, DPA, training/retention settings and any Chapter V transfer mechanism.
Customer-selected MCP and telemetry destinations
By instructionPurpose: receive a user-authorized tool call or bounded telemetry selected by the customer.
Location: depends on the external service, tenant, account and endpoint.
Before use: record account ownership, role, scopes, DPA/terms, retention, region, transfer mechanism, revocation and incident contact. MCP call history does not store tool arguments or results.
Change notifications
The executed DPA must define advance notice and a reasonable objection mechanism before Aixy appoints a new subprocessor for customer personal data. Contact [email protected] for the current verified list.