Privacy Policy

This Privacy Policy explains how Squasher collects, uses, and protects information when you use our website, dashboard, APIs, SDKs, integrations, and related services.

Squasher is an observability and incident response product. Customers decide what telemetry they send to Squasher, and they remain responsible for the content of the events, logs, traces, replays, and related metadata they submit.

We collect account data such as name, email address, team membership, authentication events, plan information, billing status, and support communications.

When you ask for a call on our demo page, we save your answers as you type, after you enter a valid email address. We use them only to reply to you and to follow up about the call, also when you do not finish the form.

We process product data that customers send to Squasher, including errors, logs, traces, metrics, releases, deployments, session replay metadata, monitor checks, incident records, and integration payloads.

We also collect usage and security data such as IP address, device and browser information, request metadata, audit logs, API usage, and diagnostic data needed to keep the service reliable.

We use data to provide Squasher, authenticate users, ingest and search telemetry, create alerts and incidents, generate status page updates, power AI-assisted triage, prevent abuse, debug reliability issues, and support customers.

We may use aggregated or de-identified information to improve the product, understand feature usage, measure performance, and plan capacity. We do not use customer telemetry to identify a person outside the customer workflow that submitted it.

On squasher.ai and in the dashboard at app.squasher.ai we use our own product analytics only with your consent. We record the pages you view and a small set of actions: starting and completing sign-up, creating a project, receiving the first data from an SDK, creating a monitor, and sending a team invite. We do not record names, email addresses, or text you type.

With your consent, your browser stores a random visitor ID in local storage. In the dashboard, the events are also linked to your internal account ID so we can see one person's path through setup. Page addresses are stored without query strings or fragments, and IDs in a path are replaced. We keep a country code, not your IP address.

With your consent, we also record a session replay of your visit to squasher.ai, so we can see where the website is hard to use. Form fields are hidden in the replay. We do not record session replays in the dashboard.

Until you answer, no analytics event is sent and no session replay is recorded. If you decline, neither happens. We store only your answer in your browser so we do not ask again. You can change it at any time with Analytics choices in the website footer or in the dashboard account menu. Declining does not change how Squasher works for you.

Without your consent, we still record errors and page performance on our website, because we need them to keep the site working. Error reports do not include a session replay. They use a session ID in session storage that ends when you close the tab. We do not use advertising cookies.

Squasher uses AI features to summarize incidents, inspect telemetry context, suggest likely causes, and assist with remediation workflows. These features may process the telemetry, code context, incident details, and instructions that customers choose to provide.

We apply access controls and product boundaries so AI workflows operate within the customer project and permissions available to the requesting user or automation.

AI requests go through OpenRouter, Inc., which sends each request to a model host: Together AI, Baseten, TypeSafe, or, as a backup for session replay tagging, Anthropic or another host of the same model. When you ask Squasher to fix an issue, your repository is cloned into a sandbox hosted by Daytona. The full list, with what each provider does and where, is at squasher.ai/subprocessors.

Squasher does not train or fine-tune AI models on customer data.

For short classification calls, such as the decision to start an investigation, we require hosts that keep no prompt data and do not train on it. If no such host is available, the call does not run. Requests from the Squasher agent, dashboard chat, and session replay tagging do not yet carry this requirement, so the data policy of the host that serves the request applies to them.

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

We share information with service providers that help us run the product, such as hosting, storage, payment, security, analytics, support, and communication vendors. These providers are only authorized to process information for Squasher's service operations. The list of providers that process customer data is at squasher.ai/subprocessors.

We may disclose information when required by law, to protect Squasher and our users, to investigate abuse or security issues, or as part of a merger, acquisition, financing, or sale of assets.

Squasher stores the data of every project in the United States, in the AWS us-east-1 region (N. Virginia). We do not offer another data region today. Some providers on squasher.ai/subprocessors process data in other locations, as that page shows.

We retain account, billing, audit, and security records for as long as needed to provide the service, meet legal obligations, resolve disputes, and enforce agreements.

Customer telemetry retention depends on the product area, plan, settings, and any deletion requests or contractual commitments that apply to the account.

We use technical and organizational safeguards designed to protect data, including access controls, encryption in transit, secret isolation, monitoring, and operational review of production access. Details are at squasher.ai/security.

No internet service can guarantee perfect security. Customers should avoid sending unnecessary sensitive personal data in telemetry and should use project-level access controls for their teams.

Depending on your location, you may have rights to access, correct, export, restrict, or delete personal information. Account owners can also manage team access, integrations, API keys, and data forwarding settings in the product.

To make a privacy request, contact support@squasher.ai. We may need to verify your identity and your authority over the relevant account before completing the request.

We may update this policy as Squasher changes. When we make material updates, we will take reasonable steps to notify customers, such as updating this page or sending an account notice.

Continued use of Squasher after an update means the revised policy applies to your use of the service.