Privacy Policy — Seats Reclaim for Jira
Last updated: 17 October 2026 · Regulation (EU) 2016/679 (GDPR)
The short version
Seats Reclaim for Jira runs entirely inside Atlassian. It is a native Forge app that declares no external network permission — permissions.external.fetch is absent from its manifest.yml — which means the Atlassian platform itself prevents the app from sending anything anywhere. We do not operate a server, a database or an analytics pipeline for this app, because the app cannot reach one.
Who we are
Pieran Lab di Erik Pieran — sole trader, Italy
Via Bruno Mion 100, 30038 Spinea (VE), Italy
VAT / Tax code: IT04915430278 · REA: VE-463627
Email: support@pieranlab.cloud
What the app reads
To do its job, Seats Reclaim reads the following from your Jira site, using your own administrator permissions — it calls the Jira API as the logged-in user, never with an identity of its own:
- Your account id and display name (
GET /rest/api/3/myself) — so it never proposes to remove you. - Group names and ids (
GET /rest/api/3/group/bulk) — to let you pick the group. - Group members: account id, display name, e-mail address as Jira returns it, account type, active flag (
GET /rest/api/3/group/member) — to build the preview. - Display names of the people listed in the History tab (
GET /rest/api/3/user/bulk) — read each time you open it, never stored. - Which groups grant which product, and how many users are billed (
GET /rest/api/3/applicationrole) — to know whether a removal actually frees a paid seat. - Whether an account holds the Administer Jira permission (
POST /rest/api/3/permissions/check) — so administrators are never removed. - The date of the most recent issue a person is assignee, reporter, creator or worklog author of, and whether they changed any issue inside your window (
GET /rest/api/3/search/jql) — to measure activity. - How many unresolved issues are assigned to them (
POST /rest/api/3/search/approximate-count) — so open work is never orphaned. - Whether your site is on a free or paid Jira plan (
GET /rest/api/3/instance/license).
Issue content is never read. The activity queries ask only for the updated timestamp field; the summary, description, comments and attachments of your issues are never requested.
All of this is processed in memory, inside the Forge runtime, for the duration of the request.
What the app stores
One thing only: the operation log, in Atlassian Forge storage attached to your own installation. Each entry holds a timestamp and the group name, the Atlassian account id of each person whose access was removed, who was skipped or failed and why, and the figure that was shown at the time. No names and no e-mail addresses are stored.
Why account ids are enough: the Undo button has to put exactly those people back, and an account id identifies them exactly. The names you see in the History tab are read from Jira each time you open it, so they are always current; an account that has since been closed simply shows its id.
- Retention: the last 50 operations. Older ones fall off automatically.
- Deletion: the Jira administrator can delete everything from the History tab at any time, with the “Delete the log” button. That works even if the subscription is not active — deleting your own data is never behind a paywall.
- On uninstall: Atlassian keeps the app’s storage for that installation for 28 days, so that it can be restored if the app is reinstalled, and then deletes it.
What the app does not do
- It does not send data to us or to anyone else. It cannot: the app has no egress permission.
- It does not use cookies, trackers or analytics.
- It has no sub-processors, because nothing is processed outside Atlassian’s own infrastructure.
- It never asks you for an API token, a password, or an account with us. There is no account with us.
Where the data lives
In your Atlassian instance and in Atlassian’s Forge platform, under Atlassian’s own data residency arrangements. We do not choose or control that location, and we never hold a copy.
Your rights under the GDPR
Because we never receive your data, requests for access, rectification or erasure are satisfied inside the app: the History tab shows everything stored and deletes it on demand. If you need written confirmation for an audit, write to support@pieranlab.cloud.
Roles: for the personal data in your Jira site you, the customer, are the controller. We do not act as a processor in the usual sense, because no data reaches us: the processing happens inside your own Atlassian tenancy, under Atlassian’s terms.
See also
The security statement and the support page.
Changes
This policy is versioned with the app. The date at the top changes when the content does, and material changes are noted in the release notes.