Privacy policy — AccessLens for Jira
The short version
AccessLens does not send your data anywhere. It runs entirely on Atlassian Forge, inside Atlassian's infrastructure. The app declares no external network permissions, which Atlassian enforces at the platform level — it cannot make an outbound call even if it tried. CSV files are generated in your browser, so exported data never traverses a vendor server either.
What the app stores
Everything is stored in Forge app storage (Atlassian-hosted KVS) inside your own Atlassian tenant region. The vendor operates no infrastructure and holds no copy.
| Data | Examples | Why |
|---|---|---|
| Project references | project id, key, name | to answer “who can access what” |
| Permission state | permission scheme grants, project role membership, group names and member account ids | the content of snapshots and diffs |
| Review records | the reviewer's Atlassian account id, a server-side UTC timestamp, the note, and the snapshot it was judged against | the audit artefact |
| Settings | snapshot retention limit, schedule | app configuration |
Personal data is limited to Atlassian account ids and display names as returned by the Jira API. AccessLens does not store issue content, attachments, email addresses, or any data you have not explicitly asked it to audit.
What is never stored
- Issue descriptions, comments, or attachments
- Email addresses
- IP addresses, usage analytics, or behavioural tracking
Who can see it
The only UI surface is an admin page, which Jira restricts to site administrators. Review sign-off carries the reviewer's Atlassian account id taken from the Forge invocation context — never from the browser — so attribution cannot be forged.
Retention and deletion
- Snapshots are retained until an administrator deletes them, capped at a configurable limit (default 12). At the limit the app refuses a new snapshot rather than evicting an old one: audit evidence is never discarded automatically.
- Review records persist until deleted by an administrator.
- Uninstalling the app removes all Forge storage.
Data residency
Whatever your Atlassian site's residency is. AccessLens adds no storage outside Forge and therefore introduces no additional residency considerations.
Sub-processors
None. Atlassian hosts everything; there is no other party involved.
Changes
Material changes to what is stored or where will be reflected here and in the Marketplace listing before they ship.
Contact
xianpeng.shen@gmail.com. For data access, correction or deletion requests, contact the same address.