Privacy notice: Due Date Fields for Jira

Effective 2026-10-01. Publisher: Sidecar Tools (support@sidecartools.com).

What the app reads. For each work item: its due date, resolution date, status category, status-category change date, and the change history of the due date field only, plus the site's field list, using the read:jira-work scope. It does not read summaries, descriptions, comments, attachments or people.

What the app writes. Five app-owned custom field values on work items (write:app-data:jira): Resolved late, Days late at resolution, Due date change count, Original due date and Due date slip (days).

Where data lives. Entirely inside your Atlassian site. Field values are stored by Jira as issue fields. The app stores only its own field ids and a backfill timestamp in Forge Key-Value Storage (storage:app). Nothing is sent outside Atlassian's infrastructure; the app has no external egress and no servers of its own. The app does not log field values or dates.

Personal data. None. The values are dates, numbers and a yes/no label. The change history is read only for due date values; who made the change is not used or stored.

Who can see the fields. The same people who can see the work item that carries them.

Retention. Values remain on work items until the app is uninstalled; uninstalling removes the fields and their values per Jira's handling of app-owned fields.

Analytics and tracking. None.

Contact. support@sidecartools.com.