Effective September 6, 2026

Privacy Policy

This policy explains how BonfireTech LLC handles information for Qiyasly, including the Qiyasly Chrome extension for Azure DevOps Server time tracking.

Information the extension handles

• Your Qiyasly email address and authentication tokens.
• The HTTPS origin of the Azure DevOps Server you choose to authorize.
• Azure DevOps work-item metadata needed for time tracking: ID, type, title, project, and organization or collection name.
• Your timer actions and the resulting time entries.

Your password is transmitted over HTTPS to Qiyasly only when you sign in. The extension does not store your password. It stores authentication tokens and your selected server origin in Chrome local storage so your signed-in session and configuration can persist.

How we use information

We use this information only to authenticate your account, place the Qiyasly timer on the Azure DevOps work-item page you authorized, start or stop timers, and show the active timer state in Qiyasly. We do not use extension data for advertising or sell it.

Sharing and retention

Information is shared only with service providers needed to operate and secure Qiyasly, when required by law, or as part of a corporate transaction subject to appropriate safeguards. Time entries follow your organization's Qiyasly retention settings. Removing the extension clears extension-local data; account data can be managed through Qiyasly or by contacting support.

Security and limited use

Personal and sensitive information is transmitted using HTTPS. Extension access is requested only for the Azure DevOps Server origin you enter. Qiyasly's use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Your choices

You can sign out to remove local authentication tokens, revoke the extension's site permission in Chrome, or uninstall the extension. For access, correction, or deletion requests, email support@qiyasly.com.

Changes

We may update this policy as Qiyasly changes. We will publish revisions on this page and update the effective date.