You can delete your account yourself, at any time, without contacting support. Sign in, open Account settings, then use Delete account in the Danger zone. You will be asked to type your account email before the deletion is submitted. It takes effect immediately and cannot be undone.
Open Account settings and scroll to the Danger zone.
Choose Delete account, review the consequences, and confirm with your email address.
What is deleted, and what is kept
GoodQA is a team tool, so deleting your account is not the same as removing all of your work from it. Your personal account is destroyed; the work you did for your team stays with your team, with your name taken off it. Here is the whole picture.
Deleted permanently, right away
Your account itself: email address, name, avatar, password, and sign-in history.
Your profile: phone number, location, bio, links, timezone, working hours and availability.
Every active session, connected sign-in provider, and push-notification device.
Your memberships in every organization and project, and any API keys you created.
Your direct messages. A one-to-one DM conversation is deleted outright, for both people. In a group DM that other people are still in, the conversation stays but your messages are emptied and shown as deleted.
Files and recordings you uploaded that were never shared — never attached to a bug, comment, mission, test plan or release, and never filed into a Drive folder. These are deleted from GoodQA immediately and the stored files are removed from the live service. See "Stored copies of deleted files" below for what happens underneath.
Kept by your team, with your name removed
Deleting your account must not delete your colleagues' bug reports. So the work you contributed stays where it is, and the link to you is severed — it no longer shows your name, and it is no longer connected to any account.
Bugs and issues you reported, and comments you wrote on them.
Project and issue chat messages you posted. Direct messages are not in this group.
Screenshots, screen recordings and files you attached to anything your team can see.
Test plans, missions, releases, decisions and estimates you worked on.
Change history, with your identity removed from each past revision.
One thing to know before you delete: removing your name does not rewrite what you typed. If you wrote a phone number or another personal detail into a bug report, a comment or a chat message, that text stays in your team's content. Edit or delete anything like that first — you can still do it while you are signed in.
Kept longer, and honestly, why
Security and admin logs. If you took an administrative action — changing an organization's settings, creating an API key — a log entry records that the action happened. These logs cannot be edited or deleted, on purpose: that is what makes them trustworthy. Once your account is gone, the entry no longer holds your name or email, only an identifier that no longer points to anyone. Logs belonging to an organization are deleted when that organization is deleted.
Recordings and files your team can see. These belong to your organization once shared, and we do not delete them on a timer. They are kept until you, or someone in your organization, deletes them — or until the organization is deleted, which removes them too. If you want a recording gone, delete it before you close your account.
Your organization's billing records. Invoices and payment history belong to the organization, not to your personal account, and are not affected by deleting it. They contain no personal account details of yours.
Stored copies of deleted files. When a file or recording is deleted it stops being reachable through GoodQA straight away — nobody can open it, and no link to it will work. Underneath, our cloud storage keeps a previous-version copy that is not erased at the same moment, and today we do not put an expiry on that copy. It is not reachable by you, your team, or anyone using GoodQA.
Database backups. We take a full database backup every day and keep the last seven, plus seven days of transaction logs, so we can recover from a disaster. Deleted data therefore still exists in those backups until they age out, which takes up to about a week. A backup restores the entire database, so it is not a way to bring one deleted account back.
Our service providers. The companies listed in our Privacy Policy — including our email, error-monitoring and AI providers — hold their own copies of what was sent to them, governed by their own retention terms. Deleting your GoodQA account does not reach into those systems. If you signed in with Apple, we do tell Apple to revoke that connection.
How long is it kept?
We would rather tell you the truth than quote a number we do not enforce: GoodQA does not delete organization content on a fixed schedule. There is no automatic expiry date on issues, comments, chat, recordings or files. They are kept until someone deletes them, or until the organization is deleted. An organization can turn on its own retention rules, but those archive old content rather than destroy it. If you need content gone by a certain date, delete it yourself or ask your organization owner.
Before you delete
Take a copy. Account settings has an "Export your data" section with a Download my data button. It gives you one JSON file containing everything you authored — your profile, issues, comments, team chat, direct messages, and a list of your files. Do this first; deletion cannot be reversed, and your direct messages are not recoverable afterwards.
Hand over any organization you own alone. If you are the only owner of an organization, deletion is refused until you promote another owner or delete the organization, so it is not left with nobody who can administer it. You will be told which organizations to deal with.
Clean up anything personal you put in shared content, as described above.
If you cannot sign in, if deletion reports an error you cannot resolve, or if you need a privacy request handled manually, email [email protected] from the address associated with the account.
We use essential cookies to keep you signed in. See our Privacy Policy for details, including how to opt out later.
You can delete your account yourself, at any time, without contacting support. Sign in, open Account settings, then use Delete account in the Danger zone. You will be asked to type your account email before the deletion is submitted. It takes effect immediately and cannot be undone.
Open Account settings and scroll to the Danger zone.
Choose Delete account, review the consequences, and confirm with your email address.
What is deleted, and what is kept
GoodQA is a team tool, so deleting your account is not the same as removing all of your work from it. Your personal account is destroyed; the work you did for your team stays with your team, with your name taken off it. Here is the whole picture.
Deleted permanently, right away
Your account itself: email address, name, avatar, password, and sign-in history.
Your profile: phone number, location, bio, links, timezone, working hours and availability.
Every active session, connected sign-in provider, and push-notification device.
Your memberships in every organization and project, and any API keys you created.
Your direct messages. A one-to-one DM conversation is deleted outright, for both people. In a group DM that other people are still in, the conversation stays but your messages are emptied and shown as deleted.
Files and recordings you uploaded that were never shared — never attached to a bug, comment, mission, test plan or release, and never filed into a Drive folder. These are deleted from GoodQA immediately and the stored files are removed from the live service. See "Stored copies of deleted files" below for what happens underneath.
Kept by your team, with your name removed
Deleting your account must not delete your colleagues' bug reports. So the work you contributed stays where it is, and the link to you is severed — it no longer shows your name, and it is no longer connected to any account.
Bugs and issues you reported, and comments you wrote on them.
Project and issue chat messages you posted. Direct messages are not in this group.
Screenshots, screen recordings and files you attached to anything your team can see.
Test plans, missions, releases, decisions and estimates you worked on.
Change history, with your identity removed from each past revision.
One thing to know before you delete: removing your name does not rewrite what you typed. If you wrote a phone number or another personal detail into a bug report, a comment or a chat message, that text stays in your team's content. Edit or delete anything like that first — you can still do it while you are signed in.
Kept longer, and honestly, why
Security and admin logs. If you took an administrative action — changing an organization's settings, creating an API key — a log entry records that the action happened. These logs cannot be edited or deleted, on purpose: that is what makes them trustworthy. Once your account is gone, the entry no longer holds your name or email, only an identifier that no longer points to anyone. Logs belonging to an organization are deleted when that organization is deleted.
Recordings and files your team can see. These belong to your organization once shared, and we do not delete them on a timer. They are kept until you, or someone in your organization, deletes them — or until the organization is deleted, which removes them too. If you want a recording gone, delete it before you close your account.
Your organization's billing records. Invoices and payment history belong to the organization, not to your personal account, and are not affected by deleting it. They contain no personal account details of yours.
Stored copies of deleted files. When a file or recording is deleted it stops being reachable through GoodQA straight away — nobody can open it, and no link to it will work. Underneath, our cloud storage keeps a previous-version copy that is not erased at the same moment, and today we do not put an expiry on that copy. It is not reachable by you, your team, or anyone using GoodQA.
Database backups. We take a full database backup every day and keep the last seven, plus seven days of transaction logs, so we can recover from a disaster. Deleted data therefore still exists in those backups until they age out, which takes up to about a week. A backup restores the entire database, so it is not a way to bring one deleted account back.
Our service providers. The companies listed in our Privacy Policy — including our email, error-monitoring and AI providers — hold their own copies of what was sent to them, governed by their own retention terms. Deleting your GoodQA account does not reach into those systems. If you signed in with Apple, we do tell Apple to revoke that connection.
How long is it kept?
We would rather tell you the truth than quote a number we do not enforce: GoodQA does not delete organization content on a fixed schedule. There is no automatic expiry date on issues, comments, chat, recordings or files. They are kept until someone deletes them, or until the organization is deleted. An organization can turn on its own retention rules, but those archive old content rather than destroy it. If you need content gone by a certain date, delete it yourself or ask your organization owner.
Before you delete
Take a copy. Account settings has an "Export your data" section with a Download my data button. It gives you one JSON file containing everything you authored — your profile, issues, comments, team chat, direct messages, and a list of your files. Do this first; deletion cannot be reversed, and your direct messages are not recoverable afterwards.
Hand over any organization you own alone. If you are the only owner of an organization, deletion is refused until you promote another owner or delete the organization, so it is not left with nobody who can administer it. You will be told which organizations to deal with.
Clean up anything personal you put in shared content, as described above.
If you cannot sign in, if deletion reports an error you cannot resolve, or if you need a privacy request handled manually, email [email protected] from the address associated with the account.