Security Policy – Balloon Apps (Atlassian apps)

Last updated: 1 October 2026.

This page describes how Balloon Apps (listed on the Atlassian Marketplace as ‘Ballon Apps’), a brand of RVDH Interim Management B.V. (the Netherlands), protects the data handled by its apps for Atlassian Jira Cloud. It applies to: Time in Status for Jira, Last Comment Field for Jira, Approval Gate for Jira, User Access Review for Jira, Recurring Issues for Jira and Retention Policy for Jira. Each app also has its own privacy policy, linked in the table below.

1. Architecture: everything runs on Atlassian Forge

2. Data handling per app

AppWhere data is storedWhat is storedPersonal data stored
Time in Status for Jira Nothing is stored. Issue data and change history are read on demand, turned into durations in memory and discarded when the function ends. None stored.
Last Comment Field for Jira In your own Jira site, as the value of the app's read-only custom field. No Forge Storage. One value per issue: an excerpt of the newest comment (max. 254 characters), the author's display name and the date. Overwritten when a newer comment arrives. The comment author's display name (inside the field value).
Approval Gate for Jira In your own Jira site, as issue properties on the issue concerned, plus a comment on the issue when a decision is made. From version 4.0.0 also a small account index in Forge Storage (Atlassian-hosted key-value store, scoped to your installation). Approval requests and decisions (title, optional description, decision rule, timestamps, decision comments) and an append-only audit trail; a separate property records when the workflow validator let a transition pass without being able to enforce the gate. The account index lists, per account ID, the issues it occurs on; it holds no approval content. Atlassian account IDs of the requester, approvers and actors (in the issue property and in the account index). The reassignment comment does not name individuals. No e-mail addresses are stored. From version 4.0.0 the app reports the account IDs it holds through Atlassian's personal data reporting; the ID of a closed account is replaced by an anonymous marker (shown as "Former user").
User Access Review for Jira Forge Storage (Atlassian-hosted key-value store, scoped to your installation). Daily access snapshots per project (who can reach the project and through which role, group or direct grant) and group membership versions. Data older than 400 days is pruned automatically (the last version before that window is kept as the starting point). Atlassian account IDs of the people who hold access, and group names. Display names of people are not stored: they are looked up from Jira when a page is opened. From version 6.0.0 the app reports the account IDs it holds through Atlassian's personal data reporting; the ID of a closed account is replaced by an anonymous marker.
Recurring Issues for Jira Forge Storage (Atlassian-hosted key-value store, scoped to your installation). The recurrence rules you configure (issue template fields, schedule, next run) and, per rule, an authorisation record showing that the permission check ran. One Atlassian account ID per rule (the person who saved it). From version 5.0.0, for closed accounts the app acts on Atlassian's personal data reporting and clears that ID.
Retention Policy for Jira Forge Storage (Atlassian-hosted key-value store, scoped to your installation). Your archiving rules (name, JQL filter, schedule, summary of the last run) and an audit log capped at the 100 most recent runs. None. Error messages in the audit log may contain the key of an issue that could not be archived.

None of the apps stores e-mail addresses, attachments or issue descriptions. Data stored in Forge Storage is scoped to your installation; data stored in Jira (custom field values, issue properties, comments) follows the lifecycle and access rules of your Jira site.

3. Encryption

4. Access control

5. Vulnerability management

6. Security incidents

If we become aware of a security incident that affects, or may affect, customer data processed by one of these apps, we contain it, notify Atlassian through its ecosystem support channel (ECOHELP) as Atlassian requires, and inform the affected customers without undue delay, with what we know about the nature of the incident, the data involved and the measures taken. To report a suspected incident, contact info@kyc-checks.nl.

7. Certifications

Balloon Apps does not hold security certifications such as SOC 2 or ISO/IEC 27001. The apps run on Atlassian's Forge platform, which is operated and certified by Atlassian; those certifications cover Atlassian's platform, not our own code or processes. How responsibilities are divided is described in Atlassian's Forge shared responsibility model.

8. Contact

Balloon Apps, a brand of RVDH Interim Management B.V., the Netherlands.
Security questions, vulnerability reports and incident reports: info@kyc-checks.nl.