Skip to main content

Data security and privacy for Jira

This page describes what Event Planner for Jira stores, where it stores it, and who can read or change it. Use it for your security review, together with the privacy and security tab of the Marketplace listing.

Where the app runs​

The app is built on Atlassian Forge. Its code and its storage run on Atlassian's infrastructure. The app has no servers of its own, and it isn't allowed to send data to any address outside Atlassian. That makes it eligible for the Runs on Atlassian program.

What the app stores​

The app keeps one calendar for each Issue Panel and one for each Dashboard Gadget. It keeps them in Forge hosted storage, inside your site's app installation.

DataWhat it holdsWhy
EventsTitle, description, start and end, all-day flag, and color of each eventTo show the calendar
Day headersA date and the text you typed for itTo label days on the calendar
Calendar settingsDefault view, start of week, weekends, working hours, slot size, scroll-to time, height, and the lock switchTo show the calendar the way you set it up

The app never stores:

  • Who created or changed an event. Calendars hold no account IDs, names or email addresses.
  • Work item content, such as fields, comments or attachments.
  • Personal data, except what people type into an event's title or description.

How data flows​

  1. Your browser loads the app from Atlassian. The calendar runs in a sandboxed frame inside Jira.
  2. When you open a calendar, the request goes to the app's Forge function. Forge tells the function which work item, or which dashboard and gadget, the calendar belongs to. The browser can't pick another calendar.
  3. The function asks Jira, as you, whether you can view the work item or dashboard. For a change, it also checks that you can edit it and that the app license is active.
  4. Only then does the function read or save the calendar in Forge hosted storage.
  5. Your browser builds ICS and CSV exports and saves them to your device.
  6. No data goes to Apportunity UG (haftungsbeschränkt) or to any third party.

Who can see and change a calendar​

Every check runs on the server side, as the signed-in user, on each request. The app's own access is never used to read or save a calendar.

CalendarViewCreate, edit, or delete events
Issue PanelPermission to view the work item (BROWSE_PROJECTS)Permission to edit the work item (EDIT_ISSUES)
Dashboard GadgetPermission to view the dashboardPermission to edit the dashboard
  • People who can view but not edit see the calendar read-only.
  • People who aren't signed in, for example on a public dashboard, can't open a calendar.
  • If the app license isn't active, calendars stay readable, but nobody can change them.
  • Anyone who can edit a calendar can change or delete any event on it. Events have no owner.

Data residency​

Forge hosted storage keeps the app's data in the same location as your Jira site, and moves it with the site when an admin changes the site's data residency location. See Atlassian's Forge data residency page for the supported locations.

Encryption, retention and deletion​

  • In transit: all traffic between browsers, Forge and Jira uses HTTPS.
  • At rest: Forge hosted storage is encrypted on disk by Atlassian.
  • Deleting a work item deletes its Issue Panel calendar.
  • Uninstalling the app: Atlassian keeps the app's stored data for 28 days, so it can be restored if you reinstall, then deletes it.

What isn't deleted automatically​

Jira doesn't tell apps about these changes, so the calendar stays in the app's storage until you uninstall the app:

You do thisWhat stays in storageTo remove the data first
Delete a spaceThe Issue Panel calendars of the space's work itemsDelete the events on each calendar, or delete the work items, before you delete the space
Remove a Dashboard GadgetThat gadget's calendarDelete the gadget's events before you remove it
Delete a dashboardThe calendars of its Event Planner gadgetsDelete the events on each gadget before you delete the dashboard

Data left behind can't be opened again: the work item, gadget or dashboard it belonged to no longer exists.

App permissions​

The app asks for these Jira permissions (scopes) when it's installed:

ScopeWhat the app uses it for
read:jira-workCheck, as you, whether you can view or edit a work item or dashboard. It also lets the app learn that a work item was deleted, so it can delete its calendar
write:jira-workNot used by the current version of the app. The app doesn't change work items, comments or attachments
storage:appKeep calendars in Forge hosted storage

Subprocessors and AI​

The app uses no subprocessors other than Atlassian. It calls no AI service. The AI reference describes a format you can use with your own AI assistant, outside the app.

Report a security issue​

Report a vulnerability or ask a security question through the support portal.