Permissions and data

What the app reads, what it keeps and whose permissions apply.

Reads

Requests, service desks, request types, organisations, groups and user names, read from Jira as the signed-in person, never as the app. Admin checks and the field list in Fields configuration use the admin’s own permissions.

Keeps, in Forge storage

  • General settings, user scopes, fields configuration and filter permissions. These hold account IDs and organisation and group names.
  • Saved filters: name and criteria, kept under the owner’s account ID. Shared and global filters also hold the owner’s display name. Favourites and each person’s default view.

Who sees filter details

  • A shared or global filter shows its name and its owner’s display name to everyone who can see it.
  • Jira admins see the name, owner and sharing of every saved filter in Filters management, including private ones, and can delete any of them. They do not see a filter’s criteria there.
  • Other customers cannot see, change or delete someone’s private filter.

In the browser

The last screen a customer had open, kept in that browser tab for up to 12 hours. Search text and custom-field filter values are not kept.

Account reporting and erasure

Once a day a scheduled job reports the account IDs the app has stored to Atlassian’s personal data reporting API, in batches of 90. Each account is reported at most once every 7 days. When Atlassian reports an account as closed, the app deletes that person’s private filters, favourites and default view, removes them from every user list in Visibility, user scopes and filter permissions, and shows their shared and global filters as owned by “Former user”. When an account is reported as updated, the stored owner name is cleared and looked up from Jira when needed. The privacy policy has the full description.

Does not

  • Store request content.
  • Send data outside Atlassian. The app lists no outside address.
  • Collect analytics.

Logs

Each call logs the function name, an outcome code and how long it took. No request content or names. The daily reporting job logs counts and codes only, never account IDs.

Trust Center

For security reviews, see the Trust Center, including data logging and retention and data retention and deletion.


Need help with PortalPilot? Contact us