Sub-processors
Last updated July 5, 2026
LiveIndex engages the third-party providers below to operate the Service. Each is bound by its own data-protection commitments. AI-assisted features can be disabled per organization in settings, in which case no delivery metadata is sent to the AI provider. See our Security overview and Data Processing Addendum for more.
Infrastructure and processing
| Provider | Role | Data handled | Region |
|---|---|---|---|
| Google Cloud / Firebase | Hosting, database, authentication | All application data, account and session data | United States |
| OpenAI | AI features (summaries, forecasts narration, AI Analyst) | Delivery metadata: PR/issue titles and statuses, repository and project names. Not used to train models by default. | United States |
| DeepSeek | Generation of LiveIndex’s own marketing and help content | None of your data. Used only for LiveIndex-authored blog and knowledge-base content. | China |
| Brevo | Transactional email | Name and email address for account and notification emails | European Union |
| Stripe | Billing and payments | Billing contact and subscription details; card data is held by Stripe | United States |
Connected sources
You choose whether to connect these. We read from them read-only and store an encrypted access token; you can disconnect at any time.
| Provider | Role | Data handled | Region |
|---|---|---|---|
| GitHub | Connected source | Pull-request and review metadata, repository names, deployment events | United States |
| Atlassian (Jira) | Connected source | Issue metadata and status transitions, project names | United States / global |
| Linear | Connected source | Issue metadata and status, workspace and project names | United States |
| Slack | Connected source and notifications | Channel and message metadata used to summarize activity you point us at; notification delivery | United States |
We will update this page before adding or replacing a sub-processor that handles customer data. For questions, use the security contact form.