Sub-processors
Last updated August 29, 2026
Third-party processors engaged by Auroranexis AI Solutions to deliver the Auroranexis platform.
Last updated August 29, 2026
Third-party processors engaged by Auroranexis AI Solutions to deliver the Auroranexis platform.
Auroranexis AI Solutions uses sub-processors and related service providers to provide hosting, authentication, billing, email delivery, monitoring, and optional AI features. This list is provided for transparency under GDPR Article 28. Inventory version: subprocessors-2026-09-02-v2 Effective date: 2026-09-02
Supabase — Database, authentication, file storage, and related backend services. Role: Processor. Activation: ACTIVE. Usage: Always used for the Service. Location/region: EU-capable regions (as configured for the production project). Data: Account, workspace, operational, and authentication data. Vercel — Application hosting, edge delivery, and deployment runtime. Role: Processor. Activation: ACTIVE. Usage: Always used for the Service. Location/region: As configured for the production deployment. Data: Request metadata, application runtime data, logs as configured. Mollie — Payment processing for subscription billing (PSP only; not Merchant of Record). Role: Payment service provider (transparency listing). Activation: ACTIVE. Usage: Always used for the Service. Location/region: EEA (Mollie as payment service provider). Data: Payment and billing transaction data necessary to process charges. Note: Auroranexis remains the contractual seller for SaaS subscriptions. SMTP / STRATO (transactional email) — Primary transactional product and billing email delivery when SMTP is configured. Role: Processor. Activation: ACTIVE. Usage: Always used for the Service. Location/region: As configured for the production SMTP provider (e.g. STRATO). Data: Email addresses and message content for transactional mail. Note: Production path prefers native SMTP; alternate providers below are optional. Resend — Transactional email delivery when Resend is configured instead of / in addition to SMTP. Role: Conditional processor. Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured for the Resend project. Data: Email addresses and message content for transactional mail. Postmark — Transactional email delivery (code-supported provider adapter). Role: Conditional processor. Activation: CODE-SUPPORTED / NOT ACTIVE. Usage: Conditional / optional. Location/region: As configured if enabled. Data: Email addresses and message content for transactional mail. Note: Adapter/support may exist in codebase; not treated as an active production dependency unless configured. Mailgun — Transactional email delivery (code-supported provider adapter). Role: Conditional processor. Activation: CODE-SUPPORTED / NOT ACTIVE. Usage: Conditional / optional. Location/region: As configured if enabled. Data: Email addresses and message content for transactional mail. Amazon SES — Transactional email delivery (code-supported provider adapter). Role: Conditional processor. Activation: CODE-SUPPORTED / NOT ACTIVE. Usage: Conditional / optional. Location/region: As configured if enabled. Data: Email addresses and message content for transactional mail. Sentry — Application error monitoring when configured. Role: Conditional processor. Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured for the monitoring project. Data: Error reports, stack traces, limited request context (PII scrubbing applied). Google Analytics 4 (GA4) — Consent-gated marketing / conversion analytics when Measurement ID is configured. Role: Optional analytics (consent-gated). Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured for the GA4 property. Data: Pseudonymous usage / conversion events under marketing consent. Note: Client tags and server Measurement Protocol require marketing consent (fail-closed). PostHog — Consent-gated product analytics when configured. Role: Optional analytics (consent-gated). Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured (EU host preferred when set). Data: Pseudonymous product usage events under analytics consent. Plausible — Consent-gated website analytics when configured. Role: Optional analytics (consent-gated). Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured for the Plausible site. Data: Pseudonymous pageview / interaction data under analytics consent. Microsoft Clarity — Consent-gated session analytics when configured. Role: Optional analytics (consent-gated). Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured for the Clarity project. Data: Pseudonymous interaction / session data under analytics consent. OpenAI — Generative AI features when explicitly enabled and configured. Role: Conditional processor. Activation: OPTIONAL / CONFIGURABLE. Usage: Conditional / optional. Location/region: As configured for the AI provider integration. Data: Prompts and related content submitted to optional AI features. Note: Not used unless AI features are enabled for the workspace / platform configuration. Anthropic — Optional generative AI provider path when configured. Role: Conditional processor. Activation: CODE-SUPPORTED / NOT ACTIVE. Usage: Conditional / optional. Location/region: As configured if enabled. Data: Prompts and related content submitted to optional AI features. Note: Provider path may exist; treat as not active unless production credentials are configured. Azure OpenAI — Optional generative AI provider path when configured. Role: Conditional processor. Activation: CODE-SUPPORTED / NOT ACTIVE. Usage: Conditional / optional. Location/region: As configured if enabled. Data: Prompts and related content submitted to optional AI features.
Where sub-processors process data outside the EEA, we rely on appropriate safeguards such as Standard Contractual Clauses and supplementary measures where required. Specific transfer details are available on request.
Material changes to sub-processors are communicated to workspace administrators with reasonable notice and reflected in an updated inventory version. Enterprise customers may request notification procedures or DPA addenda via legal@auroranexis.com.
Sub-processor and DPA inquiries: legal@auroranexis.com. Support: support@auroranexis.com.