Filter Activity Stream

Filter Activity Stream for Jira privacy policy

Last updated on 2026-11-05.

No data leaves Atlassian. The app has no servers of its own and no external permissions. It uses no analytics, no cookies, no CDNs and no third parties. Everything runs on Atlassian's Forge platform.

What the app processes

Jira data you can already see. For the issues in your filter or JQL, the app reads issue keys, summaries, creation times, creators, changelog entries (who changed which field, old and new values) and comments. It reads them as you, through your own Jira permissions. Restricted comments and issues you cannot browse are never returned to the app.
Your settings. The gadget's settings (filter or JQL, time window, event types, selected people, grouping, page size) are stored by Jira as gadget configuration on your dashboard.
Forge context. The app uses your Atlassian account ID, site URL and time zone, which Forge provides to every app. They are used to make the Jira requests, to keep the cache separate per user, and to show local times.

What the app stores, and for how long

Storage is Forge app storage (KVS), which Atlassian hosts with your site's data.

Data	Contents	Retention
Result cache	The activity list for one user and one query, with issue keys and summaries, people's account IDs and display names, field names, old/new values (max 200 characters) and comment excerpts (max 280 characters)	Expires after 5 minutes (chunks after 6 minutes)
Global-page settings	Your last query on the global page (filter or JQL, window, event types, selected account IDs, grouping, page size)	30 days after your last save

The cache key is a SHA-256 hash of your account ID and the query, so one person's cached results are never shown to someone else.

Both records contain personal data. These are Atlassian account IDs and display names (cache) and account IDs selected in the people filter (settings). Both stay in Forge storage, hosted by Atlassian.

What the vendor collects

Nothing. The vendor receives no personal data, issue content, usage data or telemetry. The app only writes standard Forge function logs. They contain warnings without issue content, for example "cache write failed".

Data subject requests

The vendor holds no data. Cached results expire on their own within minutes. Global-page settings expire 30 days after the last save, or are overwritten when you save a new query. Uninstalling the app removes its access to your site.

Security

All Jira calls use asUser(), so the app never sees more than the viewer can.
The app uses minimal scopes, read:jira-work and read:jira-user (read-only Jira access), plus storage:app, which lets the app read and write its own Forge storage for the 5-minute cache and the saved page settings. The app has no scope that writes to Jira.
Filter names are escaped as JQL strings. JQL structure is checked before it is wrapped. Requests go only to a fixed allow-list of Jira REST paths.
CSV export neutralizes spreadsheet formulas.