Snapvisor
How it worksFeaturesIntegrationsPricingDocs
Sign inStart free

Legal

Deleting your Snapvisor account

How to permanently delete your Snapvisor account and the data attached to it, what we delete, and what we keep. Effective 2026-08-01.

Before you start

Deleting your account is permanent and immediate once you confirm it. There is no grace period and no undo — we cannot restore a deleted account or the builds and screenshots that went with it.

If you are the only owner of a team, deletion is refused and we tell you which team is blocking it. Transfer that team's ownership to another member, or delete the team first, then request deletion again. This protects the other members from losing a workspace they still use.

How to delete your account from the app

  1. Sign in at app.snapvisor.io.
  2. Open your personal account settings — your account menu, then Settings. Account deletion is only available on a personal account, not on a team.
  3. In the Delete Account card, type delete my account to confirm you meant it, and submit.
  4. We email a confirmation link to your primary email address. The link is single-use and valid for 15 minutes; if it expires, start again from your settings.
  5. Open the link while signed in and confirm. Your account and its data are deleted at that moment, and we send a final confirmation email.

If you cannot sign in

If you have lost access to your account or its email address, email [email protected] from the address you signed up with, with the subject Account deletion request. Tell us your account name or slug. We may ask you to prove control of the account or its connected Git provider before we act, so that nobody can delete someone else's data. We action verified requests manually and confirm by email when the deletion is done.

What we delete

Confirming deletion permanently removes, for your personal account:

  • Every project owned by the account, and with each project its builds, build shards, screenshots and screenshot buckets, screenshot diffs and diff reviews, build reviews, build notifications, tests and their recorded statistics, automation rules and their runs, ignored changes, the project audit trail, and project memberships.
  • Comments and reactions on those builds, including other people's, since the builds they belong to no longer exist.
  • Your API and access tokens, and the scopes attached to them, so any CI job or agent using them stops working immediately.
  • Your email addresses on file, including secondary addresses.
  • Your linked Google and GitLab identities. For GitHub we keep the connection record but clear its access token, stored emails, and last-login timestamp.
  • Your team memberships and any invitations still pending for teams that are deleted with you.
  • Your subscription records, and we cancel an active paid subscription with Stripe as part of the deletion.
  • Your Slack connection, which is uninstalled from the workspace.

What we keep, and why

A small amount of data outlives the deletion. We keep it either because removing it would corrupt the history of teams you worked with, or because someone else is legally required to hold it.

  • An anonymous placeholder record for your user. Your user row is kept, stamped with the deletion date and stripped of its email address and sign-in identities. It is displayed as Deleted user and its public handle is replaced with an opaque identifier. This exists so shared history on teams you belonged to — who approved which build — does not break. It holds no contact details and cannot be signed into. We do not currently expire it, so treat it as kept indefinitely.
  • Your reviews, comments, and reactions on other people's projects. Work you did in a team whose projects still exist stays, because it is part of that team's record rather than yours alone. Build approvals are detached from you entirely; comments and reactions remain attributed to the anonymous Deleted user placeholder above.
  • Billing and invoice records held by Stripe. We cancel the subscription and clear our reference to your Stripe customer, but Stripe keeps the payment and invoice history under its own retention policy and the tax and accounting law that applies to it. That retention is Stripe's, not ours, and we cannot shorten it.
  • Stored screenshot files. Deleting your account removes every database record that points at your uploaded images, so they can no longer be reached through Snapvisor, its API, or any link. The underlying files in our object storage are not individually erased by that operation, and we do not currently publish a fixed period after which they are purged. If you need the stored files themselves erased, email [email protected] and we will handle it as an erasure request.
  • Operational logs and diagnostics. Error reports and server logs may briefly contain identifiers from before the deletion. They age out on our providers' normal schedules and are not used to rebuild a deleted account.

Deleting less than everything

You do not have to delete your account to remove data. Deleting a single project from its settings removes that project's builds, screenshots, and history on the same terms as above, and deleting a team removes the team and its projects while leaving your personal account intact.

Questions

If anything here is unclear, or you want to know exactly what we hold about you before deciding, email [email protected]. See also our Privacy Policy and Terms of Service.

Snapvisor

Visual regression testing that catches every pixel before it ships — built on a proven open-source visual-diff engine.

Open source at the core

Product

  • Features
  • How it works
  • Pricing
  • Integrations

Compare

  • vs Percy
  • vs Chromatic
  • vs Applitools
  • vs Argos CI

Docs

  • Quickstart
  • MCP server
  • Access tokens
  • Support

Legal

  • Privacy Policy
  • Terms of Service
  • Delete your account
  • Contact

Contact

  • [email protected]
© 2026 Snapvisor. All rights reserved.Zero third-party runtime requests.