Privacy policy: Record Lock for Jira

Last updated: 30 October 2026

This policy explains what data the app “Record Lock for Jira” (the app), published by Kayabyte, the trading name of Caner Kaya, Stasjonsveien 64, Oslo, Norway, processes when it is installed on an Atlassian Cloud site.

What the app does

Jira admins define lock rules. When a work item matches a rule (it enters a status, gets a resolution or is created), the app stores the values of the chosen fields as the approved values. Later changes to those fields are logged and, when the rule says so, put back to the approved values.

Data the app stores

All data is stored in Atlassian Forge hosted storage for the customer’s Atlassian site:

• Lock rules: rule names, project and work type IDs and names, status IDs and names, field IDs and names, exempt group and project role IDs and names, and settings.
• Snapshots: for each locked work item, its ID and key, the project ID, the rule, the time it was locked, the Atlassian account ID of the person whose action locked it, and the approved values of the locked fields (for example the summary, description, due date or the account IDs in a user field), with a SHA-256 hash. Next to the values, the app stores display text for them: for example version, component, select option and label names, and field names. People in user fields appear only as account IDs. When a work item is unlocked, the account ID of the person who unlocked it and their reason are stored with the snapshot.
• Audit log: for each change to a locked field, the time, work item, rule, the Atlassian account ID of the person or app that made the change, the field, the value they set and the approved value as display text (people only as account IDs), and what the app did.
• A list of the Atlassian account IDs stored above, used for Atlassian’s personal data reporting.
• Status of background tasks (for example how many existing work items were locked).

The app also sets a property on covered projects and locked work items so Jira only sends the app relevant events and admins can search for locked work items. These properties hold only “on” or “yes”.

The app does not store people’s names, email addresses or other profile data; people appear only as account IDs and their names are looked up from Jira when a page is shown.

Data the app reads but does not store

To check changes and show its pages, the app reads work item fields, projects, statuses, project roles and their members, group membership of the person who made a change, and the account type (person or app). This data is used during processing and is not kept, except for the values listed above.

Where data is processed

All processing happens on Atlassian’s Forge platform. The app makes no calls to servers outside Atlassian, and no data is sent to Kayabyte or to any third party.

Personal data and closed accounts

The app reports the Atlassian account IDs it stores to Atlassian every week, as Atlassian requires. When Atlassian reports that an account has been closed, the app replaces that account ID with “deleted user” in the audit log and in snapshots. Snapshots that contained the account ID are sealed again with a new hash, and the time this happened is recorded with the snapshot.

Retention and deletion

Data is kept while the app is installed, so the audit trail stays complete. Deleting a rule ends its locks but keeps their snapshots and audit entries as history. When the app is uninstalled, its Forge storage is removed by Atlassian in line with Atlassian’s Forge data retention rules. Customers can ask us to confirm deletion by contacting support.

Logs

For troubleshooting, the app writes operational logs on the Forge platform containing work item IDs, counts, error messages, API status codes and endpoint names, never field values. These logs are kept by Atlassian under its Forge log retention rules.

Your rights

For questions about this policy or about data the app processes, contact support@kayabyte.dev.

Changes

We will update this page if the app’s data handling changes. The date at the top shows the latest version.