StatusPath Reports Privacy Policy

Scope

This Policy applies to StatusPath Reports - Time in Status for Jira, BlueGrove Labs product documentation for the app, and support requests submitted to BlueGrove Labs.

This Policy does not apply to Jira Cloud, Atlassian Marketplace, or other Atlassian products themselves. Your use of those services is governed by Atlassian terms, privacy policies, and administrator controls.

Information the app accesses

StatusPath Reports accesses Jira Cloud data only as needed to provide reporting features. Access depends on the app installation scopes, Jira permissions, and the current Jira context.

Depending on the report setup, the app may access Jira issue metadata such as issue key, summary, issue type, status, priority, resolution, created date, updated date, resolved date, project, parent, assignee, reporter, avatars, and selected issue fields included in a report.

The app may access Jira changelog and transition history for status and assignee changes to calculate time in status, time in assignee, status counts, status entry dates, and transition counts.

The app may also access project, saved filter, JQL, sprint, epic, board, status, field, and Jira user lookup data used to define report scope, configure columns, group average reports, or label report output.

Dashboard Gadget uses Jira dashboard item properties to read and save gadget configuration for the dashboard item.

• Users can only report on Jira data that their Jira permissions allow them to access.
• The app does not grant access to Jira work items, fields, projects, filters, boards, sprints, epics, or dashboards that Jira does not make available to the current user or app context.

Information we store

StatusPath Reports is built on Atlassian Forge. When running in Jira Cloud, app configuration may be stored using Atlassian-hosted Forge storage and Jira dashboard item properties where applicable.

The app may store saved report definitions and report configuration, saved report names, default saved report selection, owner account id for saved report creation, recent setup, active draft or dirty saved setup, admin settings, project settings, work calendars, business hours, calendar exceptions, duration format, issue limits, column selections, status column order, status groups, table filters and sorts, average report grouping, chart settings, time-between-status metric settings, and dashboard gadget settings.

Some browser-local storage may be used for local demo or mock mode, language preference, and temporary diagnostic flags. Production Jira app configuration is intended to use Atlassian Forge storage or Jira dashboard item properties rather than a BlueGrove Labs-hosted external reporting database.

Information we do not intentionally store

We do not intentionally store generated report rows, exported CSV/XLSX files, exported chart images, or complete Jira changelog snapshots as long-term records.

Report data is processed to generate the requested table, chart, issue activity view, dashboard gadget view, or export. Current report calculations run in the browser frontend, and export files are generated for the user action.

Website, documentation, and support information

BlueGrove Labs public documentation is informational and is separate from Jira report processing. The current public website has no product account system, customer report database, or CMS for Jira report data.

If you contact us for support, we may receive your name, email address, company or Atlassian site name if provided, support request content, report settings, screenshots, logs, error messages, diagnostic details, and Jira site context that you choose to share.

We use support information to respond to requests, troubleshoot issues, improve the app, maintain service quality, and handle security or privacy requests.

How we use information

We use information to generate workflow reports, calculate time in status and time in assignee, count status entries and transitions, render chart results, provide issue activity and dashboard gadget functionality, save and restore report configurations, and generate CSV/XLSX exports when requested by the user.

We also use information to provide support, troubleshoot issues, maintain app security and reliability, meet operational or compliance needs, and improve product quality.

We do not sell customer data. We do not use Jira data for advertising.

Sharing and subprocessors

We do not sell, rent, or trade customer data.

We may share or process information with Atlassian as required for Forge hosting, Jira Cloud APIs, Atlassian Marketplace licensing, billing, authentication, authorization, storage, logs, and app operation.

We may also share or process information with service providers used for customer support, security investigation, operational communications, or legal compliance, and with authorities or third parties where required by law, legal process, or to protect rights, safety, and security.

Where the app runs on Atlassian Forge, Atlassian provides the underlying hosted compute, storage, security, and data processing infrastructure under Atlassian Forge terms, data processing terms, and trust documentation.

Data location

StatusPath Reports is designed to use Atlassian Forge hosted compute and storage for app functionality. Data processed by Atlassian Forge may be stored and processed in locations used by Atlassian and its subprocessors, subject to Atlassian terms and data residency capabilities.

Support communications may be processed through BlueGrove Labs support channels and related service providers.

Data retention and deletion

App configuration data may be retained while the app remains installed or while the configuration is needed to provide the product feature, unless it is deleted earlier by an administrator, by the user where supported, or upon a valid deletion request.

Saved reports store configuration. They are not frozen copies of Jira result rows, Jira changelog history, or downloaded export files.

Support records and related diagnostic information may be retained only as long as needed to provide support, maintain business records, resolve disputes, comply with legal obligations, and maintain security.

When the app is uninstalled or when we receive a valid deletion request, we will take reasonable steps to delete or de-identify personal data that we control, subject to legal, security, backup, operational, and technical limitations. Some platform-retained data may be governed by Atlassian controls and retention behavior.

Security

We use reasonable technical and organizational measures to protect information processed by the app.

StatusPath Reports is built for Jira Cloud and Atlassian Forge. The app uses Atlassian authentication, authorization, and Jira permission models, and is designed to request only the permissions needed for its reporting features.

No method of transmission or storage is completely secure. If you believe there is a security issue, contact us immediately.

International transfers

Information may be processed in countries other than your country of residence. Where required, we rely on appropriate safeguards for international transfers, including those provided by Atlassian and our service providers.

Your rights and choices

Depending on your location, you may have rights to access, correct, export, restrict, or delete personal data.

Jira administrators control app installation, app access, project permissions, work item security, filter sharing, dashboard sharing, and Jira field visibility. Users choose which report scopes, fields, saved reports, exports, screenshots, and support details they create or share.

Customers can uninstall the app through Atlassian Marketplace or Jira administration. We may need to verify your identity and your relationship to the relevant Atlassian site before fulfilling a privacy request.

Customer responsibilities

Customers and site administrators are responsible for managing Jira users and permissions, controlling which users can access the app, deciding what Jira data is included in reports, managing saved reports and configurations created by their users, and ensuring that their use of the app complies with their own internal policies and applicable laws.

Children’s privacy

StatusPath Reports is intended for business use and is not directed to children.

Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the “Last updated” date and, where appropriate, provide additional notice.

Contact

Privacy questions, access requests, correction requests, deletion requests, and security concerns can be sent to support@bluegrovelabs.com. Include your Jira site URL, organization name, product name, and enough context for us to identify the request.

Product support should use the support portal when available.