Privacy policy: Fakturer for Fortnox

Last updated: 12 November 2026

This policy explains what data the app “Fakturer: Invoice Worklogs to Fortnox 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 customer invoices that are not booked in the customer’s own Fortnox company. It never books, sends or deletes anything in Fortnox.

Data the app stores

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

• Settings: the connected Fortnox company’s name and database number, currency, rounding, due days, an optional sales account, non-billable labels and worklog tag.
• Mappings: a name, a JQL query, the customer’s number and name in Fortnox, hourly rates, per-person hourly rates (keyed by Atlassian account ID), an optional article number and a reference text.
• 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 invoice. Previews expire automatically.
• Billed worklogs: the ID of every worklog put on an invoice, with the invoice it belongs to, so the same worklog is never billed twice.
• Invoice history: for each invoice, the mapping and customer name, period, hours, amount, currency, the invoice’s number in Fortnox, and the Atlassian account ID of the person who created it.

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

Fortnox sign-in

Fortnox requires each person who creates invoices to connect their own Fortnox user. The sign-in uses OAuth 2.0 through Atlassian Forge; the access and refresh tokens are held by Atlassian’s Forge platform for that person and are not visible to the app’s author.

Data sent outside Atlassian

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

• Fortnox (apps.fortnox.se for sign-in, api.fortnox.se): to read the company’s name and database number and the signed-in user’s Fortnox user ID and name, to list customers and articles, and to create an invoice that is not booked with the customer, invoice date, due date, currency, reference text, Fakturer’s own reference for the invoice, and the invoice rows (row text, hours, hourly rate, and article or sales account).

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 invoice history with “closed account”.

Who can see the data

Only Jira admins can change settings and mappings. Previews and invoices can be made by Jira admins and by people with the app’s “Fakturer: create Fortnox invoices” 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. Invoices in Fortnox are visible according to Fortnox’s own access rules.

Retention and deletion

Settings, mappings, billed worklogs and the invoice 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. Invoices already created in Fortnox stay there; delete or credit them in Fortnox 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.