Privacy Policy

Last updated: 5 November 2026 · Version 2026-11-05

This policy covers the public QAwork website, enquiries, public demo and private test-management workspace. Wulf operates the service as an individual. For privacy questions or requests, contact [email protected].

Browsing and contacting me

You can view the website, demo and external-bug example without an account. Public examples contain sample data, not client projects. The landing page has no enquiry-submission form. If you contact me, I receive the information you choose to send, such as your name, contact details, correspondence and files.

Hosting may process IP addresses, browser information, requested URLs and request times to deliver pages, maintain security and investigate faults. The current public site has no visitor analytics or advertising trackers. Its images and icon library are served locally. I do not sell personal information or use this website for advertising profiling.

Accounts and invitation requests

Private access is invitation-only, whether you use Google or a password. A project Owner may submit a prospective participant's name, email and intended role. These details can be stored as an unapproved invitation request before that person activates an account. Wulf approves new email addresses. Project Owners should tell the person before requesting access and have authority to share their details.

Account records include email, display name, activation and approval status, assigned project roles, and a password hash when a password is set. Google sign-in adds the Google account identifier and uses a verified email. It requests identity information only, not Gmail messages. The system records the version and time of Terms acceptance when completed through activation or Google sign-in. Invitation tokens are stored as hashes; their links expire after seven days or after use. Expiration is not automatic deletion of the historical record.

Workspace content and who can see it

The workspace stores project and environment names, scenarios, test definitions, estimates, per-environment results, notes, bug descriptions, severity and priority, screenshots, external issue links, automation references, testing participants and timer records. Report exports contain selected project data; they are not full backups of all attachments.

Participants see only assigned projects. Within a project, Owners, Testers and Viewers can see its testing information according to their roles; Owners manage membership and Testers can edit and run tests. Wulf has administrator access, including in projects run independently by a customer's own team. This access supports administration, troubleshooting and any agreed testing.

For a self-managed project, the customer or project Owner decides what information to upload and who in the team needs access. Before uploading personal information about customers, employees or other people, agree the permitted data, responsibilities, recipients, safeguards and retention arrangements with Wulf. Do not assume that invitation approval is permission to upload any category of personal information. Prefer synthetic test data and remove credentials or unnecessary identifying details from screenshots.

Purposes and service providers

I use information to respond to requests, operate accounts and projects, provide support, prevent misuse and meet applicable recordkeeping duties. Optional saved accessibility settings depend on your preference choice; acknowledging the Privacy Policy is not blanket consent to unrelated processing.

Hosting, email, messaging and Google identity services process information needed for their functions. Clicking an external bug link or downloading and sharing an export can disclose information outside QAwork. A linked tracker has its own permissions and privacy rules; linking an issue does not automatically copy or synchronise its contents. People who already downloaded a report may retain a copy after their project access is removed.

Third-party providers may process information in countries other than yours. Before sharing information that requires specific location or contractual safeguards, ask Wulf to confirm the hosting and provider arrangements for your project. No particular hosting country or transfer safeguard is promised by this general notice.

AI and project information

The workspace includes an optional AI feature. If enabled for a project and configured by the operator, requests and relevant project context may be sent to the configured AI provider. Agree the permitted data and provider arrangements before enabling or using it.

Project owners should agree which information may be sent to an AI provider before enabling this feature. Any new data collection needs a review of this notice and any required choices before use.

Cookies and browser storage

Necessary workspace cookies support sign-in, security and invitation or Google sign-in flows. They are separate from optional preference storage. Choosing Necessary only does not disable the cookie needed to sign in. The public homepage does not check your workspace session.

Use Cookie settings to change the preference choice. Necessary only still lets you use the toolbar on the current page without saving those settings for later visits. Allow preferences does not enable advertising or analytics. If storage is blocked, controls work for the current page but choices may not persist. Clearing site data removes local choices and cookies, not server-side project records.

Retention, archiving and security

Enquiries and correspondence are kept while needed to respond, agree work, provide follow-up or address relevant legal or business records. Workspace accounts, acceptance records and project information are kept for operating the agreed service, support, handover and applicable recordkeeping or dispute needs. There is no automatic project-content deletion schedule in the current workspace. Agree a suitable project-specific retention period before sharing confidential or personal information.

Archiving or removing a member's access is not erasure of their historical activity or of project records. Ask Wulf about deletion, correction or a data handover. Retained backup copies and reports already exported by authorised recipients may have different removal arrangements; these need to be discussed rather than assumed.

Safeguards include password hashing, server-side permission checks, protected session cookies and sign-in rate limits. Failed sign-in attempts use a hashed email/IP key and timestamps; entries older than 24 hours are cleared during failed-login processing, and a successful password login clears that key's failures. Technical hosting-log retention depends on the actual deployment. No internet service or ordinary messaging channel can guarantee absolute security.

Privacy requests and changes

Email Wulf to ask about your information, request access or correction, or discuss deletion, restriction or another right available under applicable law. Identity or project authority may need to be verified. A team member can also contact their project Owner; that does not prevent contacting Wulf directly. Some information may need to remain for a lawful obligation, an active agreement or a dispute, and the reason should be explained. This service is not intended for children to submit personal information.

This notice describes the current service, not every possible future feature. Changes to providers, retention, analytics or integrations require review. For questions or concerns, contact [email protected].