Skip to main content

Data security and privacy

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

Where the app runs​

Both apps are built on Atlassian Forge. Their code and storage run on Atlassian's infrastructure, and Apportunity UG (haftungsbeschrΓ€nkt) has no servers of its own.

Both apps meet Atlassian's Runs on Atlassian requirements: they use only Atlassian-hosted compute and storage, follow your site's data residency, and send data out only for analytics, which admins can switch off.

The one connection outside Atlassian is error reports, logs and usage counts to Sentry. They never contain calendar content. See Error reports, logs and usage counts.

What a calendar holds​

Every calendar, in either product, holds the same kind of data:

DataWhat it holdsWhy
EventsTitle, description, start and end, all-day flag, color, and optionally a location and a linkTo show the calendar
People on eventsAtlassian account IDs onlyTo show who's involved. Names and avatars are looked up each time the calendar opens, and aren't stored
Day headersA date and the text you typed for itTo label days
Calendar settingsDefault view, start of week, weekends, working hours, time slots, height and the lockTo show the calendar the way you set it up
Save markersA revision number and random tokens of the last savesTo merge changes when several people save at once

A calendar never holds who created or changed an event, email addresses, or the content of the page or work item it sits on. Personal data is limited to account IDs of people on events and whatever people type into event fields.

Confluence​

Event Planner for Confluence keeps calendars in Confluence itself, as page attachments and space content.

Where the data is​

WhatWhereVisible to
Page calendarA JSON file attached to its page, named events-<macro ID>.json, created by the first saveWhoever can see the page's attachments
Space calendarConfluence content in its space, of the app's own content type. Confluence keeps a version for every saveWhoever the space permissions and the calendar's restrictions allow
Admin page settingsForge hosted storage: two values, Let people create calendars in spaces and Default access for new calendarsConfluence admins

A space calendar's name is indexed by Confluence search, like a page title. Its events aren't.

How data flows​

  1. Your browser loads the app from Atlassian. The calendar runs in a sandboxed frame inside Confluence.
  2. The calendar reads and saves its data through Confluence's own REST API, as you. Confluence applies page permissions, space permissions and restrictions to every request.
  3. For a PDF or Word export, the app's Forge function reads the calendar as the person exporting, and returns it as part of the document.
  4. Your browser builds ICS and CSV exports and saves them to your device.

Jira​

Event Planner for Jira keeps calendars in Forge hosted storage, not in Jira.

Where the data is​

The app keeps one calendar for each Event Planner panel and each Event Planner gadget, in Forge hosted storage inside your site's app installation.

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 see 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.

Who can see and change a calendar​

CalendarViewCreate, edit or delete events
Confluence page calendarView the pageEdit the page
Confluence space calendarSpace access and the calendar's restrictionsSpace permissions and the calendar's restrictions
Jira work item calendarSee the work item (BROWSE_PROJECTS)Edit the work item (EDIT_ISSUES)
Jira dashboard calendarThe dashboard is shared with youOwn the dashboard, or be shared on it as an editor
  • People who can view but not edit get the calendar read-only.
  • People who aren't signed in can't open Jira calendars. On public Confluence pages they can view page calendars.
  • 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.

The full list is in Permissions.

Error reports, logs and usage counts​

The apps send error reports, logs and usage counts to Sentry, hosted in the US, so we can find and fix problems.

ItemDetail
SentThe error or event, your site's ID, a pseudonymous user ID, and technical details such as the browser, operating system and app version
Never sentEvent titles, descriptions, locations, links and people; calendar, page, space and work item titles and keys; attachment names; people's names or email addresses
HowThe browser never contacts Sentry. Reports go through the app's Forge functions, which replace the user with a pseudonymous ID and add the site ID
How longSentry deletes them after at most 90 days

To switch analytics off, open the app in Connected apps in Atlassian Administration, select View app details, and turn off Analytics access. You can turn off Logs access and Custom metrics access there too. The app works the same with all of them off.

Data residency​

In Confluence, page attachments and space calendars are Confluence content, so they follow your Confluence site's data residency. The admin page settings are in Forge hosted storage.

In Jira, Forge hosted storage keeps calendars in the same location as your Jira site. It moves them with the site when an admin changes its data residency location.

See Atlassian's Forge data residency page for the supported locations.

Encryption, retention and deletion​

All traffic between browsers, Forge, Confluence and Jira uses HTTPS. Atlassian encrypts Confluence content and Forge hosted storage on disk.

When youWhat happens to the calendar
Delete a Confluence pageIts calendar file goes with it, under Confluence's trash rules
Move a space calendar to the trashIt disappears for everyone, then follows Confluence's trash rules
Delete a Jira work itemIts calendar is deleted
Uninstall the Confluence appPage and space calendars stay in Confluence; admin page settings are deleted
Uninstall the Jira appAtlassian keeps the calendars for 28 days, so a reinstall can restore them, then deletes them

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 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.

In Confluence, removing the Event Planner macro from a page leaves its calendar file in the page's attachments. Delete the file from the page's attachments to remove the events.

App permissions​

Each app asks for these permissions (scopes) when it's installed.

Event Planner for Confluence​

ScopeWhat the app uses it for
read:confluence-content.all, read:confluence-content.summary, read:content:confluence, read:page:confluenceRead the page a calendar is on, and check whether it's published
read:attachment:confluence, readonly:content.attachment:confluenceFind and read a page calendar's file
write:confluence-fileSave a page calendar's file
read:confluence-content.permissionCheck, as you, whether you can edit the page
read:custom-content:confluence, write:custom-content:confluence, delete:custom-content:confluenceList, read, create, save and move space calendars to the trash
write:confluence-contentSet the restrictions of a space calendar
read:confluence-space.summary, read:space:confluenceShow space names, and let you pick a space in Embed space calendar
read:confluence-user, read:content-details:confluenceSearch for people to add to events and restrictions, and show their names
read:confluence-groupsSearch for groups to add to restrictions
storage:appKeep the admin page settings
read:confluence-props, write:confluence-props, write:page:confluenceNot used by the current version of the app. It doesn't read or change content properties, and doesn't change pages

Event Planner for Jira​

ScopeWhat the app uses it for
read:jira-workCheck, as you, whether you can see 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
read:jira-userSearch for people to add to events, and show their names
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​

SubprocessorPurposeData
AtlassianHosting, storage and compute (Forge)All app data
Sentry (Functional Software, Inc.), USError reports, logs and usage countsSite ID, pseudonymous user ID, technical error details

The apps call no AI service.

Create with AI gives you a prompt to paste into an AI assistant of your choice, outside Event Planner. Only what you type into that assistant goes to it. You paste its answer back into Event Planner yourself.

Report a security issue​

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