What the app stores
App-owned records use Atlassian Forge hosted key-value storage and are scoped to the installation. They contain:
- Configuration and an explicit dedicated-test-target acknowledgement.
- Project and issue identifiers, plus the issue key used to display the selected target.
- App, environment, tenant and installation binding identifiers.
- Enrollment, human-request, run and permit identifiers; protocol and policy digests.
- Run, permit-consumption and result state; bounded mutation-attempt counts and target/label match booleans.
- Issuance, expiry, consumption and completion timestamps.
These identifiers are used to keep a request bound to one installation, one target and one attempt. They are not used for advertising or user profiling.
What is processed during a request
The app uses Atlassian’s authenticated runtime context and current permission checks. It reads the selected Jira issue’s project and labels to resolve and verify the target. Response envelopes and label values are processed in memory; only the allowlisted identifiers and result facts above enter app-owned records.
Atlassian provides authentication. The app does not collect a separate account password or ask you to provide an API credential.
What is not stored
The Customer Beta does not store user names, email addresses or Atlassian user account identifiers in its app-owned configuration, run, permit or result records. It does not store issue descriptions, comments, raw Jira responses, credentials or tokens. Its result interface uses fixed text, safe identifiers and bounded result values rather than raw errors or stacks.
Why these records exist
Configuration identifies the dedicated target. Binding and permit records prevent cross-installation reuse and repeated execution. Result facts support verification and read-only status recovery when a response is uncertain.
There are no automatic or background Jira mutations in this Customer Beta. A separate explicit human Start is required for the one supported label-add attempt. The app does not retry an uncertain mutation automatically.
Where data goes
App records are stored in Atlassian Forge storage. Jira requests are made to Atlassian for the current installation. The current Customer Beta has no configured external data-ingestion service, advertising integration or analytics tracker. This policy site does not receive app records.
Atlassian operates the underlying platform and may process operational or authentication data under its own terms. See the Forge privacy and security information. This policy does not promise a particular data residency region or certification.
Retention, uninstall and your choices
App-owned configuration and one-shot execution records are retained while the installation remains in use. The current app does not implement a per-run automatic deletion timer or a self-service record reset. Consumption records are retained to prevent replay.
Uninstall is handled by Atlassian. Its current Forge storage documentation describes a 28-day post-uninstall retention period; uninstall should not be treated as instant erasure. A label already added to Jira is Jira data and is not automatically removed by uninstalling the app.
For access, correction, deletion or other privacy questions, use the private invitation channel described on the Support page. Do not send secrets or confidential issue contents. Requests are reviewed against applicable obligations, platform capabilities and the need to avoid unsafe replay; a request does not itself reset execution authority.
This policy website
This is a static site hosted on Cloudflare Pages. It has no application analytics, tracking scripts, advertising, contact form or application cookies, and stores no browser data through local storage. Cloudflare necessarily processes network-request information, such as IP address and browser/request metadata, to deliver and protect the site. See Cloudflare’s Privacy Policy.
Updates and contact
This policy applies to the current evaluation beta. Material changes to data handling will be reflected here before the changed functionality is offered. The date at the top identifies this version. Contact Automation Apps Lab through your private beta invitation channel.