// Serious Software, Bearishly Good

UrsaCorp Privacy Policies

This document provides information on Privacy Policy for PromptTree app, developed by URSACORP, LLC.Privacy Policy
Last Updated: July 10, 2025
We care about keeping your personal data private.PromptTree allows you to select folders and files and copy their contents together with your custom prompt.The information you put into the app is stored on your device and never shared with any third-parties or with us. PromptTree operates completely offline and requires no internet connection to function.We do not collect any analytics, tracking data, or usage statistics. Your files and prompts remain entirely private and under your control.For more information on data processing, or for data deletion requests, please contact us at: [email protected].


Privacy PolicyURSACORP LLC. Applies to our Atlassian Marketplace apps: Issue Aging Chart, Worklog Pivot, Sprint Countdown, and Epic Lens.Effective date: 2026-10-28How the apps workThe apps use Atlassian Forge to host their interfaces inside Jira. The interface runs in your browser and reads Jira data, such as issues, boards, sprints and worklogs, through Atlassian's APIs as the signed-in viewer. Jira checks that viewer's access permissions.Report calculations, grouping, filtering and CSV creation take place in the browser. Browser-based versions call Jira using the Forge bridge. Earlier versions of Worklog Pivot and Epic Lens also process Jira API responses in Atlassian-hosted Forge resolver functions. Both paths use the viewer's Jira permissions. The apps do not send Jira report content to a URSACORP server, use Forge Storage, or maintain an app database of that content.The app manifests contain no external egress permissions or remote services. We add no external analytics, tracking pixels or telemetry to the apps. We do not sell Jira data. This does not prevent you from downloading or sharing an export you have chosen to create.What stays on your deviceJira responses and calculated reports are held in the app page's browser memory. They are not saved by us as a separate copy of your Jira records. Jira's own records remain subject to your site's retention and access rules.Exports you trigger, such as Worklog Pivot CSV files, are generated in your browser and downloaded to your device. You decide where to save or share them and when to delete them. Small display preferences, such as collapsed groups in Epic Lens, may remain in browser local storage until you clear that storage. Issue Aging Chart and Sprint Countdown save the settings you choose in Jira's dashboard gadget configuration, not in a URSACORP database or Forge Storage.Installation, operational and support informationAtlassian makes installation details and operational usage metadata available to app vendors. This can include site or installation identifiers, installation status, dates, and platform usage or error counts. We use this information to operate and support the apps, understand adoption and review hosting usage. These platform records do not provide the content of your reports, confirm a completed report or CSV export, or measure every browser interaction. Browser requests do not generate app-resolver invocation metrics.We may retain operational records for those purposes. When sharing findings publicly, we use aggregate or de-identified summaries rather than customer site identifiers. We do not add a separate tracking service to replace platform metrics.If you contact us, we receive the email address and information you choose to send. Please do not include confidential Jira content, customer information or credentials in support messages. We use the correspondence to answer your request and maintain support records. Contact us about information you have sent or a deletion request at [email protected].Your Jira permissionsEvery Jira API request runs as the signed-in viewer. None of the apps requests write permission. The apps use these read-only scopes:Issue Aging Chart: read:jira-workWorklog Pivot: read:jira-workSprint Countdown: read:board-scope:jira-software, read:sprint:jira-software, read:issue-details:jira, read:jql:jira, read:project:jiraEpic Lens: read:board-scope:jira-software, read:sprint:jira-software, read:issue-details:jira, read:jql:jira, read:project:jira, read:audit-log:jira, read:avatar:jira, read:field-configuration:jira, read:issue-meta:jiraSprint Countdown and Epic Lens use granular scopes for Jira Software's agile APIs. Epic Lens's audit-log, avatar, field-configuration and issue-meta scopes are included for the enhanced issue-search endpoint. The app does not use them to read the audit log or perform a separate audit-log analysis.The documentation for each app explains its scopes. Moving Worklog Pivot and Epic Lens requests from Forge resolvers to the browser does not add scopes.Security and contactThe apps never ask for your Atlassian password, personal access token or other shared secret, and hold no customer credentials. Our security policy describes how we handle vulnerabilities and incidents. Browser execution and the absence of an app database do not make an application immune to security defects.Security reports: [email protected]Support and privacy questions: [email protected]Security policy: docs.ursacorp.org/securityIf app behavior changes in a way that affects this policy, we will update this page and its effective date before shipping that change.URSACORP LLC, Yerevan, Armenia