Questions, answered.

How often does Guardian check my configuration?#

Run a scan on demand or use the daily schedule after the initial baseline is established. Scans require an active or trial license and the relevant capability settings. A scan or privacy operation already in progress can delay the next operation. Guardian is not a real-time monitoring or prediction service.

Where will I see a configuration warning?#

Review findings and recommended review groups inside Guardian in Jira. Each finding provides its evidence and review guidance. The app does not currently send email, Slack or other external notifications. Some findings identify existing problems; others highlight conditions that deserve review before you decide whether a Jira change is needed.

Does Guardian change Jira configuration?#

No. Jira access is read-only. Guardian records app-owned findings, settings and history but does not fix, delete or modify Jira objects.

Does a finding mean an object is unsafe?#

No. It is a review signal. Administrators must validate business context, dependencies, ownership and normal change-control requirements.

Does an inactive account mean an employee left?#

No. Guardian reports only Jira account activity state. It makes no employment or identity conclusion.

What data leaves Atlassian?#

The app runs on Forge with no remotes, external database, external analytics, AI service or outbound notification channel. Privacy reports go to Atlassian. An authorized administrator can download JSON containing identifiers and evidence to their device. Information voluntarily supplied for support is handled separately through the Atlassian JSM portal or Google Workspace. Downloads and support correspondence have their own recipients and retention; they must not be described as never leaving Atlassian.

Does Guardian store names or email addresses?#

The App does not intentionally retain them in runtime customer records. Business/support correspondence in Google Workspace and the Atlassian JSM support portal can include names and email addresses. The masking-enabled build stores installation-specific account references in ordinary records and one original ID per account in Forge secret storage for authorized functionality, privacy reporting, export and erasure. The installation key is stored separately in Forge secret storage. Other installations require their separately approved compatible upgrade. Display names can be processed transiently for a bounded UI response and are discarded.

Does masking make the data anonymous?#

No. Authorized operations can resolve the stored references, and exports can contain original account IDs. Existing derived fingerprints and privacy-restriction hashes can remain linkable. Masking reduces repeated original-ID storage; it does not promise removal of platform IP/request logs or backups. See Security and Data for the qualified rollout and retained data.

How long is data retained?#

Resolved findings and eligible historical scan data enter scheduled batched cleanup after 90 days. Active findings and current/previous baselines are retained while needed. See the Privacy Policy for the exact lifecycle.

How do I delete Guardian data?#

To obtain a copy first, use Download Guardian data (JSON) in Settings. It includes account IDs and evidence, is available to authorized administrators without license renewal, and is not a Jira backup or restore file. Large exports beyond the 256 MiB browser limit require assistance. Store the downloaded file securely.

A Jira administrator can run Delete Guardian history. Settings, schema/capability configuration, a limited operation receipt and necessary hashed privacy-restriction markers remain. The masking-enabled build retains its installation key/control and removes unused account mappings through bounded cleanup after reference checks. Future enabled scans can collect permitted data again. Run deletion before uninstall if app-level removal is required. Atlassian's current Forge storage reference states that hosted storage is retained for 28 days after uninstall, with recovery requests due within 21 days; the platform controls that physical lifecycle.

Why can Coverage be partial?#

Guardian refuses to label inaccessible or over-limit inventory as healthy. Permissions, product availability, API behavior or declared safety ceilings can limit a domain.

Who can install and use Guardian?#

An authorized administrator installs it on the intended Jira Cloud site and approves its permissions. Every in-app request checks current Jira administrator authority. Read-only Jira scopes cover supported configuration; app-storage and personal-data-reporting scopes support Guardian records and privacy obligations. See the installation and permissions guide.

Why can scans or export be temporarily blocked?#

A scan, history deletion or privacy operation may already be active. Privacy maintenance continues independently of paid licensing and scan scheduling, and conflicting actions wait for it to finish. If the status remains blocked, send sanitized details to support. Turning off scheduled scans does not disable privacy handling.

What happens without an active license?#

Scans and ordinary Guardian-state changes require an active/trial license. Authorized administrators retain read-only views, JSON export, privacy-request handling and history deletion without renewing a paid license. Deletion does not cancel the Marketplace subscription.

Is all information kept in the EU?#

No EU-only processing promise is made. Forge hosted-storage residency follows the host product's applicable settings; compute and provider support access have separate rules. Business correspondence uses Workspace Business Starter, which does not offer the Workspace data-region policy. Customer downloads go to the chosen device. See Security and Data.

What site size is supported?#

The qualified statement is limited to the documented large-site profile. Hard internal ceilings are safety mechanisms, not a promise of unlimited scale. Contact support before relying on broader configurations.

Is 24/7 support included?#

No. Support is provided asynchronously in English, Monday–Friday excluding closures listed on the published support calendar, with published first-response targets measured in support business days. There is no fixed live-support window, and Atlassian service availability can also affect restoration.

Use the support portal with signup/login for ordinary help. See the support policy and calendar for targets. Report security concerns to [email protected] and rights requests to [email protected]; do not include secrets or full Jira exports in an ordinary support request.