App Usage for Jira · Lens
Privacy Policy
Effective September 29, 2026. This policy covers App Usage for Jira (Lens) and its support contact form, operated under the BrightNetworks brand.
What the app measures
Usage collection starts only when a Jira site administrator turns on Live Collection. A new installation starts with collection off. While on, the app records app and Jira route visits, session starts, timestamps, and estimated recent visit time. It uses Jira cloud and account identifiers to make a site-specific pseudonymous user hash. It processes URL pathnames, which can contain project or issue identifiers; query strings and URL fragments are excluded. The app does not intentionally collect issue descriptions or page contents.
Why and where data is processed
These measurements produce the site administrator’s app usage dashboard, including daily sessions, page views, and estimated unique visitors. Collection data is processed in Atlassian Forge and stored in Forge storage for the Jira installation. The dashboard shows aggregate results; it is available to Jira administrators with an active app license.
Retention and controls
Temporary tracking state and retry records are kept for up to seven days. Daily usage aggregates are removed after about 100 days by a daily cleanup task. Pending browser observations stay in the tab’s session storage until sent, the tab session ends, collection changes, or they become more than 23 hours old. App recognition settings and administrator layout preferences have no automatic expiry at present. A Jira administrator can turn Live Collection off at any time; this stops new collection but does not immediately erase existing aggregates.
Support contact information
If you use the contact form, we collect your name, email, selected topic, and message to answer your request. The form sends this information over HTTPS to the BrightNetworks administrator server through a private REST API. It is stored in the administrator database outside Atlassian Forge. Lens contact information is not sent to Slack. We do not use contact submissions for marketing. Contact submissions remain until deleted by the privacy officer or handled through a valid deletion request. The blog and administrator hosting providers may process technical request data under their own service terms.
Access and requests
Jira site administrators control collection and can access dashboard results. In the BrightNetworks administrator app, only the designated privacy officer, Sean, can access Lens contact submissions. Contact Sean at seiyon.kim@brightnetworks.kr or use the contact form and choose Privacy to ask about access, correction, or deletion of information associated with you or your Jira site. We will review the request and applicable obligations. Because usage is aggregated and account identifiers are hashed, we may need help from your Jira site administrator to locate relevant records.
Changes
We may update this policy when the product or data handling changes. The effective date above will change when a revised policy is published.