Issue Dates Calendar

Privacy policy for Issue Dates Calendar for Confluence

Publisher Zovo. Last updated 2026-11-05.

What the app reads

When someone views a page with the macro, the app searches Jira as that person (Forge asUser) with the macro's JQL. For each matching issue it reads the key, summary, status, issue type and the configured date fields. If a custom date field is configured, it also reads Jira's field list to check that field's name and type. It can't see anything the viewer can't see in Jira, and it has no scope that writes to Jira or Confluence.

What the app stores

• A result cache in Forge storage, inside Atlassian. It holds the issue data listed above for one viewer, one macro query and one calendar range, for 5 minutes, and then it expires.
• A field cache in the same storage. It holds the names and types of the configured custom date fields for one viewer, also for 5 minutes.
• Both storage keys are SHA-256 hashes that include the viewer's Atlassian account ID, so cached data is never shown to another person. No account IDs, names, e-mail addresses or avatars are stored in the values.
• Confluence stores the macro settings (JQL, fields, view, title) in the page, like any macro parameters.

What the app does not do

No data leaves Atlassian. The app has no external (egress) permissions, no remote backend, no analytics and no tracking. No data is sold or shared.

Personal data

Issue summaries are free text and may contain personal data written by Jira users. The cache keys are derived from the account ID. Everything expires within 5 minutes, and nothing is kept longer.

Contact

Send questions or deletion requests through the "Support" link on the Atlassian Marketplace listing.