Closed Platform Access QAwork is a private, closed platform. It is not open for public registration. Users can access the system only when they have been approved and assigned to a project by the platform owner, a super admin, or a project administrator.

Account And Access Data QAwork stores account details needed to identify approved users, such as name, email, login credentials where applicable, Google sign-in identity where used, account role, project membership, active/inactive status, and super admin or project admin permissions.

Project And QA Data The platform stores project data such as project names, slugs, team access, checklist structure, scenarios, tests, descriptions, expected results, priorities, risks, environments, test execution statuses, assignees, last-changed labels, planning runs, Jira or documentation links, analytics settings, report data, uploaded sprint/chart images, and export-related records.

AI Wizard And Draft Data QAwork includes AI-assisted checklist drafting. The AI wizard may use information entered by admins to suggest checklist names, scenarios, test titles, descriptions, expected results, negative checks, priorities, and related structure. AI output is a draft and should be reviewed before publishing.

AI Usage, Test Finder, And Limits QAwork may store AI usage counters at the project level, AI request metadata, and the prompts or descriptions users submit for AI-assisted tools such as checklist creation, issue drafting, and Find Test with AI. AI usage can be limited for a project, and those limits may be reviewed or adjusted by project admins, super admins, or QAwork administration.

Issues, Comments, Notifications, And Attachments QAwork stores internal bug/task issues, linked Jira references, issue comments, uploaded attachments, author labels, edit/delete metadata, notification records, and read/unread status so teams can track follow-up work against the exact test where it was found.

Profile Avatar And Account Settings Users may upload an avatar in Account Settings. If an avatar is uploaded, QAwork stores the file and uses it in permitted account, issue, and comment views. If no avatar is uploaded, the interface may show initials instead.

Jira Integration Settings If a project admin enables Jira integration, QAwork may store the Jira base URL, Jira auth email, saved API token state, project keys, issue type for metrics, solved-status names, synced status results, and Jira chart snapshots. Jira sync reads Jira data for configured projects and does not require QAwork to create Jira tickets automatically.

Google Sign-In If Google sign-in is enabled, QAwork uses the Google account identity returned by Google, such as email and basic profile identity, only to match the user with the approved access list. If the email is not approved for the closed platform, access is refused.

Uploads, Exports, And Reports QAwork may store uploaded sprint images, chart images, checklist files, generated report data, analytics summaries, Excel export data, and related metadata when those tools are used inside a project. These records belong to the project context where they were created.

Project Data Changes QAwork stores project data so approved users can run the workspace: checklists, scenarios, test cases, priorities, environment statuses, bugs, comments, team access, settings, references, uploads, reports, analytics, AI drafts, and related history. Users with the required project permissions may create, edit, rename, delete, move, export, or otherwise change this data. The project owner and project admins are responsible for controlling those permissions and for the effect those actions have inside their project.

Cookie Policy QAwork stores a login session cookie, a cookie-consent flag, and a small amount of local browser data. The login session can stay active for up to 3 days unless you sign out manually. Local browser storage may be used for accessibility preferences, saved AI wizard drafts, and saved manual checklist drafts so unfinished work can remain available in your browser.

What Is Not Stored In Cookies Published test results, analytics, checklists, scenarios, project access, and team settings are not stored inside cookies. Those records stay in the application database. Browser-side draft storage is only a convenience layer for unfinished inputs until you publish, clear, or replace them.

External Links And Third Parties Projects may contain Jira links, documentation links, Google Sheets links, external websites, uploaded files, and Google sign-in. QAwork may connect users to those resources, but external services remain governed by their own rules and availability.

Support Project And Buy Me A Coffee The Support Project page may link to Buy Me A Coffee. Opening that link is optional and takes you to an external third-party service under its own privacy and payment terms. Optional support helps QAwork cover hosting, maintenance, development, and AI infrastructure costs during launch, and it is not a hidden payment requirement for using the product.

Account Deletion Users may delete their own account from settings. Deleting an account removes the personal profile and project access, but project activity may remain to preserve reports and audit integrity. Historical records such as status changes, dates, test results, issue history, and comments may stay in the project as anonymized activity, with the user's name replaced by a neutral deleted_user label. If a user is the only admin of one or more projects, deletion may also remove projects that no longer have an active admin, after the required warning and confirmation flow.

Your Choices You can sign out to end the active session, clear cookies and local site data in your browser, manage accessibility preferences, delete drafts by clearing browser storage, or request access/help by contacting [email protected].