1. Data controller
KeulTech — Andreas Keul
Wildgansweg 4, 31535 Neustadt, Germany
Email: info@keul.tech · Phone: +49 173 639 0736
The controller is the natural or legal person who alone or jointly with others determines the purposes and means of the processing of personal data.
2. Hosting and server log files
This website is hosted by an external provider. The web server automatically collects and stores information in server log files, which your browser transmits automatically: browser type and version, operating system, referrer URL, host name of the accessing computer, time of the server request, and IP address. This data is not merged with other data sources. Processing is based on Art. 6(1)(f) GDPR — the operator has a legitimate interest in the technically error-free presentation and optimisation of the website.
3. Contact by email, telephone or fax
If you contact us, your enquiry and any personal data you provide will be stored for the purpose of processing your request and in case of follow-up questions. We do not pass this data on without your consent. Processing is based on Art. 6(1)(b) GDPR where the request relates to the performance of a contract, and otherwise on Art. 6(1)(f) GDPR. The data remains with us until you ask us to delete it or the purpose for storage ceases to apply. Mandatory statutory retention periods remain unaffected.
4. Google Fonts (local hosting)
This site uses Google Fonts, hosted locally. No connection to Google servers is established when you visit this site.
5. Your rights
You have the right to obtain information about the origin, recipients and purpose of your stored personal data free of charge at any time, and the right to have this data corrected or deleted. You may withdraw consent at any time with effect for the future. You also have the right to data portability and the right to lodge a complaint with the competent supervisory authority. For any of these, contact us at info@keul.tech.
6. Atlassian Marketplace app: "Dependency Guard for Jira"
This section describes data processing by our Atlassian Marketplace app, separately from the website above.
6.1 Nature of the app
Dependency Guard for Jira is a pure Atlassian Forge app. It runs entirely on Atlassian’s own infrastructure. It has no backend of its own, makes no outbound network connections, uses no external services, and engages no sub-processors. No data ever leaves the Atlassian platform.
6.2 Data the app reads
Within the Jira instance where it is installed, and only via the permissions granted at installation (read:jira-work), the app reads:
- issue links between issues,
- issue status and status category,
- issue summaries,
- the project identifier.
In user-facing contexts, these reads are performed under the requesting user’s own identity, so the user’s existing Jira permissions are enforced.
6.3 Data the app stores
The app uses only the Atlassian Forge Storage API (storage:app). It stores exactly two kinds of record:
| Record | Content | Retention |
|---|---|---|
| Project settings | Three configuration values: whether notifications are enabled, whether auto-guard is enabled, and the name of the blocker link type. Contains no personal data. | Until the app is uninstalled or the setting is changed |
| One-time override | The Atlassian accountId of the user who granted a one-time permission to complete an issue despite open blockers, plus an ISO-8601 timestamp. Used solely to attribute the override in an audit comment on the issue. | Maximum 15 minutes; deleted when consumed |
The Atlassian accountId is a pseudonymous identifier issued by Atlassian. The app stores no names, no email addresses, no IP addresses and no free-text user content.
6.4 Data the app writes
The app posts comments on Jira issues — to notify a waiting issue that its blocker is done, and to record an audit trail when an override is granted. Where auto-guard is enabled and an issue is completed while blockers are still open, the app reverts that status transition.
6.5 Legal basis and controller
Where the app processes personal data on behalf of the customer operating the Jira instance, that customer is the controller and KeulTech acts as processor. Processing is limited to what is described above and is necessary for the app’s contractual function under Art. 6(1)(b) GDPR.
6.6 Access by the provider
KeulTech has no runtime access to customer data. There is no provider-operated database, log store or admin console holding customer data. Diagnostic access is limited to Forge application logs in the Atlassian Developer Console, secured by the provider’s own Atlassian account with two-factor authentication.
6.7 Contact
Questions about app data processing: info@keul.tech
The German version of this privacy policy is available at https://keul.tech/datenschutz.