Privacy policy: Long URL Field for Jira

Last updated: 28 October 2026

This policy covers the Jira Cloud app Long URL Field for Jira ("the app"), published by Datadelight ("we"). Questions: privacy@accounts.datadelight.co.

What the app does

The app runs on Atlassian Forge. It adds a custom field type, Long URL, that holds a link longer than the 255 characters Jira's own URL field allows, with an optional label. It also adds an administration page (Jira settings > Apps > Long URL Field) that copies links from other fields, sets one link on many work items, and lists and repairs stored values.

The field

A Long URL value is the link, an optional label of up to 100 characters, and the link's host name, which the app works out from the link so that you can search by host. Jira stores this value in your Jira site, like any other custom field.

When someone views or edits the field, the app's code draws the link and the edit boxes in the person's browser, on Atlassian's Forge platform. It checks the length and shape of what is typed there. It makes no request to the app's backend, to Jira or to anywhere else, and keeps nothing. The rules that apply to values set through other routes (Jira's bulk edit, CSV import and the REST API), and the short text shown in lists, are run by Jira itself, inside your site.

What the administration page reads

The administration page is for Jira administrators. When one uses it, the app reads, as that person:

• the list of fields on the site (each field's ID, name and type), to offer the fields to choose from;
• the work items that match the JQL query the person typed, only the ones that person may see, with the values of the chosen fields: for Copy, the chosen URL, multi-line text or Description field and the chosen Long URL field; for Check values and Repair values, the Long URL field; for Set one link on many work items, the work item's key and summary. It reads at most 1,000 work items in a run.

What the administration page changes

When the person confirms an action, the app writes the Long URL field, as the app, on the work items the query found: Copy and Set write a link, Repair corrects spaces and an empty host. It changes nothing else, and a repair never changes the link itself. Jira shows the app as the one who made these changes. Because the write is made as the app, it can reach a work item the administrator could not edit; for that reason only site administrators can open the page.

What the app stores

Nothing. The app has no storage of its own. The reports the page shows (counts, and the keys and stored text of values it could not repair) are shown on the page and not kept.

What the app sends elsewhere

The app uses Atlassian Forge and your Jira site. Its assessed manifest declares no external integrations or analytics services; the app code makes no calls to an external analytics service. The links stored in the field are yours; when a person clicks one, Atlassian shows its own confirmation page and, on Continue, the person’s browser opens the link.

These app-level observations do not establish the platform’s contractual role or an authorised subprocessor list. Platform legal entities, contractual chain, processing locations, transfers and retention remain to be verified before completing an agreement, as described in processing annex C.

Logs

The app writes troubleshooting lines to Atlassian's Forge app logs, one for each action of the administration page, holding the action (copy, check, set or repair), its mode (preview, copy, count and so on) and counts of work items: how many were read, how many would be or were changed, and how many failed.

The log lines carry no links, no JQL, no work item keys, no field values, no account IDs and no text from Jira.

Atlassian holds these logs. We can see them in the Atlassian developer console for 30 days. A site administrator can turn off our access to them in Atlassian Administration (Apps › Connected apps › this app › Logs access).

Personal data

The app stores no personal data. A link or label that someone types into the field may contain personal data; it is stored by Jira in your site, under your control.

Your choices and rights

Your Jira site administrator controls the data in your Jira site, including the values of Long URL fields. Send questions about the app to privacy@accounts.datadelight.co.

Changes

We will post any change to this policy at this address with a new date.