Auto Participants privacy

Where the application runs

Auto Participants is an Atlassian Forge application. Its interface and its functions run on infrastructure operated by Atlassian, and it stores data only in Atlassian-hosted storage provisioned for your own installation. Atesen Software operates no server and no database for it.

What it talks to

Only your own Jira site. The application requests no external network egress. It uses no analytics or external service and sends no email of its own.

What it stores

• Rules: the name, service spaces, request types, the organizations or group to add, the group to leave out, the limit and the switches.
• Activity records: the request key, service space key, time, trigger, dry-run flag, record id, rule id and name, account IDs of added or refused participants, skip counts and error codes. Participant account IDs are retained in activity records and returned in previews so the interface can display Jira users.
• The application does not deliberately copy participant display names, email addresses or request content into activity records. Rule names are administrator-provided text and may contain personal information.

How long it is kept

A daily scheduled cleanup targets activity records older than 30 days. Scheduling delays or cleanup failures can extend retention; this is not an exact 30-day deletion guarantee. Rules are kept until an administrator deletes them. When the application is uninstalled, Atlassian deletes its stored data for your site.

Data residency

The application uses Atlassian-hosted storage, which follows the residency of your Jira site. If your organisation pins its Atlassian data to a region, the application’s data is pinned with it.