Client Status Snapshot for Jira

Privacy Policy

Last updated: 2 September 2026

Provider: Client Status Snapshot is an Aigeeza Apps product, operated by Chris May trading as Aigeeza.

Privacy contact: [email protected]

1. Scope

This policy explains how Client Status Snapshot processes information when used in Jira Cloud. The app runs on Atlassian Forge and provides a full Jira Apps page and dashboard gadget. Atlassian operates Jira Cloud and Forge; Aigeeza Apps is responsible for the app and this policy. The app is not produced by Atlassian.

2. Information accessed

The app requests only information needed to create the report:

InformationPurposeStored by the app?
Jira project ID, key and nameLet the signed-in user choose an accessible project and label the reportNo
Issue summaryDescribe work in the reportNo
Status and status categoryClassify completed, active and blocked workNo
Due dateIdentify overdue and upcoming workNo
Updated dateIdentify stale or attention-worthy workNo
Resolution dateInclude recently completed workNo
Optional executive summary entered by the userAdd context to the reviewed reportNo; browser memory only until refresh or navigation

The app does not request issue descriptions, comments, attachments, worklogs, people fields, custom fields, issue keys, credentials or Jira write access.

3. Processing and permissions

Jira requests are made through Forge as the signed-in user. Jira applies that user’s existing permissions. The app uses the returned fields to classify work and construct the visible report in the user’s browser.

The app requests only read:jira-work. It does not request Forge storage, Jira write, personal-data reporting, remote or external-egress permissions.

4. Storage and retention

Client Status Snapshot has no app database and does not persist Jira report data, project selections, reporting periods or executive summaries. Reloading the app reconstructs the view from Jira and resets browser-only inputs.

Because the app stores no End User Data, it has no app-controlled retention period and no stored report data to delete after uninstall. Jira and Atlassian-controlled platform data remain governed by Atlassian and the customer’s own Jira configuration.

5. External services and sharing

The app has no developer-operated backend, remote API, analytics service, advertising service, AI provider or external database. It declares no external egress and does not send Jira data to Aigeeza Apps or developer-selected third parties.

When a user selects Copy report, the displayed text is written to the user’s clipboard. When a user selects Print / save as PDF, the browser’s print interface opens. The user decides whether and where to paste, save or send the exported content. After export, that content is governed by the chosen destination and the customer’s policies.

The provider does not sell End User Data.

6. Logs

The app is designed not to log issue content, report text, executive summaries, credentials, tokens or secrets. Operational failures may appear in Atlassian-hosted Forge logs. The production release process includes verification that error handling does not log Jira response bodies or unnecessary End User Data.

7. Cookies and browser storage

The app code does not set cookies or use localStorage, sessionStorage or IndexedDB. Atlassian may use cookies and related technologies to operate Jira Cloud and Forge under Atlassian’s policies.

8. Security

The app relies on Forge authentication, tenant isolation and Jira permission checks. It does not collect passwords, personal access tokens or third-party credentials. Aigeeza Apps is responsible for secure app code, dependency maintenance, vulnerability handling and accurate disclosures.

Report suspected security issues privately to [email protected]. Do not include passwords, tokens or unnecessary customer information.

9. Individual rights and legal roles

Depending on applicable law, individuals may have rights concerning personal data. Requests may be sent to [email protected]. Because Jira data remains in the customer’s Atlassian product and the app stores no End User Data, requests concerning Jira records will normally need to be handled by the Jira customer or Atlassian.

Where UK data protection law applies, individuals may also complain to the UK Information Commissioner’s Office at https://ico.org.uk/. As the app stores no End User Data and operates no developer backend, personal data held directly by Aigeeza in connection with the app is limited to any details a person chooses to include when contacting support.

10. Children

Client Status Snapshot is a business productivity app for customer-managed Jira Cloud sites and is not directed to children.

11. Changes

Material changes will be published at this permanent privacy-policy URL with an updated effective date. Previous versions will be retained where legally required or operationally appropriate.

12. Contact