Security Policy Effective Date: February 16, 2026 1. Introduction This Security Policy describes how the Timelapse for Jira app (the "App") handles security when used in Jira Cloud. 2. Hosting and Infrastructure The App runs entirely on Atlassian Forge infrastructure. No separate hosting or servers are used. 3. Data Handling Overview The App stores app configuration, tracker definitions, and snapshot metadata in Forge storage. Snapshot data consists of issue metadata only (for example: issue key, status, labels, and optional summary) and does not include issue bodies or attachments. The App does not write data back to Jira. 4. Logs and Diagnostics The App writes operational logs to Forge logging facilities. Logs are designed to exclude issue content and other personal data. Optional diagnostics record timings and counts, not issue content. 5. Data Egress The App does not send data to external services. CSV exports are generated in-app and delivered to the user directly. 6. Security Measures All communication between the App and Atlassian APIs uses TLS. Access to data is scoped by Atlassian permissions and Forge app scopes. The App follows least-privilege access and requests only required Jira scopes. 7. Incident Response We investigate and remediate security issues promptly. If an issue impacts customer data, we will notify affected customers and Atlassian as required. 8. Customer Responsibilities Customers are responsible for managing Jira permissions and ensuring appropriate access controls within their Atlassian site. 9. Contact Information If you have any questions about this Security Policy, please contact us at sergey@trophyapps.com.