Security Statement for Page Review Manager for Confluence

SECURITY_STATEMENT.md

Data Security And Privacy Statement For Confluence Page Review Manager

Last updated: 2026-03-25

Purpose

This statement is the combined data security and privacy document used for the Atlassian Marketplace Data security and privacy statement field for Page Review Manager for Confluence.

It is intended to summarize how the current app handles End-User Data and how the current launch build is secured.

Current Product Scope

The current app is a Forge-hosted Confluence app that helps customers:

• activate one governed Confluence space
• identify stale or due-soon pages
• record review workflow actions
• keep an audit trail for those actions

Data Handled By The App

Based on the current implementation, the app may access or store:

• Confluence page metadata needed to assess freshness
  • page identifiers
  • page titles
  • update timestamps
  • space identifiers, keys, and names
• review workflow data created by users of the app
  • review decision status
  • defer-until timestamps
  • assigned owner account identifiers
  • assigned owner display names when selected in the UI
  • audit timestamps
  • actor account identifiers associated with review actions
• installation and configuration data
  • governed space selection
  • review cadence settings

The app is not currently designed to store full Confluence page bodies in application storage.

Where Data Is Stored

The current implementation uses:

• Atlassian Forge hosted runtime
• Atlassian Forge hosted storage

The app does not currently declare:

• external data egress
• a vendor-hosted database
• third-party processors in the request path
• external analytics or logging sinks

How Data Is Used

The app uses data to:

• determine whether content is current, due soon, stale, or needs attention
• display status in the Confluence space dashboard and page byline
• record review workflow actions
• preserve audit history for review actions
• enforce one governed space per installation

Data Sharing

Based on the current implementation, the app does not intentionally share End-User Data with third-party entities outside Atlassian-hosted services.

Logging

The app is intended to keep logging limited to operational diagnostics and to avoid intentionally emitting raw page bodies or unnecessary End-User Data to logs.

Security Posture

The current app is designed around:

• least-privilege scopes
• Forge-hosted compute and storage
• no declared external egress
• storage of governance metadata rather than copied page bodies

Declared scopes in the current launch build:

• storage:app
• read:page:confluence

Current page reads use the current user context, and application writes are restricted by governed-space enforcement in the app logic.

The current development deployments have also reported eligibility for the Runs on Atlassian program.

Retention

The app stores governance configuration and review history in Atlassian Forge-hosted storage.

Based on Atlassian's current Forge-hosted storage lifecycle documentation, hosted storage retains app data according to Atlassian's retention lifecycle after uninstall. The app does not currently offer a custom retention period or automatic restoration commitment after reinstall.

Limitations

This statement reflects the current app implementation only.

It must be updated before launch if any of the following are added:

• Jira follow-up creation
• background reminders
• remote back-end services
• third-party subprocessors
• external analytics
• customer-managed retention or deletion controls

Contact

Privacy or security questions about the app should be directed to support@nagayasu.work.