Privacy policy

What stays in your browser

• Your tests, suites and settings are kept in the extension's storage in your browser profile.
• Screenshots taken while a test runs, and the evidence reports made from them, stay in your browser unless you download them yourself.
• If you don't sign in to a team, the extension sends nothing to us. Tests and suites that you don't share, and their runs, are never sent.

What is sent when you use a team

Signing in to a team, in the extension or here, stores on the team server:

• Your account: your name and email address, and either your password (kept only as a salted hash, never in readable form) or, if you sign in with Google, your Google account's identifier, name and email address.
• Your workspace: which workspace you are in and your role in it.
• Tests and suites you share: their names, base URL, screen size and steps. Steps hold what you put in them: the elements they use, the text they type (including any password a "Type text" step types) and files attached to upload steps. The server also keeps who changed a shared test last, and when.
• Runs of shared tests and suites: who ran them, when, how long they took, the test run they were part of, and for each step its description, whether it passed, its error message and its notes (such as a value saved to a variable). Screenshots are not sent.

Use test accounts and test data in tests you share: everyone in your workspace can read them.

What the extension can reach in your browser

• It can read and change the pages you test (on any site) so that it can let you pick elements and carry out a test's steps. It does this only while you build or run a test, in the tab you are testing.
• "Real input mode" uses Chrome's debugger to send real clicks and typing to that tab. It is off until you turn it on.
• It opens a sign-in window when you choose to sign in with Google.

It does not collect your browsing history, and it does not watch pages in the background.

Who can see your data

• The members of your workspace see its shared tests, suites and runs, and each other's names and email addresses.
• The people who run this team server can reach what is stored on it, and do so only to keep the service working. It is hosted on Vercel with a managed Postgres database; these providers process the data, and request details such as IP addresses, on our behalf.

We don't sell your data, show ads, or use analytics or tracking, and we don't use or pass on your data for anything other than providing QA Recorder.

Cookies

This dashboard sets one cookie that keeps you signed in, and a second one for the few minutes a Google sign-in takes. The extension uses no cookies.

Keeping and deleting data

• A sign-in ends when you sign out, and by itself after 90 days.
• Signing out of the extension removes the shared tests from your browser. The workspace owner can stop sharing or delete a test, which removes it from the workspace for everyone; runs already recorded stay in the workspace's history.
• Deleting a workspace, which its owner can do in the extension, deletes its shared tests, suites, runs and memberships.
• To have your account deleted, or to get a copy of what is stored about you, contact us.

Limited use

QA Recorder's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Changes and contact

When what QA Recorder sends or stores changes, this page changes with it, and the date at the top says when.

Questions or requests: epafroditus.kristian@gmail.com