TELCOMA Global / Seat Reclaim for Jira / Privacy policy
What the app reads, what it keeps, and what it changes.
This policy describes what Seat Reclaim for Jira does with your data.
1
What the app is
Seat Reclaim for Jira ("the app") is an Atlassian Marketplace app that helps a Jira Cloud administrator find licensed users who have shown no activity in Jira over a chosen period and, after the administrator confirms, free their seats by removing them from the groups that give them product access. It runs entirely on Atlassian's Forge platform.
2
What data the app processes
The app reads the following from your Jira Cloud site, using the permissions granted at installation:
- User directory data: account ID, active status and account type while a scan runs; display name and email address (where the user's Atlassian profile makes it visible to apps) only when the list, history or an export is displayed. None of these except the account ID are written to storage.
- Application roles and group membership: which groups give access to each Jira product, which of those groups each listed user belongs to, and Atlassian's per-product seat counts.
- Issue activity metadata: for recently-updated issues, the author and timestamp of changelog entries, comments and work logs, and the creator and reporter. The app reads this to determine who was active and when. It does not read issue descriptions, comment text, attachments or custom field values.
3
What the app changes
Only group membership on your Jira site, and only for users an administrator selects and confirms. A reclaim removes the user from the product access groups the app planned; an undo adds them back to exactly those groups. Both calls run as the signed-in administrator, and Jira itself only allows site administrators to make them. The app never deactivates or deletes accounts and never changes any other setting, issue or configuration.
4
What data the app stores
The app stores, in Forge's Atlassian-hosted storage within your site's data residency region:
- Scan progress (cursors, counters, timestamps).
- For each inactive user: the Atlassian account ID, product membership, the IDs of their product access groups at scan time, and an inactivity band derived by the app.
- A history of reclaims and undos: the account ID of the user affected and of the administrator who acted, when, which groups were changed, which products were freed, and the outcome.
- The protected list: account IDs an administrator has chosen to protect from reclaim.
- The yearly seat prices an administrator enters (one per product). These are settings, not personal data.
Display names and email addresses are not stored; they are read from Jira each time they are shown. The app never stores issue content, comment text, work log descriptions, attachments, or any text authored by your users.
5
Where data goes
Nowhere. The app makes no network requests outside Atlassian and has no servers of its own. Data does not leave your Atlassian site's hosting region. If an administrator uses the app's Rovo agent, the agent passes report and history data (names, products, inactivity bands, reclaim status and seat prices) to Atlassian Rovo, which writes the answer within Atlassian under your agreement with Atlassian. The agent cannot reclaim, undo or protect anyone.
6
Legal basis and roles
You (the customer) are the data controller for the personal data on your site. TELCOMA Global is a data processor acting on your instructions, which consist of installing the app, running scans, and confirming reclaims and undos. Where the GDPR applies, the app's processing is performed under your instructions and on Atlassian's infrastructure.
7
Retention and deletion
Report data persists until the next scan replaces it. The history keeps the most recent 1,000 reclaims and undos; older entries are deleted automatically. The protected list and seat prices stay until an administrator changes them. When the app is uninstalled, Forge deletes all app storage for your site. You may also request deletion by contacting us.
8
Security
The app runs on Atlassian Forge, which enforces the app's permissions at the platform level, hosts its storage, and isolates it from other apps. Its one write permission is used only for the group changes described above, made as the signed-in administrator after they confirm. Security issues may be reported to [email protected]; please do not post them publicly.
10
Changes to this policy
We will update this policy when the app's data handling changes and note the effective date above.