Privacy notice: Last Comment Fields for Jira

Effective 2026-09-16. Publisher: Sidecar Tools (support@sidecartools.com).

What the app reads. Issue comments (body, author, created date, visibility), issue ids, and the site's field list, using the read:jira-work scope.

What the app writes. Five app-owned custom field values on issues (write:app-data:jira): a 255-character plain-text excerpt of the latest comment, the author's account id, the comment date, a visibility label, and a count.

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.

Who can see the fields. The same people who can see the issue. Note: the "Last comment" excerpt is an issue field and follows issue permissions, not comment visibility restrictions. If your team restricts individual comments to roles or groups, hide the "Last comment" field from screens and filters where those users work, or rely on the "Last comment visibility" field, which contains only the label restricted/internal/public/none.

Retention. Values remain on issues 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.