Govexa

Subprocessor Notice

Version 1.0-RC2 · Effective date: November 12, 2026

Draft — company registration details are being completed. This document is not yet final.

The following providers may support Govexa. The providers actually used may vary by plan, region and configuration. A provider's listing does not mean that it receives all Customer Data.

ProviderStatusPurposeNoteVerified region (8 November 2026)
AnthropicActive / default for Govexa-managed AIAI inferenceSubprocessor for Govexa-managed use. Processing in the US and internationally may occur. ZDR is not promised unless separately verified.US
OpenAIConditionalOptional AI inferenceSubprocessor only for tenants with Govexa-managed OpenAI enabled.US
Customer's Anthropic/OpenAI accountCustomer-directedBYOAIIf it is Customer's own account/API key, it is not considered a Govexa subprocessor; it is Customer's supplier.Per Customer configuration
Customer's Ollama serverCustomer-directed / self-hostedBYOAICustomer's server; under Customer's control.Per Customer configuration
VercelInfrastructureWeb/application/functionsNo EU-only claim is made unless the EU function region is verified.Functions: EU — Frankfurt (fra1)
RailwayInfrastructureBackend/PostgreSQL/computeNo EU-only claim is made unless the actual deployment region is verified.EU — Amsterdam (europe-west4)
CloudflareInfrastructure/securityDNS/CDN/WAF/DDoS; R2 file storageR2 EU jurisdiction / Regional Services are committed only if actually configured.R2: EU jurisdiction; network: global
SentryConditionalError monitoringOnly if the production integration is enabled. PII-reduction controls in place.Being verified
PaddleMerchant of Record / separate role + necessary processingPayment, tax, invoicing, refundsPaddle's own legal role and terms also apply.United Kingdom
Lemon SqueezyConditional — backup Merchant of RecordPayment, tax, invoicing, refundsOnly if Paddle becomes unavailable and it is activated.US
ZeptoMail (Zoho)E-mail serviceTransactional e-mailEU cluster per current verification; the list is updated if the actual account/cluster changes. Open/click tracking disabled.EU cluster

Source systems connected by the customer such as AWS, Google, Okta, Microsoft Entra, GitHub, Jira and Slack are integration sources from which Govexa pulls data on Customer's behalf. These services, which are Customer's direct suppliers, are not automatically Govexa subprocessors merely because a Govexa connector exists. If Govexa separately uses a service with its own account, its role is assessed separately.

The "Verified region" column reflects the technical verification on the stated date; it is not an EU-only service commitment unless separately committed in writing.

Request a demo