Privacy

The short version

This website uses no cookies, no advertising trackers and no third party analytics, and stores nothing on your device. The one thing we count is visits to private pages we make for a company and send to someone there, so we know whether our message was useful. When you contact us, we only use what you send to reply to you.

What we collect on this website

• Demo requests and messages. The demo form sends us your name, work email, company and what you'd like tested, so Oscar can reply and set up a call. If you send it after opening a private page we made for your company, we link the request to that company. We keep requests and emails to reply and follow up, and delete them when you ask.
• Server logs. Our hosting and our network provider (Cloudflare) keep standard request logs, such as IP address and browser type, for security and to keep the site running. Our hosting deletes them after 14 days.

Private pages we send to companies

Sometimes we test a company's public website and send someone there a private page with the results (an address that starts with fireyourqa.com/for/). On those pages we record:

• when the page was opened and how long it was open
• whether the video was played, and how far
• which other pages of this website were opened from it during the same visit, and how long each was open
• clicks on Book a demo or our email link

These records are tied to the company the page was made for. We don't record your name, email or IP address with them, we don't use cookies or store anything on your device, and no third party receives them. To follow the visit from one page to the next, links carry a short code that is removed from the address bar as soon as the page opens. We use the records only to follow up the message we sent, which is our legitimate interest, and delete them after 6 months. To have them deleted sooner, email [email protected].

Customer data in the product

Fire Your QA tests your application using the test accounts and test data you give it access to. Test runs produce screenshots, recordings and reports. These are stored in the tools you connect, such as your documentation space, issue tracker or chat, and are only shared with your team. We ask customers to point Fire Your QA at staging or test environments, not at live customer data.

Our Jira app and Slack connection

When your Jira admin installs the Fire Your QA app, we keep the following on our server in Germany:

• Your Jira site. Its address and the IDs Atlassian sends with each request, plus a short lived access token from Atlassian (it expires within 4 hours) that lets the app read the ticket being tested and post the result on it.
• The settings your admin enters. The address of the app to test, the test logins and passwords, and any notes for the tester. Passwords are never shown again after saving.
• Each test. The ticket key, the Atlassian account ID of the person who pressed the button, when it ran, the result and links to it.
• Slack, if you connect it. The workspace and channel you picked, and the access token Slack gives us to post there. Disconnecting Slack in the app settings deletes the token.

When a test runs, we read that ticket's title, description and recent comments, and test your app on our own computer. Screenshots and a short video go back to the ticket as an attachment, and the result to your Slack channel. We keep these records while the app is installed. After you uninstall it, email [email protected] and we will delete everything we hold for your site within 30 days.

Our Bitbucket app (QA)

When your Bitbucket workspace admin installs the QA app, we keep the same kind of records as above for your workspace: its ID and name, a short lived access token from Atlassian (it expires within 4 hours), the settings your admin enters, Slack if you connect it, and each test (the repository, the pull request number and title, who pressed the button, the result and links to it).

When a test runs, we read that pull request (its title, description, commits and code changes) and make a temporary copy of the repository on our own computer, so the tester can find the pages and conditions the change touches. The copy is read only and is deleted when the test ends. The result goes back to the pull request as a comment, with a private report page (screenshots and a short video) on fireyourqa.com at an address only you get, which search engines are told not to index.

Jira, if you connect it (optional). We keep the Jira site you picked and the access tokens Atlassian gives us to read it. QA only reads: when a pull request names a ticket in its branch name or title, we read that ticket's title, description and recent comments to check the change against it. We never change anything in Jira. Disconnecting Jira in the QA settings deletes the tokens, and you can also remove access at any time from your Atlassian account (Profile, Connected apps).

We keep these records while the app is installed. After you uninstall it, email [email protected] and we will delete everything we hold for your workspace within 30 days.

Who we share data with

We do not sell personal data. We use a small number of service providers to run the service, for example hosting, email and the AI model providers that power test runs. Each customer agreement lists the providers used for that customer.

Your rights

You can ask us for a copy of your data, ask us to correct it or ask us to delete it. Email [email protected] and we will reply within 30 days.