Privacy policy: On-Call Pay

Last updated: 12 November 2026

This policy explains what data the app “On-Call Pay: Standby Hours & Payroll Reports for JSM” (the app), published by Kayabyte, the trading name of Kaya Byte (sole proprietorship of Caner Kaya, org.nr 938 851 883), Stasjonsveien 64, Oslo, Norway, processes when it is installed on an Atlassian Cloud site.

What the app does

The app reads Jira Service Management on-call schedules (rotations and the final on-call timeline) with the access of the person using it, and calculates on-call hours and standby pay per person from rates the customer enters. It does not change schedules, alerts or anything else in Jira.

Data the app stores

The app stores its data in Atlassian Forge hosted storage for the customer’s Atlassian site:

• Pay plan: time zone, currency, public holiday location, working days, office hours and hourly rates.
• Snapshot settings: whether monthly snapshots are on, the chosen schedules, the Atlassian account ID of the admin whose access the monthly run uses, and the last run’s status.
• Monthly snapshots (up to 24): for each person on call, their Atlassian account ID and display name, hours and amounts per category, and the names of the schedules included.

Reports run on demand are not stored. The app does not store alerts, email addresses or avatars.

Data sent outside Atlassian

None. The app runs on Atlassian Forge and only calls Jira and Jira Service Management APIs of the customer’s site. It does not send data to Kayabyte or any other party.

Personal data and account closures

Account IDs and display names are personal data. The app reports the account IDs it stores to Atlassian’s personal data reporting API every week. When Atlassian reports an account as closed, the app replaces that person in saved snapshots with “Closed account”, and turns monthly snapshots off if the closed account is the admin the monthly run acts as.

Who can see the data

Only Jira admins can change the pay plan and snapshot settings. Reports and snapshots can be seen by Jira admins and by people with the app’s “On-Call Pay: view reports” global permission. Reports read schedules with the viewer’s own access in Jira Service Management.

Retention and deletion

Settings and snapshots are kept while the app is installed; snapshots older than 24 months are deleted. When the app is uninstalled, its Forge storage is deleted by Atlassian according to Forge’s data retention rules.

Logs

For troubleshooting, the app writes operational logs on the Forge platform with error types and status codes, without account IDs, names, hours or amounts. Atlassian keeps these logs under its Forge log retention rules.

Data processing agreement

Customers who need a data processing agreement can request one at support@kayabyte.dev.

Your rights

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

Changes

Changes to this policy are published on this page with a new date.