Skip to main content

Data security and privacy

This page describes what FieldCraft stores, where it runs, what leaves your site, and who can see what.

Use it for your security review, together with the privacy and security tab of the Marketplace listing.

Where the app runs​

FieldCraft runs on Atlassian Forge. Its code and its storage are on Atlassian's infrastructure.

FieldCraft calculates every value on the server, as the app.

Your browser shows values and settings, but never calculates or writes a value.

The one connection outside Atlassian is error reports and usage counts to Sentry. See Error reports and usage counts.

What the app stores​

FieldCraft keeps its data in Forge hosted storage, inside your site's app installation.

DataWhat it holdsHow long
Work calendarsName, working hours, breaks, holidays and time zoneUntil you delete the calendar
Calculation settingsThe three switches on the Settings tab, and which fields a Jira admin acknowledgedUntil you change them
Last calculationFor each field and work item: the value, when and why it was calculated, a fingerprint of the configuration, and the last error message, up to 300 characters365 days
Counting stateFor time-based values: where the count started, so the hourly refresh needs no Jira readWhile the value keeps counting
Hourly usagePoints used, and values recalculated, written, failed and waiting, per hour2 days
ReindexesThe fields, the JQL, the progress, and failed work items with their key and error message30 days
Suggested updatesWhich field or calendar changed, and when30 days
ActivityOne row per refresh or reindex, with its fields and JQL7 days for refreshes, 90 days for reindexes
Refresh failuresThe work item, the field, the reason and Jira's message, up to 200 characters7 days
AI assistant plansThe planned change, and the account ID of the Jira admin who made it15 minutes
Working dataThe list of FieldCraft fields and their contexts, status names, and short-lived marks that prevent duplicate work10 minutes to 1 day

Jira itself stores the calculated values, as the values of the fields.

Jira also stores each field's configuration, as part of the field's context.

FieldCraft doesn't keep copies of work items, comments, attachments or work logs.

It keeps only what it calculates.

A calculated value can contain text from a work item, for example a Previous Value field.

Where a value is a person, FieldCraft stores their account ID.

In your browser​

Your browser keeps a few conveniences in local storage. Examples are the tab you used last, and the last JQL you entered.

They never leave your browser.

How data flows​

  1. A work item changes, and Jira sends FieldCraft an event through Forge.

  2. FieldCraft's Forge functions read the work item, its history and related work items from Jira, as the app.

  3. FieldCraft writes changed values to its fields. The writes add no history entry and send no notifications.

  4. When someone opens a work item, Jira asks FieldCraft for the value and stores the answer.

  5. Admin pages and field views run inside Jira, hosted by Forge, and call FieldCraft's functions through Forge.

  6. AI clients reach FieldCraft's tools through Atlassian's MCP service, after the person signs in.

  7. FieldCraft's functions send error reports and usage counts to Sentry, in the US.

    Browsers never contact Sentry.

  8. Nothing else leaves Atlassian.

App permissions​

FieldCraft asks Atlassian for these scopes.

It doesn't ask for write:jira-work, so it writes only to its own fields.

ScopeUsed for
read:jira-workReading work items, their history, comments, links, work logs and children, and running JQL searches and Jira expressions
manage:jira-configurationReading and saving FieldCraft fields' configurations, writing calculated values, and creating, renaming and trashing fields through AI assistants
manage:jira-projectAdding a field to screens through AI assistants
read:jira-userReading people for user values, and checking whether a person may browse a work item
storage:appForge hosted storage for the data above

Error reports and usage counts​

FieldCraft sends error reports from its own code, and usage counts, to Sentry, hosted in the US.

We use them to find and fix problems.

WhatDetails
SentThe app's own errors: type, a shortened message with values removed, and where in the app's code it happened. Also the app version, browser and operating system, which FieldCraft page or function was in use, your site's ID and a pseudonymous user ID. Usage counts: admin actions, and daily totals of recalculations, refreshes, reindexes and fields by type
Never sentField values, Jira expressions, JQL, work item content, work item keys and IDs, status, field, space and user names, comments, work logs, field configurations, work calendars, Jira's response bodies, storage contents, email addresses, account IDs and IP addresses

How it works:

  • The pseudonymous user ID is a salted hash of your site's ID and the account ID, made on the server.

  • Daily totals carry no user at all.

  • Expected outcomes aren't reported. Examples are Jira's rate limits, missing permissions and errors in your own JQL or expressions.

  • The hourly budget and an inactive license aren't reported either.

  • Sentry keeps the data according to our plan's retention, 90 days by default.

Turn them off​

FieldCraft has no setting of its own for this. A site admin or organization admin turns it off in Atlassian Administration:

  1. In Jira, go to Settings (βš™) > Marketplace apps > Manage apps, and select Take me there. Connected apps opens in Atlassian Administration.

  2. Find FieldCraft Custom Fields for Jira, and select View app details.

  3. Under Analytics access, select Disable analytics access.

Result: FieldCraft can no longer send error reports and usage counts to Sentry. Calculation works as before.

Data residency​

Forge hosted storage keeps FieldCraft's data in the same location as your Jira site.

It moves with the site when an admin changes its data residency. See Atlassian's Forge data residency page.

Error reports and usage counts in Sentry are in the US, outside your site's data residency.

Encryption and deletion​

Traffic between Jira, Forge and Sentry uses HTTPS.

Atlassian encrypts Forge hosted storage at rest.

When you uninstall FieldCraft, Atlassian keeps its storage for 28 days and then deletes it.

A reinstall starts with empty storage.

If you reinstall within 21 days, contact us through the support portal.

With your consent, we can ask Atlassian to restore the data.

Fields that read with the app's access​

Jira expressions, Parent Field and Rollup fields read other work items with the app's access.

That access can include spaces and work items that the person viewing the field can't see.

Everyone who can see the work item sees the stored value.

So a Jira admin must acknowledge each such field before FieldCraft calculates it. See Acknowledge app access.

AI assistants​

FieldCraft calls no AI model, and sends no data to a model provider.

AI clients other than Rovo can use FieldCraft's tools only after an admin enables them in Atlassian Administration.

Each tool checks the person's permission, then reads Jira as the app.

The results go to the AI client the person uses.

What that client does with them is up to that service. See How the tools reach your data.

Subprocessors​

SubprocessorPurposeData
AtlassianHosting, storage and compute (Forge)All app data
Functional Software, Inc. dba Sentry, USError reports and usage countsYour site's ID, a pseudonymous user ID, technical error details and counts

Report a vulnerability​

Report a vulnerability or ask a security question through the support portal.