Privacy policy

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:

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.

What the app does not do

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.