Legal · last updated 4 October 2026
Subprocessors
The third parties that process data so Elpis can run, and what each of them does. This list is part of our DPA and Privacy Policy.
| Subprocessor | Purpose | Data processed |
|---|---|---|
| Neon | Hosted Postgres database (accounts, incidents, settings) | Account and incident data at rest |
| Cloudflare | Edge delivery and tunnel for the web app (HTTPS, routing, abuse protection) | Traffic in transit |
| FormSubmit | Relays apply-form submissions to our inbox | Name, email, company, team size, stack, goal |
| Google (Gmail) | Our support and application email mailbox | Emails you send us |
| Elpis-managed Ollama | Self-hosted open-source LLM used as a fallback when you have not set your own key | Prompt content for those investigations |
| Your LLM provider (BYOK) | The OpenAI-compatible endpoint you configure with your own key. Your direct relationship, not our subprocessor | Incident content sent when you set a key |
We may replace a subprocessor or add one when it improves the service. The date on this page shows when it last changed, and the current list always lives here. Your own LLM provider is listed for clarity: when you use your own key you engage that provider directly.
Questions about a subprocessor: notsekiro11@gmail.com.