← Back

Privacy

Last updated: May 17, 2026

Deploy Failures reads your failed-deployment data from the Vercel REST API on your behalf via an OAuth integration you choose to install. This page describes what is read, where it goes, and how to make it stop.

What we read

Only the data needed to render the dashboard you see. For each failed deployment Vercel returns to us:

  • Project name and team slug
  • Environment (production / preview / development)
  • Deployment timestamp, deployment URL, deployment state
  • Commit SHA and branch name when available

We also read your account username so the top bar can display who you're signed in as.

What we never read

  • Source code or repository contents
  • Environment variables, secrets, or build logs
  • Successful deployments
  • Anything outside the read-only scopes you authorize at install time (deployment, project, team, user)

Where data lives

  • Deployment data: in your browser's localStorage. It is not sent to or stored on any server we run.
  • OAuth access token: in a session cookie scoped to this domain. The cookie is httpOnly, sent only to this site, and encrypted server-side so its contents are not readable from logs or proxies.

Who we share with

Nobody. There are no third-party analytics, no trackers, no advertising, no data sales. The only outbound network call from our server is to the Vercel REST API on your behalf.

Your rights

  • Uninstall the integration from inside the app (“Uninstall” button in the top bar) or from your Vercel dashboard at any time. This invalidates the access token immediately.
  • Clear your browser's data for this site to remove the local cache.
  • Email [email protected] with any questions.