Security Policy โ Funatic Labs apps for Jira Cloud
Effective date: November 2, 2026 ยท Provider: Funatic Illuminations, doing business as Funatic Labs
1. Scope. This policy covers our apps for Jira Cloud: Sprint History Search, Label Cleanup, Default Values, Bulk Link Changer, Blocked-By Close Guard, Release Date Search, Label Wildcard Search and Pinned Comments.
2. How the apps run. Every app is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. We run no servers of our own, use no remote back end and make no outbound calls (no egress), so customer data never leaves Atlassian. The apps hold no API keys or secrets and collect no credentials.
Reporting a security issue
Email support@funaticilluminations.com with the app name, your Jira site URL and steps to reproduce. Please do not share customer data in your report. We confirm receipt and triage within 24 hours.
Vulnerability management
- Finding issues: a dependency scan runs daily on every app, alongside Atlassian security reports and tickets, customer reports and review of app logs.
- Triage: each report is confirmed or dismissed and given a severity within 24 hours. Critical is CVSS 9.0 or higher, or any flaw that exposes another user's or site's data; High is CVSS 7.0โ8.9.
- Fixing and patching: fixes follow Atlassian's Security Bug Fix Policy for cloud apps: Critical within 10 days, High within 4 weeks, Medium within 12 weeks and Low within 25 weeks. Fixes are tested, deployed to a development environment first and then to production. Because the apps are hosted on Forge, a patch reaches every customer site without any action on your part.
- Dependencies: dependencies are kept to a minimum, scanned before every release and daily, and tracked in a software bill of materials for each release.
Incident handling
- Any event that may have exposed, changed or deleted customer data without permission is treated as a security incident.
- We triage within 24 hours, report a confirmed incident to Atlassian within 24 hours of becoming aware, and notify affected customers within 72 hours of confirming it, using Atlassian's incident communication guidelines.
- After a fix is deployed and verified, we write a post-incident review and update our controls. The incident plan is tested once a year.
Security controls
- Access control: admin features are limited to Jira administrators or the groups and roles they allow, and this is checked on the server on every request. User actions run with the user's own Jira permissions, and each app requests only the scopes it needs.
- Authentication: the apps use Atlassian's platform authentication only. Our developer, source-control and email accounts require multi-factor authentication and unique passwords, and access is reviewed regularly. Deployment tokens expire within 90 days and are revoked at once if exposure is suspected.
- Encryption: Atlassian encrypts all app data in transit (TLS) and at rest. Our source code backups are encrypted at rest, and development machines use full-disk encryption.
- Logging and monitoring: app logs hold only IDs, counts, event names and error codes, never issue content or personal data. Logs are checked daily for unusual errors and permission failures, and alerts are handled under our incident process.
- Infrastructure security: hosting, networking, storage and data residency are provided and secured by Atlassian. Every change is reviewed and must pass tests, lint and the dependency scan before release.
Changes. We may update this policy and will post the new version here with a new effective date.
Contact: support@funaticilluminations.com