test2task Privacy Policy

Last updated: 2026-11-16

Summary

test2task is a Chrome extension for user-directed evidence capture and Jira Server/Data Center issue creation. It processes data locally and sends issue content and selected evidence to the Jira instance you configure. It has no developer telemetry, analytics, or developer-operated data collection servers, and does not sell user data.

Data we collect and why

The extension handles the following information to provide its visible features:

This information is used to configure and test your Jira connection, capture and review evidence, maintain local workflow state, create issues, and attach the evidence you select. It is not used for advertising or unrelated profiling.

Capture, consent, and review

Where data is stored

Where data is sent

Data sharing

Chrome Web Store Limited Use

test2task's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the user-facing features described in this policy.

Public website and support

The public documentation site and support tracker are hosted by GitHub. When you visit them or submit a support issue, GitHub handles those interactions under the GitHub Privacy Statement, including standard website request information. The documentation pages contain no analytics scripts. The extension does not automatically send captured evidence or Jira credentials to this site or tracker. Support issues are public; share only synthetic or redacted information.

Permissions

User control

Changes to this policy

We may update this policy as the extension evolves. Changes will be reflected in this file.

Contact

For privacy questions or support, use the public test2task support tracker. The tracker is public: do not post credentials, personal information, private URLs, or confidential captured evidence. If a question needs sensitive details, first request a private contact channel without including those details in the issue.