Subprocessors

These are the third parties that process customer data for Squasher. For each one, we tell you what it does, which data it gets, and where.

The location is the place where the provider processes the data when our configuration sets it. When our configuration does not set it, the location is the country where the provider is based.

Amazon Web Services, Inc. Runs the Squasher API, the ingest service, and the event database, and stores ingest batches that we hold for retry. Data: all telemetry that you send, and application logs. Location: United States (us-east-1, N. Virginia).

Cloudflare, Inc. Runs the website, the dashboard, the edge of the API and ingest endpoints, the Squasher agent, and notifications. Stores session replays, source maps, and short-lived caches, and connects our services to the databases. Data: all requests to Squasher, session replays, and source maps. Location: global network; stored files in eastern North America.

PlanetScale, Inc. Hosts the Postgres database. Data: accounts, organizations, projects, integration settings, encrypted access tokens, incidents, on-call schedules, and billing status. Location: United States (AWS us-east-1, N. Virginia).

OpenRouter, Inc. Sends each AI request to a model host. Data: the telemetry, incident details, code context, and instructions in the request. Location: United States.

Together AI and Baseten, Inc. Host the main model for the Squasher agent, dashboard chat, and session replay tagging. Data: the content of these requests. For dashboard chat, OpenRouter can use another host of the same model when both are unavailable. Location: United States.

TypeSafe. Hosts the model for short classification calls, such as the decision to start an investigation. Data: a bounded summary of the signal or request. Location: not published by the provider.

Anthropic, PBC, or another host that OpenRouter lists for the same model. Serves the backup model for session replay tagging when the main model is unavailable. Data: session replay events. Location: United States.

Daytona Platforms, Inc. Hosts the sandbox in which the agent clones your repository, runs your tests, and pushes a fix branch. Data: your source code and a GitHub token for one repository. Location: United States.

Resend (Plus Five Five, Inc.). Sends sign-in links, invitations, alert emails, mention emails, weekly summaries, and status page emails. Data: email addresses and the content of these emails. Location: United States.

Twilio Inc. Sends on-call pages by SMS and voice call, and verifies responder phone numbers. Data: phone numbers and the text of the page. Location: United States.

Stripe, Inc. Processes payments and subscriptions. Data: the billing contact email, the organization name, the plan, and usage quantities. Stripe collects card details directly; they do not go through Squasher. Location: United States.

Attio Ltd. Stores the answers that you give on the demo request form, so that we can reply. Data: name, email address, company, team size, current tool, and the incident description that you write. Location: United Kingdom.

Cal.com, Inc. Shows the booking calendar on the demo page and books the call. Data: the details that you enter to book. Location: United States.

Analytics on squasher.ai and in the dashboard are sent to Squasher itself. We do not use a third-party analytics service.

When you sign in with GitHub or Google, or connect an integration such as GitHub, Slack, or a webhook, Squasher sends data to that service because you asked for it. Your own agreement with that service applies.

If your organization adds its own OpenRouter key, AI requests use that key and the settings of your OpenRouter account.

We update this page when the list changes. For questions about this list, email support@squasher.ai.