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:
- Authentication information: your configured Jira username, password or personal access token (PAT), authentication method, and Jira base URL. Credentials authenticate requests to your Jira instance.
- User-provided issue text and settings: summary, description, labels, components, assignee, custom fields, templates, and defaults. These may contain personal information.
- Website content: screenshots and annotations, tab video without audio, and optional page localStorage keys and values selected for an attachment. These can contain private content, personal information, or secrets.
- Browsing activity and diagnostics: captured page/request URLs, network requests and responses including headers and bodies, console warnings/errors, and exceptions during a log recording. These can contain credentials, personal information, and activity on the recorded tab.
- Optional description metadata: page URL, timestamp, and browser information. Automatic metadata inclusion defaults OFF for fresh settings; existing explicit settings are preserved. Review issue text before submitting.
- Local workflow state: drafts, recorded evidence, recent issue history (up to 20 entries), and suggestions (up to 12 entries).
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
- On first use of log or video recording, a visible in-popup disclosure explains what will be collected and that recording continues after the popup closes. You may select Remember my choice before clicking Start recording. That approval is stored locally, separately for logs and video, and permits subsequent Record clicks to start that feature without repeating the disclosure. Recording never starts automatically. Without a remembered approval, the disclosure appears on each start. Cancelling or closing the disclosure captures nothing and does not remember approval.
- Settings provides Reset recording approvals, which makes the next recording ask again. This does not stop an active recording, revoke browser permissions, or delete evidence. Material changes to a feature's disclosure or capture scope require renewed approval for that feature. Stop recording explicitly when finished.
- Recording and uploading are separate choices. Log/video attachment checkboxes default OFF for a new recording and preserve saved opt-outs. The popup shows recording details when a recording exists, and allows review/download of sanitized diagnostic JSON and preview/download of video.
- LocalStorage attachment defaults OFF and is not restored from drafts. You must request a snapshot, review its REDACTED contents in the popup, and choose which keys to include before attaching. Submission uses the reviewed snapshot; it does not silently recapture localStorage.
- Diagnostic redaction uses heuristics to mask credential fields in headers, bodies, URLs, console messages, and localStorage snapshots. Diagnostic data may also be truncated. Sanitization is not guaranteed to remove all credentials, secrets, or personal information. Review sanitized JSON and omit unsafe keys or evidence before sharing.
- Screenshots and videos can expose anything visible in the captured tab; do not assume diagnostic redaction sanitizes images or video.
Where data is stored
- Settings, credentials, optional versioned recording approvals, recent issue history, and suggestions are stored locally in
chrome.storage.local. Remembered approvals persist across browser restarts until reset or invalidated by a disclosure/scope change; they are not uploaded to Jira. This is local Chrome storage, not an encrypted credential vault. - Drafts and recordings use
chrome.storage.sessionwhere available, with achrome.storage.localfallback. Recordings remain until cleared/reset or until the browser session ends when session storage is used. Fallback local data can persist across browser restarts until explicitly cleared/reset. - Closing the popup does not stop recording or delete saved evidence. Clear/reset drafts and recordings when they are no longer needed. Local settings/history remain until removed or the extension's local data is deleted.
- Downloaded exports are separate files under your control and remain until you delete them. Jira issues and attachments are stored by your Jira instance according to its retention policies. Clearing extension data does not delete downloads or Jira data.
Where data is sent
- Jira API requests, including authentication, connection testing, issue creation, and selected evidence uploads, go only to the HTTPS Jira Server/Data Center base URL you configure. HTTP Jira URLs are rejected.
- Jira fetch redirects are rejected to avoid forwarding credentials or evidence to a redirected endpoint. Configure the final HTTPS base URL, including any context path.
- No captured data is sent to developer servers, analytics providers, or advertising services.
Data sharing
- The developer does not sell user data or share it for advertising or unrelated purposes.
- At your direction, issue content and selected evidence are shared with your configured Jira instance. Uploaded content is visible to users and administrators authorized under that Jira instance's access rules and is subject to its operator's policies.
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
storagestores settings and workflow data locally;activeTabprovides user-invoked access for active-tab capture. There is no mandatorytabspermission.- Optional
scriptingpermission is requested at runtime when you request a localStorage snapshot. debuggeris a required manifest permission because Chrome does not support it as an optional permission. It is used for network/console recording only after explicit in-popup consent. Installing or updating the extension does not itself start recording.tabCaptureandoffscreensupport tab-only video without audio, including continuing a recording after the popup closes.- Optional host access is requested for the configured Jira host on save/test so the extension can make Jira API requests. There is no default access to all websites.
User control
- You decide whether to capture evidence and which evidence to attach. Review issue text, sanitized diagnostic JSON, localStorage keys, screenshots, and video before uploading.
- You can stop recordings, clear/reset drafts and recorded evidence, and use Clear Credentials to remove the stored token/password.
- Clear Credentials does not revoke a Jira token or erase existing Jira issues or attachments. Revoke tokens through Jira and request removal of uploaded content through your Jira administrator or instance controls. Delete downloaded exports separately.
- You can revoke optional extension permissions through Chrome. Removing access does not erase content already uploaded to Jira.
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.