Handover for Jira runs entirely on Atlassian's Forge platform. We operate no servers and receive no customer data. Everything the app processes stays on Atlassian infrastructure attached to your own Jira site.
To perform an offboarding, the app reads, within your Jira site: user profiles (account ID, display name, active flag) for people you search for; issues assigned to the selected leaver; filters, dashboards, components and projects they own or lead; and their group membership names.
Offboarding plans, execution progress, audit summaries and app settings, in Atlassian Forge storage on your site. This includes account IDs and display names of leavers and successors, and the issue keys and one-line issue summaries of reassigned work so administrators can review what was transferred. It does not include issue descriptions, comments, attachments, email addresses, or credentials. Data residency follows your Atlassian site's configuration. Administrators can delete any offboarding record from inside the app; uninstalling removes the app's storage under Atlassian's Forge data lifecycle (soft-deleted at uninstall, permanently deleted on Atlassian's retention schedule).
None. The app has no external endpoints, no telemetry and no analytics. If you email support, we receive what you send us and use it only to provide support.
We do not sell, share, or transfer app data; we never possess it. Our sole subprocessor for app operation is Atlassian (as your existing Jira host).
Data-subject requests concerning Jira content should be directed to your Jira administrator or Atlassian per their privacy program. Your administrator can delete individual offboarding records from inside the app. For support correspondence held by us, contact privacy@greylineinteractive.com for access or deletion.
This policy is published at https://handover.software/privacy. We will post changes there with an updated effective date.