Documentation · Support · Privacy Policy · End User Terms · Security
Effective date: August 25, 2026
Baseline Guard (“the App”) is a Jira Cloud application built on the Atlassian Forge platform. It evaluates Jira project evidence and produces evidence-backed project assessments and reporting for Executive, Client, and Internal audiences.
This Privacy Policy explains what information Baseline Guard accesses and processes and how that information is handled.
Brian Levy, doing business as Levy Automations (“we,” “us,” or “our”) operates Baseline Guard.
For privacy or support questions, contact help@levyautomations.com.
Baseline Guard reads selected information from a Jira Cloud project when an authorized user generates an assessment.
The App uses available Jira evidence to evaluate project status, evidence confidence, risks, commitments, decisions, proposed actions, and evidence limitations.
Baseline Guard is designed to avoid presenting unsupported assessments when the available Jira evidence is insufficient.
When an authorized user generates an assessment, Baseline Guard accesses selected information from the Jira project chosen by that user.
Using Jira’s read:jira-work permission, this may include:
The information accessed depends on the project, reporting period, available Jira evidence, and selected reporting audience.
Baseline Guard does not request the read:jira-user scope and does not access the customer’s Jira user directory through that scope.
Baseline Guard does not fetch Jira comments.
Baseline Guard respects the Jira permissions of the user generating the assessment.
Assessments are generated on demand from Jira evidence available at the time of generation. During generation, Jira information is processed transiently within Atlassian Forge.
To support asynchronous generation and allow the requesting user to retrieve a result, Baseline Guard writes a generation-job record to Atlassian Forge Key-Value Store (KVS). Depending on the job state, that record may contain the requesting user’s Atlassian account identifier, Jira project key and name, selected reporting period and audience, job status and timestamps, a validated assessment and its evidence-derived fields, deterministic baseline, governance, and provenance information, or a structured error.
Baseline Guard does not operate an independently hosted or externally managed customer data store. These generation-job records remain within Atlassian-hosted Forge storage. Baseline Guard does not fetch Jira comments and does not intentionally write credentials or access tokens to generation-job records.
Local interactions or edits to a generated report are page-local and are not persisted by Baseline Guard.
Baseline Guard does not intentionally log Jira issue content.
Generation-job records use state-based time-to-live controls in Atlassian Forge KVS:
Each time a job record is updated, the time-to-live appropriate to its current state is applied. Forge KVS expires the record after that period unless it is updated again or deleted earlier. Baseline Guard’s personal-data reporting process may delete records earlier when Atlassian identifies a stored account as closed.
A newly generated assessment evaluates the Jira evidence available at the time it is generated.
Operational platform information may be processed by Atlassian as necessary to provide and operate the Forge platform, subject to Atlassian’s applicable policies and platform practices.
Baseline Guard processes Jira information only as necessary to provide the App’s functionality.
This includes:
We do not use customer Jira data for advertising, marketing, or user profiling.
We do not sell customer Jira data or personal information.
Current project assessments and reports are generated deterministically within Atlassian Forge. Baseline checks establish readiness, governance rules determine supported project status, and audience reports are assembled from the same Jira evidence. Current report generation does not send Jira context to an LLM or use AI-generated status or report content.
Baseline Guard distinguishes facts from interpretations and identifies proposed actions as proposals rather than established facts. When required evidence fails or cannot be verified, the app returns BASELINE INCOMPLETE or NOT ASSESSABLE instead of assigning an unsupported project health status.
Baseline Guard does not require external AI API keys and does not intentionally transmit customer Jira issue data to an independently operated external AI service controlled by Levy Automations.
Baseline Guard is built and hosted using Atlassian Forge.
The App does not operate an independently hosted application backend for processing customer Jira issue data.
Atlassian processes information as part of providing the Forge infrastructure and services on which Baseline Guard operates.
We do not sell customer information or share customer Jira data with advertisers or data brokers.
Baseline Guard is built and hosted on the Atlassian Forge platform.
Application processing occurs using Atlassian-hosted Forge infrastructure.
Baseline Guard is designed without external network egress for customer Jira issue data.
Customers should consult Atlassian’s current documentation for information regarding Forge infrastructure, hosting, and applicable data residency capabilities.
Baseline Guard is designed according to least-privilege principles.
Baseline Guard:
Baseline Guard does not claim an independent security certification.
Baseline Guard may process personal information contained in Jira issue data when necessary to generate an assessment, such as an assignee display name associated with an issue.
Baseline Guard does not request access to the customer’s Jira user directory through the read:jira-user scope.
Baseline Guard may retain the requesting user’s Atlassian account identifier and limited personal information incorporated into a generation-job record for the state-based retention period described above. It does not operate a separate externally hosted customer data store.
The organization operating your Jira Cloud site controls the underlying Jira information available to Baseline Guard.
Users with questions concerning information stored in Jira should generally contact their organization’s Jira administrator.
For questions concerning Baseline Guard’s data practices, contact help@levyautomations.com.
We will review and respond to reasonable requests as appropriate.
Baseline Guard is business software intended for use by organizations.
It is not directed to children under the age of 16, and we do not knowingly collect personal information from children through the App.
We may update this Privacy Policy to reflect changes to Baseline Guard, Atlassian’s platform, legal requirements, or our data practices.
When material changes are made, we will update the effective date at the top of this policy and, where appropriate, provide notice through the Atlassian Marketplace or another reasonable channel.
Baseline Guard
Operated by Brian Levy, doing business as Levy Automations
Levy Automations
421 W Riverside Ave #381
Spokane, WA 99201
United States
Email: help@levyautomations.com
For questions about this Privacy Policy or Baseline Guard’s data practices, contact us at the email address above.