Privacy Policy – Agent Ready for Jira

Data Privacy & Security – Agent Ready for Jira

Agent Ready for Jira is built by Simplify on the Atlassian Forge platform. Its code and data run on Atlassian’s infrastructure, in your Atlassian site. The app makes no calls outside Atlassian: no data leaves Atlassian through Agent Ready, and Simplify has no server that receives it.

What the app reads

• Issues — summary, description, links, the latest comments, fields, development information — and projects, workflows’ statuses and people, read from Jira as the person who opens a page, uses Rovo or runs a coding agent, with that person’s permissions. Nobody sees more through Agent Ready than in Jira.
• Confluence pages linked to an issue or naming its key, only where the app is also installed in Confluence, read as the person for a coding agent’s brief, cut to 4,000 characters each and not stored.
• Work that no person starts — keeping readiness fresh after an edit, the workflow validator, a sprint start — reads the issue as the app. What it reads this way is shown to nobody.

Passwords, keys and tokens found in an issue are shown only as their type and a mask, and are never stored or logged.

What the app writes in Jira

• Readiness numbers on each issue (ready, score, checks passed) as an issue property, for JQL and the workflow validator; the roles and skills chosen for an issue as issue properties.
• Comments it was set up to post: the brief at a handoff, giving an unready issue back, a sprint-start warning, an agent’s question, receipt or release.
• Changes a person makes through the app, as that person: inserted description sections, sub-tasks, assignments, transitions, sample issues.

What the app keeps (Forge storage, inside your Atlassian site)

• Rules and settings of the site and of each project — rules, headings, the agent brief, roles, skills, the repository map, agent accounts, prices and budgets — with the account ID of who saved them.
• The last readiness score of each issue, numbers only, kept for 30 days.
• The agent report: per handoff to an AI agent — project, issue, agent account ID, score, the checks missing, times and outcome — and per work receipt the counts of proven criteria, cost and tokens. Kept for 365 days.
• An agent’s run on an issue, while it lasts: the claim (which agent holds it), the agent’s questions and people’s answers with their account IDs, the plan and its decision, and the progress steps. Emptied when the agent finishes, and expires 30 days after its last change.
• Work receipts: the newest five per issue — what the agent changed, its tests and risks, the pull request address, and each acceptance criterion with its test. Kept for 365 days.
• Waivers: per waived check, the reason and the account ID of who waived it. Names are never stored: the name is read from Jira when someone looks.
• The Backlog X-ray: a daily trend point (at most 90) and, per Jira admin, the last handoff shown at the top — the issue key and its numbers, never the summary.
• Small counters: when the app was installed, the setup steps marked done, MCP tool use per agent name per month, and per person when to ask for a review.

When an issue is deleted, everything the app kept about it — its score, run, receipts and waivers — is deleted too. Found passwords and keys are never stored.

Closed accounts

Every day the app asks Atlassian, through Forge’s personal data reporting, which of the accounts it keeps a per-person record for were closed, and deletes their records. Account IDs inside rules, runs and the agent report go with those records when they expire.

Rovo and coding agents

• Rovo is Atlassian’s AI, used only when a person opens the Agent Ready agent on a site with Rovo. It receives the issue’s summary, description and newest comments with every password and key masked and every line that looks like an instruction to an AI agent removed, plus the agent brief. Rovo asks the person before every change, and the change is made as them.
• MCP tools for coding agents are off until a site admin turns them on. A coding agent your team runs — such as Claude Code or Cursor — then receives, as the person it signs in as, the issue with keys masked and hidden instructions removed, the brief, skills, linked issues and linked pages. That agent and its model are chosen by your team and are outside Agent Ready.
• The app’s own checks use no AI.

Data Access & Sharing

• Your data is never shared with third parties by Simplify, and Simplify cannot access it.
• The app’s logs record only what failed and an error’s name — never issue text, briefs, account IDs or found keys.

Uninstalling

When the app is uninstalled, Atlassian deletes its Forge storage under Atlassian’s Forge data retention. Issue properties and comments the app wrote stay in Jira as part of the issues.

Updates to the Policy

We may update this privacy policy to reflect changes in the app or legal requirements. Any updates will be posted on this page and take effect immediately.

Consent

By using Agent Ready for Jira, you agree to this privacy policy and our End User License Agreement (EULA). For privacy-related inquiries, contact us via our Support Desk.

For more information, please visit Atlassian’s Privacy Policy.