Skip to main content
There are two deletions, both in the console. They are independent: deleting your account does not delete your organizations’ data, and deleting an organization’s data does not delete anyone’s account. The privacy policy is the authoritative description of both. This page says how to do them.

​
Delete your account

Settings → Delete account (/users/settings/delete). You may be asked to log in again first. It happens at once. Deleted:
  • your email address, and your password if you set one;
  • your link to GitHub;
  • every session you are signed in with, in every browser;
  • your place in each organization.
One email confirms it. Kept: every organization keeps its reviews, connections and settings, because they belong to the organization, not to one person. Where they named you, the console now says “a former member”.
If you are the only owner of an organization, nobody will be able to manage or delete its data after your account is gone, until someone is an owner again. Delete the organization’s data first if that is what you want; the page warns you and links to it.
You can sign up again at any time.

​
Delete an organization’s data

Owners only. On the organization’s page, under Delete this organization’s data (/orgs/<login>/delete).
1

Cancel any live subscription

If the organization has an active subscription, cancel it first in Plan & billing → Manage billing. The deletion page will not let you continue until you do. The subscription runs to the end of the period you paid for.
2

Confirm

The page lists how many items of each kind will be deleted. Type the organization’s login and confirm.
3

Reviews stop at once

From that moment CodeWarden does not review the organization’s pull requests or answer mentions. Every owner is emailed the date of the deletion.
4

Deleted 7 days later

The data is deleted seven days after you confirm. Until then, any owner can cancel from the organization’s page, and reviews resume with the next push. Owners are emailed when it is done.

​
What is deleted

Every review record and the code, pull request text and answers in it; replies and rejected findings; measured outcomes; the Jira and Sentry connections and their credentials; the repository list and your switches; and pending background jobs.

​
What is kept, and why

  • The organization’s name and GitHub account, so that installing CodeWarden again finds it.
  • The dates the App was installed, suspended or removed.
  • The billing record and usage counts, because a refund or a dispute can arrive after the deletion. They hold no code and no personal data.
  • The members and their roles, so the owners can still open the organization.
  • A record that the deletion happened: when, who asked, and how many items were removed, never what they contained.
Deleted data leaves backups within 7 days, and a restore never brings it back.

​
What CodeWarden cannot delete for you

  • Comments already posted on pull requests stay on GitHub.
  • The App stays installed. Uninstall it in the installation’s settings on GitHub.
  • Jira’s grant: the person who connected it removes CodeWarden at id.atlassian.com → Connected apps, or a site administrator removes the app.
  • Sentry’s token: revoke it in Sentry’s settings.
  • accepted: lines in .codewarden.yml are in your repository and stay there.
Installing the App again after the deletion reopens the organization.

​
By email

You can also ask for either deletion, a copy of your data, or a correction by writing to contact@codewarden.co from the address on your account.