ProbePilot for Jira privacy policy
What ProbePilot stores
ProbePilot stores the following in your installation’s Forge storage.
| Data | Personal data? | Purpose |
|---|---|---|
| Atlassian account IDs (requesters, approvers, owners, admins) | An identifier. The app does not store the names or email addresses of Atlassian users. | Attribute bookings, approvals and the audit log |
| Bookings, environments, dependencies and rules | Business data | The product’s function |
| Deployment records: source, environment, commit reference, pipeline link and the CI user name your CI sends | May include a CI user name. Your CI decides what it sends; it can be a username or, depending on your setup, an email address. | Show who deployed what, and when |
| Booking purpose text and issue keys | May contain text customers enter | The product’s function |
| Audit log (actor account ID, action, entity) | An identifier | Accountability; purged after 365 days |
Display names of Atlassian users are read from Jira when needed and are not saved.
Data residency
ProbePilot operates no servers and sends no customer data to third parties. The data stays in Forge storage, which follows the location of your Atlassian site. Because the app is built on Atlassian Forge, Atlassian’s own sub-processors apply to that storage; see Atlassian’s published sub-processor information.
Retention
The audit log is kept for 365 days. Deployment records and other data are kept until you delete them or uninstall the app.
When you uninstall, Atlassian soft-deletes the app’s stored data. If the app is reinstalled within 21 days, the new installation can be linked to the old data. After that, the data is removed in line with Atlassian’s retention policy for Forge-hosted storage.
Closed accounts
The app reports the Atlassian account IDs it stores to Atlassian’s personal data reporting service on a regular schedule. When an account is reported as closed, its ID is replaced with a fixed placeholder shared by all closed accounts, so it can no longer be linked to a person, and entries that only linked that person, such as approver lists, are removed. CI user names are not Atlassian account IDs: they stay with their deployment record until you delete it.
Your rights
You can ask us what personal data we hold about you and ask us to correct or delete it. If you are in the European Union or the United Kingdom, you can also complain to your local data protection authority.
Contact
Questions about this policy: contact@probeflow.net. Product help: support@probeflow.net.
Changes
- 1.0 (2026-11-21): First published version.