Filter Delta for Jira / Privacy
A small history.
A clear data picture.
The data used by Filter Delta, where it is processed and the controls available to you.
Jira Cloud Preparing for public release
What this page covers
This page describes the current app’s technical data handling before its public Marketplace release. It is not a completed contractual data-processing agreement. The legal privacy terms for public distribution are still being finalised.
Filter Delta is provided by Robert Freese under the Untiefe name. Find operator and address details in the legal notice. For privacy enquiries, contact info@untiefe.dev.
The website privacy notice separately covers visiting untiefe.dev and emailing us. The website’s hosting location and email provider do not describe where Jira or Forge processes app data.
Data stored by the app
Filter Delta uses Atlassian Forge hosted Key-Value Store for:
- Owner information: your Jira account ID, an internal owner reference, privacy-reporting timestamps and status.
- Monitor settings: internal IDs, the monitor name, saved filter ID or direct JQL, source hash, revision, daily-scan setting, timestamps, status and safe error fields.
- Snapshots: issue IDs, issue counts, timestamps, scan trigger and request references needed to compare result membership.
- Operations: request status and attempts, temporary cancellation markers, a token-protected deletion receipt, and maintenance counts and privacy-reporting state.
Issue IDs are the snapshot’s stored issue content; they are not the only data stored by the app. In particular, your owner account ID and monitor source are also stored. Avoid creating a monitor with sensitive JQL if you do not want that source stored.
Current details, not historical copies
Issue keys and summaries are fetched only when you view a comparison and only within your current Jira permissions. They are not persisted as historical content.
The app does not store issue descriptions, comments, attachments, worklogs, full changelogs, profile names, email addresses, customer-supplied API tokens, external analytics identifiers or complete Jira REST responses.
Why the data is used
The stored data supports personal monitor configuration, baselines and comparisons, manual and daily scans, queued work and retries, scan limits, retention, privacy reporting and verified deletion.
Jira and Forge platform services process data to operate the app. Filter Delta declares no external app servers, remotes, external authentication providers or analytics services. This does not mean Jira and Forge do not process personal data.
Retention and removal
- Snapshots: 14 days and at most 100 snapshots per monitor, whichever limit is reached first. Expired snapshots are excluded from lists and comparisons; hourly maintenance removes expired records and references.
- Request records: expire after 7 days and are removed by maintenance or their expiry mechanism.
- Monitor and owner data: removed through the deletion controls or the account-lifecycle handling described below.
- Deletion evidence: temporary cancellation markers and a token-protected completion receipt may remain for up to 7 days to prevent stale jobs recreating data and to confirm completion. The receipt contains no account ID, owner reference, JQL, issue IDs or Jira content.
Delete monitor removes that monitor’s configuration and snapshots. Delete my app data removes your owner record, monitors, snapshots, owner-scoped requests and registry entries for the current installation. See the step-by-step instructions.
Uninstalling the app is different from requesting deletion in the app. Remaining hosted storage after uninstall follows Forge’s platform lifecycle; immediate deletion by the app is not promised. Use the deletion controls before uninstalling when possible.
Your controls and account lifecycle
You can pause daily scans, delete a monitor or delete all your own Filter Delta app data in an installation. Deletion and privacy controls remain available if the licence is inactive or unavailable.
The app reports stored owner account IDs through Forge’s personal-data reporting API. If Atlassian reports an account as closed or its stored personal data as updated, Filter Delta deletes the affected owner’s app data.
For access, correction, deletion or other privacy enquiries outside these controls, contact info@untiefe.dev. Start with a short description of the request. Do not email credentials, private JQL or issue content.