ankaiho

Privacy Policy — Offboarding Auditor

Data access, processing, retention and privacy request information.

English · 繁體中文 · 日本語 · Deutsch · Français · Español · Português (Brasil) · 한국어

Service provider and contact information

Data accessed

  • Atlassian account ID
  • display name
  • active/inactive status
  • account type where required
  • Jira issue ID/key
  • assignee
  • reporter
  • limited issue metadata needed for findings
  • scan/case/history/audit metadata

Purpose

  • identify inactive accounts
  • detect supported Jira dependencies
  • display offboarding cases
  • maintain scan/history information
  • generate audit exports
  • provide support and security diagnostics

Hosting and storage

The app runs on Atlassian Forge.

The production deployment must be verified as eligible for Runs on Atlassian before stating eligibility as confirmed.

App-managed persistent data is described as stored using Forge app storage.

External processing

The described release does not use the following; this must be validated against the production deployment:

  • an external application server
  • an external database
  • Forge Remote
  • third-party analytics
  • external AI/LLM processing

Retention

App-managed scan, case, dependency, history and audit metadata are retained while needed to provide the service while the app remains installed, unless deleted earlier through an applicable process.

Deletion

The app includes pre-uninstall cleanup logic intended to remove app-managed stored data. Verify its execution and the data deletion behavior before launch.

This does not delete underlying Jira issues or Atlassian accounts.

Logging

Operational logs may be generated for troubleshooting and reliability.

The app is designed not to intentionally log:

  • passwords
  • API tokens
  • Authorization headers
  • session cookies
  • authentication state
  • unnecessary personal information

Privacy requests

For data subject requests (DSR), contact privacy@ankaiho.com.