Privacy Policy

FeatureBridge is a Jira Cloud app built on Atlassian Forge by YTI Digital OÜ (Estonia). It keeps BDD scenarios (Gherkin) on Jira issues, synchronises them with .feature files in a Git repository you connect, and shows test results you upload from CI. Contact: support@yti.digital.

What the app stores, and where

All data below is stored in your Jira site's Forge app storage, hosted by Atlassian. It follows the data residency of your Atlassian site. We do not run our own servers for the app, and we have no copy of your data.

• Scenarios. The Gherkin text you or your team write on an issue, every saved version (version history), the issue ID, key and project ID, and the time of each save.
• Editors. The Atlassian account ID of the person who saved each version. No names, email addresses or other profile data are stored. Closed Atlassian accounts are anonymised every week through Atlassian's personal data reporting API.
• Git connection (only if an administrator connects a repository).
  • Settings: repository owner and name, branch, folder, the account ID of the administrator who connected it.
  • Secrets, in Forge secret storage: the access token and a webhook secret. They are never shown again after saving.
  • Per-issue sync state: file path, the last synced file version, and, while a conflict is open, the Git version of the scenarios.
• Test results (only if your CI uploads them).
  • Stored per scenario: name, status, the failing step, the first lines of the error message, duration, commit ID and time.
  • The upload key is kept in Forge secret storage.

What leaves Atlassian

• Your own Git repository (GitHub, GitLab or Bitbucket). When a repository is connected, the app reads and writes .feature files and registers one push webhook there, using the token your administrator provided. Scenario text and file paths are sent to that repository. Nothing else is sent.
• Nothing else. No third-party analytics, tracking, advertising or processors. We do not sell or share data.

Logs

The app logs only technical status words, for example "export created" or "import conflict". It never logs scenario text, tokens or keys. Atlassian keeps Forge logs according to its own policies.

Usage counts

The app records anonymous counts of events per Jira site, for example how many scenarios were saved, synced or imported, in Atlassian's developer console. The counts contain no scenario text, names or account IDs, and they never leave Atlassian.

Retention and deletion

• Data stays while the app is installed.
• When the app is uninstalled, Atlassian deletes the app's Forge storage according to its Forge data retention policy.
• An administrator can disconnect the repository at any time. This removes the token, the webhook secret and the settings. Files in your repository are never deleted by the app.

Your rights

For access, correction or deletion requests, contact support@yti.digital or your Jira site administrator. Because the data lives in your Atlassian site, many requests are handled fastest by your administrator together with us.

Security

• Access to scenarios follows Jira permissions. Editing requires the "Edit issues" permission. The project page lists only issues the viewer can see.
• Webhooks are verified with HMAC-SHA256 signatures or a secret token. CI uploads require a secret key, compared in constant time.
• Report security issues to support@yti.digital.

Changes

We will update this page and its date when the app's data handling changes.