Subprocessors
Last updated: 2026-05-29
To run Cruxible, we use a small set of third parties that process data on our behalf ("subprocessors"). This page lists them, what they do, and where they operate. It supports our Privacy Policy. Cruxible is operated remotely, so processing may take place in the regions listed below; where data is transferred across borders we rely on appropriate safeguards (see the international-transfers section of the Privacy Policy).
Infrastructure subprocessors
These run for every account.
| Subprocessor | Function | Regions |
|---|---|---|
| Clerk | Authentication and user identity | United States |
| Neon | Postgres database (accounts, runs, run history) | United States or European Union, depending on configuration |
| Polar.sh | Billing and Merchant of Record (payment and refund processing) | United States and European Union |
| Vercel | Frontend hosting and content delivery | Global edge network |
| Fly.io | Backend hosting | United States or European Union, depending on configuration |
Research-pipeline subprocessors
These process data when you run a scout.
| Subprocessor | Function | Regions |
|---|---|---|
| OpenRouter | Large language model gateway. OpenRouter routes requests to underlying model providers, which act as further subprocessors. | United States and other regions |
| VoyageAI | Text embeddings | United States |
| DuckDuckGo | Default web search retrieval | United States and other regions |
| Serper | Web search retrieval (used only when enabled in configuration) | United States |
| Exa | Semantic web search retrieval (used only when enabled in configuration) | United States |
Changes
When we add or remove a subprocessor, we will update this page and the "Last updated" date. Where required, we will provide advance notice so you can object before a change takes effect. To be notified of changes, contact admin@trycruxible.com.