Time color for JiraPrivacy policy
Time color for Jira ("the extension") is an independently developed Chrome extension and is not affiliated with Atlassian. This policy explains what data the extension handles, where it is kept, and how to delete it.
In short
- The extension has no developer server. It never sends your Jira issue data to the developer, and it has no tracking or analytics.
- Jira issue data is read, calculated and displayed only in your browser.
- Site settings and color preferences sync through Chrome to your other computers. Issue data does not.
- The extension only connects to the Jira site you are using and never to any other website. Holidays come from your Jira admin, in a configuration file or in the Jira project settings.
1. Data the extension handles
1.1 Jira issue data
The extension only runs on project Timelines on Jira Cloud (*.atlassian.net); it does not run on Confluence pages. When you open a Timeline, it uses your browser's current Jira sign-in to read, from the same Jira site, the project ID and any settings your admin saved in the project (project property time-color-for-jira; skipped if absent). Only when settings exist (project settings or a configuration file you imported) does it read the data needed for display:
- Issue type, summary, status, start date, due date and issue links
- Values of the custom fields named in the admin configuration
- The site's lists of fields, issue types and link types (to check that the settings are usable)
- The project ID and project settings (to decide which settings apply)
This data is cached only in that tab's memory, with size and time limits. It is not written to the extension's storage and does not sync through Chrome. It is cleared when you close the tab, disable the extension, or reload data from the settings page. What you can see depends entirely on your Jira account's permissions. The extension never modifies any Jira data.
1.2 Account identification
To tell whether you are signed in and whether you switched Jira accounts (so one account's cached data is never shown to the next), the extension asks Jira for the current user. It keeps only the account ID, in memory. The ID is not stored, synced or sent anywhere else.
1.3 Sign-in credentials
The extension never reads, asks for or stores your Jira password, API tokens or cookies. Your browser attaches your current sign-in to requests to Jira automatically.
1.4 Settings and preferences
The following settings are kept in Chrome extension storage:
- Jira site URL and project scope
- IDs and display rules for issue types, custom fields and link types
- Holidays and make-up workdays (when included in a configuration file)
- Colors, display switches and the floating toolbar's position
If Chrome sync is on, these settings sync through Google's Chrome sync to other computers signed in to the same account, and Google handles them under its own privacy policy. Note that site URLs and field settings may reveal which organization you belong to.
The following stay on this computer only and do not sync: unsaved import drafts and one backup of the previous admin configuration. Settings read from a Jira project are used only in that tab's memory and are never stored.
1.5 Configuration generator for admins
"Create configuration (admin)" on the settings page processes what you type only within that page. It does not connect to Jira, upload anything or store anything, and it is cleared when you close the page. You keep the downloaded file yourself. If you click one of the page's links for finding IDs, Jira opens in a new tab with that tab's sign-in.
2. Data sharing
The extension does not sell, rent or share your data. Data only goes to the parties below, and only because the features need it:
| Recipient | What | Why |
|---|---|---|
| The Jira Cloud site you are using (Atlassian) | Read-only requests to that same site | To read the issue data to display |
| Google Chrome sync | Settings and preferences (no issue data) | To sync to your other computers, according to your Chrome sync settings |
3. Retention and deletion
- Cached issue data: cleared when you close the tab, or with Manage settings → Backup and more → Reload data in open Jira tabs.
- Site settings: click "Remove this site" in Manage settings.
- Colors and switches: click "Reset my preferences" in the extension panel.
- Everything: remove the extension on Chrome's extensions page; its data on this computer is deleted with it. When synced settings on your other computers are deleted depends on Chrome sync.
4. Chrome Web Store User Data Policy
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the extension's features, never for advertising, never sold, and never made available to anyone without your consent.
5. Changes to this policy
When anything changes, this page is updated along with the "Last updated" date above. Significant changes are also noted in the extension's release notes.
6. Contact
For any question about this policy, please open an issue on this project's GitHub pageplease open a GitHub issue. Please don't include issue titles, people's names, company site URLs or unredacted screenshots in your report.