Privacy policy

Release Views for Jira

Information the app reads

The app reads the Jira data available to the signed-in user and needed for the selected views, columns, charts and settings. This can include space/project names and avatars; release names, dates, descriptions and approvals; work item keys, summaries, descriptions, statuses, estimates, configured custom fields, child items and linked items; and user account IDs and visible profile information such as display names and avatars. Configured fields can contain personal or confidential information entered into Jira.

Jira permissions apply to each viewer. Sharing a saved view does not grant access to Jira work items the viewer cannot otherwise read. The app uses read permissions for Jira content and does not change your native Jira releases or work items.

Information the app stores

The app stores saved view names, scopes and JQL, chart and column settings, Release Sets, sharing and ownership references, owner/sharing display labels, personal table layouts and temporary report data in Atlassian Forge storage for the installation. Your browser may remember your last selected view using local storage tied to your account and site.

Cached ticket user objects retain account IDs rather than raw profile names, email addresses or avatars. Visible profile details are obtained from Jira when loading reports. Jira text and custom-field content may still contain personal information. The app also stores account IDs and retrieval/reporting timestamps for Atlassian's personal-data reporting and cleanup process.

How information is used and shared

We use this information to display reports, apply permissions, remember settings, export the results you request, maintain the app and respond to privacy instructions. Operational logs record counts, timings, quota information and diagnostic errors; app logging is designed to exclude ticket content and user profile details.

The app runs on Atlassian Forge. Its current configuration does not send Jira report data to an RGBIQ server, advertising service, external analytics service or AI provider. Account IDs and retrieval timestamps are reported to Atlassian's personal-data service so it can instruct the app to erase or refresh stored information. People with authorized developer or administrative access may access app diagnostics or stored data when necessary to operate the service or investigate a request. Users you authorize can see shared views subject to Jira and app permissions.

Opening RGBIQ support or privacy links takes you to our website. The support link includes the app name; it does not automatically attach your Jira tickets or profile. CSV files are downloaded to your device and become subject to your organization's handling of those files.

Storage, retention and deletion

Jira administrators can open More View Options → Data and Privacy to clear cached report data or remove a selected user's stored profile labels. Cleanup invalidates old loading sessions. It preserves Jira content, saved view configurations and ownership/sharing permissions. Removing a label is not full account anonymization. Requests concerning personal information in free-form saved view text, Jira content or associated settings need individual review.

An hourly privacy maintenance job processes Atlassian's instructions and retries unfinished cleanup. The default account reporting interval is seven days, unless Atlassian supplies a different interval. Cleanup can temporarily pause report loading. Information already displayed in another browser or downloaded by a user cannot be recalled by the app.

Forge-hosted app storage uses Atlassian's hosting and data residency capabilities. Atlassian controls its own platform logs, recovery copies, backups and uninstall retention. Deletion from the app does not promise immediate removal of every platform-retained copy. See Atlassian's Forge storage lifecycle. Contact us before uninstalling if you need assistance with an app-data request.

Website, support and service providers

When you contact RGBIQ, we receive your email address, message, topic and any optional name, company, phone number or application details you provide. We use them to respond, provide support, discuss requested services and keep relevant correspondence. Please do not send passwords, API tokens or unnecessary sensitive Jira information.

The website is hosted through Amazon Web Services. Submitted messages are stored in our AWS support database in US East (N. Virginia), and AWS email delivery sends notifications to our Google Workspace support mailbox. Support database records are scheduled to expire after 90 days. Email copies are managed separately and retained while needed for support and related business records; the database expiry does not automatically delete mailbox copies. Hosting and email providers may process information in other countries under their service arrangements.

Hosting services process network and browser request information to deliver the website and protect it from abuse. The contact service uses salted hashes of source IP addresses for rate limiting; these counters are scheduled to expire after two hours. Its diagnostic logs are configured for 14-day retention and are designed not to include submitted message content. Database expiry and backup removal are subject to AWS processing and retention.

The website does not use advertising or analytics trackers. It currently loads fonts from Google Fonts, which causes your browser to contact Google's font services. Provider privacy practices are described by AWS and Google. The app's Forge storage and the website's support systems are separate.

We do not sell personal information, use Jira data for advertising, or use it to train an AI model. We may disclose information when needed to provide the services described here, comply with applicable law, protect the service, or follow your organization's instructions. If a new purpose requires consent, we will request it separately.

Our roles and international processing

For customer-directed Jira reports and technical support evidence, RGBIQ processes information on the customer’s instructions. For independent business inquiries, customer relationships and service administration, RGBIQ determines the purposes of processing. Where applicable, our controller processing relies on legitimate interests in operating and protecting the business and responding to requests, performing applicable contracts, complying with legal obligations, or consent where required.

The founder provides support and administration from the United States. Forge residency for hosted app storage does not mean every platform operation or support activity remains within the EEA. Where required, applicable contractual safeguards, including Standard Contractual Clauses and regional adaptations, govern covered transfers. See the customer DPA and provider list for their scope; vendor arrangements do not constitute a separate RGBIQ certification.

Squarespace registers the domain and resells our Google Workspace subscription; its reseller administrative access is enabled. This is separate from Forge app operation. Our provider list describes the app and support services.

Your choices and privacy requests

You can choose what to include in a saved view, change its sharing, clear browser storage, download reports and ask your Jira administrator about access or app removal. Reducing a view's scope does not itself erase every existing cache record; cache expiry and administrator cleanup govern stored report data.

Depending on applicable law, you may have rights to access, correct or delete personal information, restrict or object to processing, receive a portable copy, withdraw consent where it is used, or complain to a relevant privacy authority. To make a request, email support@rgbiq.com with the subject “Privacy request.” Tell us the product and Jira site involved and what you would like to request. Do not include credentials.

We may need to verify your identity and coordinate with your organization's administrator. For information controlled by your organization in Jira, start with that administrator; we can help with app-stored information. Some account references or records may need to be retained for access control, legal obligations or resolving disputes. We will explain applicable limits when responding. The applicable customer DPA provides additional terms for covered customer personal data.

Contact and updates

RGBIQ is operated by RGB Brands LLC DBA RGBIQ, a Florida, United States company, at 12404 Kelly Place, Thonotosassa, FL 33592, United States. Contact the founder responsible for privacy at support@rgbiq.com. For suspected vulnerabilities, use our security reporting instructions.

We will update the date on this page when our practices change and provide additional notice when required. This policy describes RGBIQ Release Views for Jira and this website; other products or separately agreed consulting work may have additional notices.