Privacy policy: Fakturer for Tripletex

Last updated: 11 November 2026

This policy explains what data the app “Fakturer: Invoice Worklogs to Tripletex for Jira” (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 the time logged in Jira for the work items an admin chooses, prices it with hourly rates the customer enters, and creates orders in the customer’s own Tripletex company. It never creates invoices, books vouchers or deletes anything in Tripletex.

Data the app stores

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

• Settings: the Tripletex environment, currency, rounding, due days, the VAT type for lines, non-billable labels and worklog tag.
• Mappings: a name, a JQL query, the customer’s identifier and name in Tripletex, hourly rates, per-person hourly rates (keyed by Atlassian account ID), an optional product identifier and a reference text.
• Tripletex employee token: kept in Forge secret storage, used only for calls to Tripletex and never shown again.
• Previews: for 14 days, the order lines of a preview: line text (work item key and summary, a person’s display name or a date, depending on the line setting), hours, rates, amounts and the IDs of the worklogs on each order. Previews expire automatically.
• Billed worklogs: the ID of every worklog put on an order, with the order it belongs to, so the same worklog is never billed twice.
• Order history: for each order, the mapping and customer name, period, hours, amount, currency, the order’s number and link in Tripletex, and the Atlassian account ID of the person who created it.

The app does not store worklog comments, email addresses or avatars.

Data sent outside Atlassian

The app sends data only to the Tripletex company the customer connects:

• Tripletex (tripletex.no, or api-test.tripletex.tech for its test environment): to list customers, products and VAT types, and to create an order with the customer, order date, due days, reference text and the order lines (line text, hours, hourly rate, VAT type and optional product).

Line text can include work item keys and summaries and, with the “one line per person” setting, people’s display names. Choose the line setting with that in mind. The app does not send data to Kayabyte or any other party.

Personal data and account closures

Account IDs are personal data. The app reports the account IDs it stores to Atlassian’s personal data reporting API every week. When Atlassian reports that an account has been closed, the app removes that person’s personal hourly rate and replaces their account ID in the order history with “closed account”.

Who can see the data

Only Jira admins can change settings and mappings. Previews and orders can be made by Jira admins and by people with the app’s “Fakturer: create Tripletex orders” global permission. Those people see the preview for every active mapping, including work item summaries and people’s names from projects they cannot browse in Jira. Orders in Tripletex are visible according to Tripletex’s own access rules.

Retention and deletion

Settings, mappings, billed worklogs and the order history are kept while the app is installed. Previews are deleted after 14 days. When the app is uninstalled, its Forge storage is deleted by Atlassian according to Forge’s data retention rules. Orders already created in Tripletex stay there; delete them in Tripletex if needed.

Logs

For troubleshooting, the app writes operational logs on the Forge platform with error types and status codes, without account IDs, rates 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.