Sub-processors
Sub-processors.
The services that process data on our behalf to run Trawler. Where each one runs is where your data can be.
Last updated:
| Service | What it receives | Why | Where |
|---|---|---|---|
| Railway | All application data: workspaces, projects, runs, findings, encrypted keys and passwords, logs, and screen captures | Hosting of the app, its database, the hosted runners and the storage for screen captures | European Union (Netherlands, EU West) |
| Cloudflare | DNS queries for usetrawler.com | DNS | Global |
| GitHub | The name, email address and picture of people who sign in with GitHub | Sign-in | United States |
| The name, email address and picture of people who sign in with Google | Sign-in | United States | |
| OpenRouter | A product's public page, and its documentation page when you give one, during setup; prompts and page content of runs paid by Trawler or with an OpenRouter key | Setup, the first run on Trawler, and runs of workspaces that use OpenRouter. OpenRouter passes each call on to a provider that serves the model, which can be outside the United States. | United States, and the serving provider's region |
| OpenAI, Anthropic, Google (Gemini) or an OpenAI-compatible service | Prompts and page content of runs | Only for a workspace that brings its own key for that provider | The provider's own |
| Sentry | Error reports and request counts, with secrets masked and no cookies, request bodies or user details | Finding and fixing failures in the app and the hosted runners | European Union |
The local runner sends nothing to Trawler or Sentry. We announce a new sub-processor on this page before it receives data.