SLA & Time to Resolution Reports privacy
Product-specific data handling for SLA & Time to Resolution Reports, last updated 23 October 2026. This supplements the website privacy policy.
Where the application runs
The application runs on Atlassian Forge. Atlassian hosts its code and processes its requests. Atesen Software does not operate an external app server or report database. This is a hosting description, not a certification or trust-badge claim.
Data read for a report
- Accessible project key and name; request keys, creation timestamps, current priorities and issue types.
- Native SLA metric identifiers and names; cycle start and stop times, elapsed and goal durations, remaining time, breach outcomes, pause state and calendar-hours flags.
- The implementation does not request names, email addresses, comments or request descriptions for the report. Read access still processes Jira data and is limited by the signed-in user's permissions.
What it talks to
App reporting calls go to Jira through Forge asUser. The manifest configures one read-only scope, read:jira-work, with no external egress or remotes. There is no third-party reporting service or app analytics integration. Atlassian platform processing is governed separately.
Storage, retention and deletion
The app does not persist report data or calendar configuration in Forge storage, a database or an app cache. Report data is held transiently for requests and the page session. Local preview settings reset on reload.
There is no app-held report archive to delete or restore. Closing the page ends that page session; uninstalling does not delete files already downloaded to your device. Atlassian platform logs and retention are separate; this statement does not promise that Atlassian retains nothing.
Files you download
CSV and PDF are generated in your browser and saved when you choose to download. They include request keys and SLA metrics, cohort, metric selection and coverage information. You control the files and their sharing, retention and deletion after download. The app keeps no stored copy.
Support correspondence
Email you choose to send to support leaves Atlassian and is handled under the website privacy policy. Send only a sanitized description and necessary diagnostic context. Do not send report exports, customer request data, credentials, passwords or tokens.