Sub-Processors
Last updated: July 28, 2026
Note: Google Workspace integration (Gmail, Google Calendar) is currently disabled while Electryion completes Google's CASA Tier 2 security assessment. Google does not appear in the lists below because we do not request Google scopes or process Google user data at this time.
Electryion uses a small number of carefully vetted sub-processors to operate the Service. Each sub-processor is bound by a Data Processing Agreement (DPA) and commits to appropriate security safeguards. This page lists every sub-processor that may process personal or business data on our behalf, the purpose of the processing, and where the data is stored.
We will notify customers of any material changes to this list at least 30 days in advance via email or in-app notice. If you object to a new sub-processor, you may terminate your subscription before the change takes effect.
1. Infrastructure
| Sub-processor | Purpose | Data location |
|---|---|---|
| Sevalla | Application hosting, database, file storage, background workers. | European Union |
| Cloudflare | DNS, DDoS protection, CDN, optional privacy-friendly analytics. | Global edge network (EU routing preferred) |
2. AI Model Providers
| Sub-processor | Purpose | Data location |
|---|---|---|
| OpenAI | Large language model inference powering all AI employees. Prompts are processed on request and not used for model training under the Zero Data Retention configuration. | United States (SCC-based transfer) |
| OpenRouter | Routing layer in front of OpenAI; used as a failover when the direct OpenAI endpoint is unavailable. Same prompt content as the OpenAI row; no training on customer data. | United States (SCC-based transfer) |
3. Payments & Billing
| Sub-processor | Purpose | Data location |
|---|---|---|
| Stripe | Payment processing, subscription billing, invoicing, tax calculation. Card numbers never touch our servers. | Ireland / United States (SCC-based transfer) |
4. Connected Services (customer-initiated)
The following providers only receive data when the customer explicitly connects them through OAuth. Data flow is initiated by the customer and governed by each provider's own privacy policy.
| Sub-processor | Purpose | Data location |
|---|---|---|
| Microsoft (Outlook, Calendar) | Read/send email and calendar events on behalf of the user after OAuth consent. | Global |
| Profile identification and social posting after OAuth consent. | Global | |
| Meta (Facebook, Instagram) | Social posting after OAuth consent. | Global |
| X (formerly Twitter) | Social posting after OAuth consent. | Global |
| Atlassian (Jira Cloud) | Read tickets and write approved EARS requirements back to issue descriptions for PRISM (Requirements Engineer), only after OAuth consent. | Global (Atlassian-managed) |
| Linear | Read issues and append approved EARS requirements back to issue descriptions for PRISM, only after OAuth consent. | United States |
5. Operational & Monitoring
| Sub-processor | Purpose | Data location |
|---|---|---|
| Sentry | Error and exception monitoring. Configured with PII redaction; passwords, tokens, and API keys are stripped before leaving the app. | European Union |
| Hunter.io | Email enrichment for the lead-generation AI employee (only when the customer triggers enrichment). | European Union |
| Apify | Public web scraping for lead research (only when the customer triggers scraping). | European Union / United States |
6. Transfers Outside the EEA
Where a sub-processor operates outside the European Economic Area, Electryion relies on the European Commission's Standard Contractual Clauses (SCCs) and, where applicable, adequacy decisions to ensure an equivalent level of data protection.
7. Bundled Data Sources
Some features use openly licensed datasets that ship with the product. No customer data is sent to these providers.
| Source | Purpose | License |
|---|---|---|
| GeoNames | City names and coordinates powering the kilometre-radius option in candidate search. | CC BY 4.0 |
8. Questions
To request our current DPA, ask about a specific sub-processor, or object to a new sub-processor, email [email protected].