Privacy notice

Provider and contact

Claervo provides Claervo Undo for Jira. Privacy and data-rights requests can be sent to support@claervo.com.

Product boundary

The app runs entirely on Atlassian Forge inside your Jira Cloud site. Compute, Custom UI assets, Forge SQL and Forge storage run in Atlassian's environment in your site's region. There is no Claervo-operated remote backend, external database, analytics endpoint, advertising technology or AI processing, and no data is sent to Claervo or any third party.

Data the app reads

Through Jira's product events and the Jira Cloud REST API as the app, only to keep a mirror that can restore or undo changes.

• Work items in the projects of your site: all fields (summary, description, labels, priority, dates, people fields, custom fields), comments, worklogs, links and attachment metadata (file names, sizes, types). Attachment file content is never read or stored.
• Change history as Jira reports it in events: which field changed, the previous and new value, when, and the Atlassian account ID of the actor (a person, an automation rule or an app).
• Display names and account types of accounts that appear as actors, reporters, assignees or comment authors, so administrators see names instead of IDs.

Data the app stores

App data is stored in Forge SQL and Forge storage for your installation, in your site's region.

• A compressed copy (mirror) of each protected work item's fields, comments, worklogs and links, taken when the item is created or when a rich field such as the description or a custom field changes.
• A change ledger: one line per field change, deletion, comment, worklog, link or attachment event, with the actor's account ID and the previous and new values.
• Deleted work items and the data needed to restore them.
• Restore and undo records: who requested them, when, what was created and what was skipped.
• Actor display names and account types cached from Jira.
• Settings chosen by administrators (retention period).

Personal data

Personal data therefore includes work item content written by your users, Atlassian account IDs and display names. No e-mail addresses or other profile attributes are stored. Customer data is never used to train an AI model.

Retention and deletion

Administrators choose the retention period (30, 90 or 180 days; 90 by default). A daily job deletes mirror snapshots, ledger lines, deleted work items and restore records older than that. Uninstalling the app removes all of its Forge SQL and Forge storage under Atlassian's platform rules.

Who can see the data

Only Jira site administrators can open the Claervo Undo page. Restores and undos are performed as the app user, only after an administrator confirms the preview, and every one is recorded.

Rights

Customers can shorten the retention period, run the clean-up on demand or uninstall the app. Access, correction, restriction or deletion requests can be sent to the customer organization or to support@claervo.com; we may coordinate with the relevant site administrator to verify authority.