This page lists the sub-processors Geocast engages to deliver the Geocast service to operators. It is incorporated by reference into:
- The Geocast Operator Terms of Service, Section 6.4, at geocast.ai/legal/operator-terms
- The Geocast Privacy Policy, Section 05, at geocast.ai/legal/privacy
- The Geocast Data Processing Addendum, Sections 4.3, 6.1, and Annex III, at geocast.ai/legal/dpa
This page is the canonical source for the current sub-processor list. Operators, procurement teams, and regulators relying on the contractual sub-processor commitments in the documents above should treat this page as the operative list.
Status flags
As of April 2026, Geocast is in Early Access, with sub-processors provisioned for initial deployments. Where a sub-processor is selected and contractually engaged but not yet processing live operator data, that status is flagged explicitly. This page reflects the architecture as currently designed; it will be updated as the service expands and as the architecture evolves.
Categories
Sub-processors fall into two categories under the DPA: named data-handling sub-processors (substantive Operator Personal Data processing, listed individually, 30-day advance notice on changes per DPA Section 4.4); and operational sub-processor categories (operational role, listed by category, no advance-notice requirement per DPA Section 4.5). A third group, banking and corporate services, is listed for transparency but is not a sub-processor relationship for Operator Personal Data.
OUR COMMITMENTS. Every sub-processor is engaged under a written data processing contract with obligations no less protective than those in the DPA. AI sub-processors are configured to use zero-data-retention endpoints. No sub-processor uses Operator Personal Data to train AI models or for any independent purpose.
Geocast offers two independent channels for receiving sub-processor change notices, both designed to integrate cleanly with internal compliance and procurement workflows.
- RSS feed. A machine-readable feed of changes to this page is published at geocast.ai/legal/sub-processors/feed.xml. Procurement and compliance teams can subscribe in their feed reader of choice.
- In-product notice. Active operators receive an entry in the Geocast admin app's change log, plus a banner on this page when a change is published.
The 30-day advance notice window for named data-handling sub-processor changes (per DPA Section 4.4) is measured from the banner posting and the sub-processor page update.
The following sub-processors process Operator Personal Data in a substantive way. Each is engaged under a written data processing contract that imposes data protection obligations no less protective than those in the Geocast DPA.
2.1AI inference and content generation
| Sub-processor & contracting entity | Function | Region | Transfer mechanism (EU/UK/CH → US) | Data categories | Status |
|---|---|---|---|---|---|
| Anthropic, PBC anthropic.com Delaware Public Benefit Corporation. US contracting entity. | LLM inference for the Story Writing Agent, the Property Research Agent, Geocast AI, the Story Interviewer, and other AI tools | United States | EU-US DPF, UK Extension, Swiss-US DPF SCCs Module 2 as backup | Operator Content, Operator-provided context for content generation, prompts and responses (zero-retention configuration) | Provisioned |
| ElevenLabs, Inc. elevenlabs.io Delaware corporation. US contracting entity. The only ElevenLabs entity covered under DPF certification. | Voice cloning and audio narration synthesis | United States | EU-US DPF, UK Extension, Swiss-US DPF SCCs Module 2 as backup | Voice samples (where the operator uses voice cloning), generated audio content, narration scripts | Provisioned |
API calls to Anthropic and ElevenLabs are configured to use zero-data-retention endpoints where the sub-processor offers them. Inputs and outputs are not retained by the sub-processor beyond the lifecycle of the request, are not used to train or improve the sub-processor's models, and are not logged for purposes other than abuse monitoring required by law. See DPA Section 3.3 for full commitments.
2.2Cloud infrastructure and hosting
| Sub-processor & contracting entity | Function | Region | Transfer mechanism (EU/UK/CH → US) | Data categories | Status |
|---|---|---|---|---|---|
| Amazon Web Services, Inc. aws.amazon.com Delaware corporation. Contracting entity for US-region accounts. | Primary infrastructure for application hosting, data storage, compute, content delivery in US regions | United States (us-east, us-west) | EU-US DPF, UK Extension, Swiss-US DPF SCCs Module 2 as backup | All Operator Personal Data and Operator Content for properties hosted in US regions; encrypted at rest and in transit | Provisioned |
| Amazon Web Services EMEA SARL aws.amazon.com/legal/aws-emea Luxembourg société à responsabilité limitée. Contracting entity for EU-region accounts. | Primary infrastructure for application hosting, data storage, compute, content delivery in EU regions | European Union (eu-west, eu-central) | Not applicable. Operator data hosted in EU regions under AWS EMEA SARL stays within the EU; no third-country transfer occurs at the AWS contracting layer. | All Operator Personal Data and Operator Content for properties hosted in EU regions; encrypted at rest and in transit | Provisioned |
Where infrastructure permits, Geocast processes Operator Personal Data in the region closest to where it is collected. Operator and guest data from properties in the European Economic Area is hosted in EU regions. See Privacy Policy Section 06 for full transfer mechanism commitments.
2.3Payment processing
| Sub-processor & contracting entity | Function | Region | Transfer mechanism (EU/UK/CH → US) | Data categories | Status |
|---|---|---|---|---|---|
| Stripe, Inc. stripe.com Delaware corporation. Primary US contracting entity for Geocast. | Payment processing for operator subscriptions | United States; payment data may be processed regionally based on operator location | EU-US DPF, UK Extension, Swiss-US DPF SCCs Module 2 as backup | Operator billing contact information, payment method tokens (full card data is held by Stripe, not by Geocast) | Provisioned |
| Stripe, LLC stripe.com Delaware limited liability company. Additional contracting party for purposes of personal data processing under Stripe's standard agreement. | Personal data processing as additional party to Stripe's services agreement | United States | EU-US DPF, UK Extension, Swiss-US DPF SCCs Module 2 as backup | Same categories as above; processing role only | Provisioned |
| Stripe Payments Europe, Limited (SPEL) stripe.com Irish private limited company. Contracting entity for European-located Stripe Users; relevant where European operators contract with Stripe directly for their own payment-acceptance needs. | EU contracting entity (where applicable to operators) | Ireland (Dublin) and EEA branches | Not applicable. Where European operators contract with SPEL directly, transfers to/from SPEL stay within the EEA at the Stripe contracting layer; PCI-DSS card processing may involve onward transfers governed by Stripe's own DPA. | Same categories as above for European operators | Provisioned |
Geocast does not store full card numbers. Stripe holds the card data; Geocast holds tokenized references and billing metadata.
2.4Email and operator communication
| Sub-processor & contracting entity | Function | Region | Transfer mechanism (EU/UK/CH → US) | Data categories | Status |
|---|---|---|---|---|---|
| Google LLC workspace.google.com Delaware limited liability company. US contracting entity for Google Workspace globally. | Operator support email, team communication, document collaboration (Google Workspace, Gmail) | United States, with regional processing per Google Workspace's data residency configuration | EU-US DPF, UK Extension, Swiss-US DPF SCCs Module 2 as backup | Operator support communications, team communications, attachments where operators send them | In production |
Google Workspace handles email and document collaboration for the Geocast team. Operator-side email Geocast sends (notifications, billing, breach notifications) flows through Google Workspace. Transactional email at scale (in-product notifications, password resets, system messages) is sent via the operational sub-processor in Section 3.5.
The following categories cover sub-processors whose role is operational rather than substantively data-handling. Changes within these categories do not trigger the 30-day advance notice obligation per DPA Section 4.5, provided the change does not materially expand the categories of personal data processed or the regions of processing.
The "Under evaluation" status is an Early Access artifact, not the steady state.
Several operational categories below are currently marked "Under evaluation" while Geocast is in Early Access and initial deployments are being provisioned. Once initial vendors are selected for these operational categories, the finalized list will establish the baseline against which future changes are evaluated. Any subsequent material change to a finalized vendor selection (including replacement, region change, or category expansion) will trigger standard notification per the DPA Section 4 mechanics.
- Function
- Capture application errors, performance metrics, and operational telemetry to support service reliability
- Current vendor
- Under evaluation Candidate vendors include Sentry (sentry.io), Datadog (datadoghq.com), and Honeycomb (honeycomb.io). Final selection will be reflected here as initial deployments come online.
- Region of processing
- United States by default; EU region available where the selected vendor offers it
- Data categories
- Application logs, error stack traces, performance metrics, anonymized request metadata. Personal data is excluded from telemetry where feasible; where personal data appears in error context, retention is short and access is restricted.
- Function
- Aggregate, anonymized analytics on use of the marketing site and the admin web companion
- Current vendor
- Under evaluation Candidate vendors include Plausible (plausible.io), Fathom Analytics (usefathom.com), and PostHog (posthog.com). Selection prioritizes privacy-friendly analytics that operate without third-party cookies and do not require cookie consent banners under EU and UK rules.
- Region of processing
- EU for Plausible and Fathom; US for PostHog
- Data categories
- Aggregated page-view data; no personal identifiers; no cross-site tracking
- Function
- Operator support ticket management, knowledge base, and (potentially) in-product chat support
- Current vendor
- Not yet engaged Geocast handles operator support directly through email at the contact addresses in Section 05. A dedicated support tool will be selected as customer volume warrants. Candidate vendors include Plain (plain.com), Intercom (intercom.com), and Help Scout (helpscout.com).
- Region of processing
- Will be selected for EU data residency where applicable
- Data categories
- Support ticket content, operator-supplied attachments, conversation history
- Function
- DNS resolution, edge caching, content delivery, DDoS mitigation, web application firewall
- Current vendor
- Under evaluation Candidate vendors include Cloudflare (cloudflare.com) and AWS CloudFront (the latter is bundled within the AWS relationship in Section 2.2 if selected).
- Region of processing
- Global edge network with primary data planes in United States and EU regions
- Data categories
- Request metadata (IP addresses, user agents), TLS termination, transient request content. Edge sub-processors do not retain Operator Personal Data beyond request handling.
- Function
- System-generated email at scale (account verification, password resets, billing notifications, breach notifications, sub-processor change notifications, system status emails)
- Current vendor
- Under evaluation Candidate vendors include Postmark (postmarkapp.com), Resend (resend.com), and SendGrid (sendgrid.com).
- Region of processing
- United States by default; EU region available where the selected vendor offers it
- Data categories
- Operator email addresses, email subject and body content for system-generated email, delivery status
- Function
- Customer relationship management, operator account management, sales pipeline tracking, marketing automation
- Current vendor
- Not yet engaged for Operator Personal Data Geocast does not currently use a CRM to manage operator accounts; operator account data is held in Geocast's own application database (hosted on the Section 2.2 cloud infrastructure) and operator support is handled directly via email through the Section 2.4 Google Workspace relationship. As Geocast scales, a CRM may be adopted; candidate vendors include Attio (attio.com), HubSpot (hubspot.com), and Salesforce (salesforce.com). When a CRM is adopted that holds Operator Personal Data, it will be added to Section 02 as a named data-handling sub-processor with the standard 30-day advance notice.
- Region of processing
- Will be selected for EU data residency where applicable when a vendor is adopted
- Data categories
- When adopted, will hold operator account information, account managers' contact details, and sales/account-management notes
For clarity: Geocast uses Apollo (apollo.io) and Clay (clay.com) for outbound prospecting to identify and reach potential operators. These tools process information about prospects (people Geocast might want to reach about Geocast) sourced from public business databases. Prospects are not Operators and prospect data is not Operator Personal Data under the DPA. The moment a prospect signs up as an operator, their account data flows into Geocast's own systems and is governed by this Sub-processor List and the DPA. Apollo and Clay are listed here for transparency about Geocast's outbound vendor stack but are not sub-processors of Operator Personal Data and do not appear in the Section 02 inventory.
The following relationships are listed for transparency but are not sub-processor relationships for Operator Personal Data. These are Geocast's own commercial banking and incorporation relationships. Operator Personal Data does not flow to these vendors. They are not subject to DPA Section 4 sub-processor obligations.
| Vendor | Function | Operator Personal Data flow |
|---|---|---|
| Mercury Technologies, Inc. mercury.com | Geocast's business banking (operating account) | None. Mercury holds Geocast's corporate funds; no Operator Personal Data flows to Mercury. |
| Stripe Atlas stripe.com/atlas | Geocast's incorporation platform (Delaware C-Corp formation) | None. Atlas was used to incorporate Geocast AI, Inc. in Delaware; no Operator Personal Data flows to Atlas. |
These are listed because operator procurement teams sometimes ask for full transparency on Geocast's vendor stack. The legal status is unambiguous: these are Geocast's own relationships, not sub-processors of Operator Personal Data.
For sub-processor questions, change-notice subscriptions, or related legal inquiries:
- Sub-processor and legal questions: legal@geocast.ai