Privacy policy for the apps

The short version

The apps run on Atlassian Forge, inside your own Atlassian site. They read Jira or Confluence data for the person using them, store their own records in Forge app storage on your site, and send nothing anywhere else. I don't receive or store any of your data. No external servers, no analytics, no cookies.

Who is responsible

The vendor of the apps is Toine.com B.V. in Utrecht, the Netherlands, Chamber of Commerce 87544903. That's my company. For the data the apps process inside your site, your organisation is the controller and Atlassian is the hosting provider under the Atlassian Cloud Terms of Service. Because the apps send no data out, Toine.com B.V. never acts as a processor of your content.

What the apps read and store

The apps are read-only. They don't write to your Jira issues and they don't edit Confluence page bodies. They ask only for the scopes listed below, and they read within the permissions of the person using the app. Each list is the one on that app's documentation page. Nothing is stored outside Atlassian. The apps don't call any server other than Atlassian's own APIs.

Release Readiness for Jira

Reads Jira work (issues, versions, components and links) and Jira users (display names of accountable owners and signers, and who may sign through project roles). Stores criteria (JQL text, thresholds, accountable role), the daily state of each criterion per release for 90 days, the last 50 snapshots, decision records (account ID, display name, role, time, reasoning, conditions) and personal display preferences.

Defect Health for Jira

Reads Jira work (defects, their fields, versions, components and changelog) and Jira users (assignee display names). Stores per-project settings (defect types, a custom field id, triage days, age boundaries, phase keywords) and one small record per day with the open count, median age, triage breaches, escaped and reopened counts. No issue content.

Exploratory Sessions for Jira

Reads Jira work (issue titles and status for the keys a charter or finding references) and Jira users (tester and reviewer display names). Stores charters, sessions (tester account ID, start and end time, notes, findings with optional Jira keys, debrief) and settings per project. No Jira issue content. It does not create or change a Jira issue.

Test Summary Report for Jira

Reads Jira work (the issues in scope, their links, status, priority and components) and Jira users (author and signer display names). Stores reports (scope, computed numbers, narrative, status, signer account ID and display name, time, version) and per-project settings.

AI System Register for Jira

Reads Jira work (titles and status of the issues an entry references) and Jira users (owners and reviewers by display name). Stores the register: systems, classification and rationale, obligations with status and notes, evidence links and Jira keys, review dates and history, owner account IDs and display names.

Throughput and Cycle Time for Jira

Reads Jira work (work items, their fields and their changelog, to compute throughput, cycle time and lead time) and Jira users (assignee display names). Stores the chosen project, window and grouping per project. No work item content.

Work Item Aging for Jira

Reads Jira work (work items, their fields and their changelog, to work out when each item started and how long it has been running) and Jira users (assignee display names). Stores the chosen project, window and grouping per project. No work item content.

Cumulative Flow Diagram for Jira

Reads Jira work (work items and their changelog, to replay status transitions day by day) and Jira users (assignee display names). Stores the chosen project, window and grouping per project. No work item content.

Created vs Resolved for Jira

Reads Jira work (work items and their changelog, to count what was created and what reached a done status in each period) and Jira users (assignee display names). Stores the chosen project, window and grouping per project. No work item content.

Test Plan and Test Report for Confluence

Reads Confluence users (approvers by name and display names), Confluence content summary (the page title in the global list) and Jira work (to count the issues in a JQL scope). Stores plans and reports (sections, JQL scope and stored counts, version, status, approvers with account ID, display name and time, history). No page content. It does not edit a Confluence page body or a Jira issue. Jira counts need the app installed in Jira on the same site.

Decision Log for Confluence

Reads Confluence users (owners by name and display names) and Confluence pages (page titles in the register, and to search users). Stores decision records (title, status, date, owner account ID and display name, context, options, decision, consequences, tags, links, supersedes chain, history) per log, with the page ID the log lives on. It does not edit the page body.

RAID Log for Confluence

Reads Confluence users (owners by name and display names) and Confluence pages (page titles in the register, and to search users). Stores RAID items (type, title, owner account ID and display name, status, probability, impact, dates, response, updates with author and time) per log, with the page ID the log lives on. It does not edit the page body.

Lessons Learned for Confluence

Reads Confluence users (owners by name and display names) and Confluence pages (page titles in the register, and to search users). Stores lessons (title, kind, status, source, owner account ID and display name, three sections, tags, votes by account ID, applied-in entries, history) per log, with the page ID the log lives on. It does not edit the page body.

How long it's kept

The data stays on your site as long as the app is installed. When you uninstall the app, Atlassian removes its storage under the Forge storage lifecycle. Release Readiness for Jira, while it is installed, keeps the daily state of each criterion per release for 90 days and the last 50 snapshots. The other apps' documentation does not state a shorter retention period than the life of the installation.

Who can see it

Only people with access to your Atlassian site, within their Jira or Confluence permissions. I have no access to your site or to the app's storage on it. What Atlassian itself can access is covered by your agreement with Atlassian.

Security

The apps are Forge apps. They run in Atlassian's sandboxed runtime, use Atlassian's authentication and authorisation, and go through Atlassian's security review before they get listed. How I secure the code, the accounts and the releases is on the security policy for the apps. If you find a security issue, mail the support address below. Those get priority.

This website

toine.com is a static site on Vercel. It sets no cookies, has no analytics and loads nothing from third parties. Vercel keeps standard server logs (IP address, requested page, time) to run the service. This page is the privacy notice for that site as well as for the apps.

Your rights

Requests about personal data inside your Atlassian site go to your own site administrator. They can handle those directly in the app, in Jira or in Confluence. Questions about this policy can go to the address below.

Changes

Version 2, 26 October 2026, covers all thirteen apps. Version 1, 21 September 2026, described Release Readiness for Jira only. Later changes go on this page with a new version number and date, and on the changelog. Bigger changes I also mention in the app's release notes on the Marketplace.

Contact

Toine.com B.V., Utrecht, the Netherlands. Email contact@toine.com.