Privacy and Terms of Use

Last updated 2 October 2026.

Privacy

What is stored

Your account details — name, e-mail address, and the optional contact fields you fill in — and everything you enter into the tool: teams, projects, versions, bug reports, comments, message-board posts and replies, test plans, test cases and test results, together with any screenshots, logs or other files you attach to a bug.

When a team admin invites someone, we store the address they typed so the invitation can be honoured when that person registers. If they never do, the invitation is deleted automatically after 90 days. The link in an invitation email is stored only as a one-way hash, so a copy of our database cannot be used to accept invitations.

Bug reports and attachments often contain more than intended. A screenshot of an application under test may show a real customer's name, an account number, or an internal URL. Before you attach a file, consider whether it needs to be there, and prefer test data over live data.

Who can see it

Everything belongs to a team. Only members of that team can read its projects, bugs, plans and runs, and what each member may change is set by their role in that team. Site administrators can reach the underlying records for support and maintenance.

The AI features

Four features send content to a third-party AI service (Anthropic) to draft a bug report, suggest duplicates, draft a test plan, or summarise a version's readiness. What is sent is only what that feature needs — the note you typed, the bug summaries in that project, your project description, or the counts and titles from the runs and bugs on a version. Attachments are never sent. Nothing is sent unless you press the button that starts it, and no AI feature writes to your records: every one ends at a review screen where a person saves it.

We record the date, the feature used and the size of each AI request so that usage limits can be enforced and the cost is visible. The content of the request is not kept in that record.

Cookies

One session cookie keeps you signed in. There is no advertising or cross-site tracking on this site.

Keeping and deleting

Records stay until they are deleted. Removing someone from a team removes their access; the bugs they raised and the results they recorded stay on the project, because a test record that changes when someone leaves is not a record. To have an account and its personal details removed, write to us at the address below.

Terms of use

Your account

Accounts are approved by an administrator before they can be used. Keep your password to yourself; you are responsible for what is done through your account. Tell us promptly if you think someone else has access to it.

What you may not do

Do not upload malicious files, attempt to reach another team's data, or use the tool to store material you have no right to hold. Do not use it to track defects in a way intended to harass or expose an individual.

What this tool is and is not

QATestLog records what your team enters and reports it back. A readiness summary, a suggested duplicate and a drafted plan are aids to a decision, not the decision — whether to release software remains your judgement and your responsibility. The service is provided as it stands, without warranty, and we are not liable for losses arising from a release decision, from data entered into it, or from an interruption to the service. Keep your own copy of anything you cannot afford to lose.

Changes

If these terms change materially, the date at the top of this page changes with them.

Contact

Questions about this statement, or a request to remove an account: info@qatestlog.com.