Legal

Privacy Policy

Last updated: 27 October 2026 Controller for this app: Miftode Vasilica, private individual, Romania. Contact: [email protected].

Short version

Your scenarios, settings and test results are stored in your Atlassian site's Forge storage, on Atlassian's infrastructure. We run no servers and no database of our own.
We do not see your data, sell it, or use it for marketing.
Data leaves Atlassian only if an admin turns on:
Git sync: to the one repository a project admin configures (GitHub, GitLab.com or Bitbucket Cloud);
AI drafts: to Anthropic, with your organisation's own API key, only for the story a user asks about.

What the app stores (in Forge storage on your site)

Data	Why	Where
Gherkin scenarios per issue, with the time of the last change	The core feature	Forge key-value storage
Step usage counts per project	Step suggestions	Forge key-value storage
Git connection (provider, repository, branch, folder)	Git sync	Forge key-value storage
Git access token, Anthropic API key, hash of the CI token	Authentication	Forge secret storage (encrypted, never shown again)
Last sync state and last test results per issue	Sync and results display	Forge key-value storage
Test status label on each issue	Shown in the issue glance	A Jira issue property

We do not store Atlassian account IDs, names, email addresses or other personal data. So that only the person who asked for an AI draft can open it, the draft is stored with a one-way fingerprint of their account ID (salted with the draft's random ID), and it is deleted when they open it or expires after 24 hours (details below). Scenario text may contain whatever your users type into it.

What leaves Atlassian, and when

Git sync (off until a project admin connects a repository). The scenario text of an issue is read from and written to <folder>/<ISSUE-KEY>.feature in the configured repository, using the token the admin provided. Commit messages contain only the issue key.
AI drafts (off until a Jira admin opts in and adds an API key). When a user clicks "AI draft", the issue key, summary, description (first 30,000 characters, fewer for very long stories in non-Latin alphabets), existing scenarios of that issue and up to 60 common step phrases of the project are sent to Anthropic's API (api.anthropic.com). Anthropic processes it under the terms between your organisation and Anthropic.
CI test reports come into the app through a Forge web trigger URL protected by a secret token. We keep only the latest result per issue: scenario names, pass/fail status, the failing step, the first 500 characters of each failure message, and the build link if your CI sends one.

The app declares exactly these hosts in its Forge manifest: api.github.com, gitlab.com, api.bitbucket.org, api.anthropic.com. It cannot contact anything else.

Sub-processors

Who	For what	Chosen by
Atlassian	Hosting of the app and its storage	Atlassian (Forge)
GitHub / GitLab / Atlassian Bitbucket	Git sync	You, only if connected
Anthropic	AI drafts	You, only if switched on, with your key

Retention and deletion

Text you typed in the scenario editor but did not save is kept in your own browser's local storage, so it is not lost if you leave the story. It is removed when you save or press Discard. It never leaves your browser.
Data stays while the app is installed. Deleting scenarios in the editor deletes them from storage.
Deleting an issue in Jira deletes what the app stored for it: its scenarios, CI test results, Git sync state and any unread AI draft. Sub-tasks deleted together with their parent are cleaned up too. Files in your Git repository are not touched.
Deleting a project for good (emptying it from Jira's trash) deletes what the app stored for it: its stories' data, its step suggestions and its Git connection, including the token. Stories that were moved to another project keep their data under their new key.
Disconnecting Git deletes the stored Git token. Deleting the AI key removes it and turns AI off.
An AI draft runs in the background, so the request (the story text listed above) and the answer are kept in Forge storage while it runs. The request is removed as soon as the AI call starts; the answer is removed when the person who asked opens it. If nobody opens it, it expires after 24 hours and Forge storage deletes it (Atlassian says the deletion itself can take up to 48 hours more); a new AI draft on the same story replaces it sooner.
When you uninstall, Atlassian deletes the app's Forge storage according to Atlassian's Forge data retention policy.

Your rights (GDPR)

You can ask for access to, correction or deletion of personal data related to the app by writing to [email protected]. Because data sits in your own Atlassian site, most requests can be handled directly by your Jira admins. We answer within 30 days.

Changes

We will post changes here and note the date at the top. Material changes are announced on the Marketplace listing.