Scope
This policy covers all Atlassian Marketplace apps published by KeulTech, Andreas Keul: "Dependency Guard", "Component Archiver", "Project Archiver" and "Chat Relay: Google Chat Notifications for Jira".
Architecture and data handling
All our apps are built on Atlassian Forge and run on Atlassian-operated infrastructure. We operate no servers, databases or log stores of our own and use no sub-processors. Persistent data is limited to Forge storage on the Atlassian platform. What each app reads and stores is documented in our Privacy Policy.
Dependency Guard, Component Archiver and Project Archiver declare no outbound network access. Their data never leaves the Atlassian platform.
Chat Relay has exactly one declared outbound destination: https://chat.googleapis.com. It sends the work item fields shown in a notification card only to the Google Chat incoming webhooks that the customer’s Jira administrators (team spaces) or individual users (their personal space) have configured. Webhook URLs act as shared secrets: they are accepted only if they point to Google Chat, are kept in Forge secret storage and are never returned to the browser after saving. Before a personal notification is sent, the app checks that the recipient is allowed to view the work item.
Encryption
All traffic between Jira, the Forge platform and Google Chat uses HTTPS (TLS). Data in Forge storage is held on Atlassian’s platform, which encrypts it at rest. We do not hold copies of customer data elsewhere.
Access control
KeulTech has no runtime access to customer data. There is no provider-operated database, log store, or administrative console holding customer data. Development and deployment access is limited to the sole proprietor’s own Atlassian account, which is protected by a unique password and two-factor authentication.
Permissions
Our apps request the minimum Atlassian scopes required to function, and these are declared in the app manifest and visible to administrators before installation. Where an app acts in a user-facing context, it performs API calls under the requesting user’s own identity, so existing permissions are enforced.
Vulnerability management
Before every deployment we run the Forge linter and a dependency audit (npm audit). Reported vulnerabilities in dependencies are fixed or overridden before a new version is deployed. Apps request no scopes beyond what their features need, and scope changes are only released as a new major version that administrators must approve.
Certifications
KeulTech is a one-person business and holds no formal security certifications such as SOC 2 or ISO 27001. Our apps rely on the security controls of Atlassian’s Forge platform.
Reporting a vulnerability
Email info@keul.tech with "SECURITY" in the subject line. Please include the affected app, a description of the issue, and steps to reproduce it.
- We acknowledge reports within one business day.
- We aim to provide an assessment within five business days.
- We will keep you informed until the issue is resolved, and will credit you if you wish.
Please do not publicly disclose a vulnerability before we have had a chance to address it. We will not pursue legal action against researchers who report issues in good faith and do not access, modify, or destroy customer data.
Patching
Security fixes are deployed as a new app version through the Atlassian Marketplace. Because our apps run on Forge, updates reach all installations without customer action.
Incident notification
If an incident affects customer data, we will notify affected customers and report the incident to Atlassian through the Marketplace partner incident process.