Privacy policy: Fakturer

Last updated: 11 November 2026

This policy explains what data the app “Fakturer: Invoice Worklogs to Fiken 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

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 invoice drafts in the customer’s own Fiken account. It never sends, books or deletes invoices.

Data the app stores

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

• Settings: the chosen accounting system, Fiken company name and identifier, currency, rounding, due days, VAT and income account choices, non-billable labels and worklog tag.
• Mappings: a name, a JQL query, the customer’s identifier and name in the accounting system, hourly rates, per-person hourly rates (keyed by Atlassian account ID), an optional product identifier and a reference text.
• Previews: for 14 days, the invoice 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 draft. Previews expire automatically.
• Invoiced worklogs: the ID of every worklog put on a draft, with the draft it belongs to, so the same worklog is never invoiced twice.
• Draft history: for each draft, the mapping and customer name, period, hours, amount, currency, the draft’s reference and link in the accounting system, and the Atlassian account ID of the person who created it.

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

Fiken sign-in

Fiken requires each person who creates Fiken drafts to connect their own Fiken 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 Fiken account the customer connects:

• Fiken (api.fiken.no, fiken.no): to list companies, customers and products, and to create a draft with the customer, invoice date, due days, reference text and the invoice lines (line text, hours, hourly rate, and VAT or 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 draft history with “closed account”.

Who can see the data

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

Retention and deletion

Settings, mappings, invoiced worklogs and the draft 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. Drafts already created in the accounting system stay there; delete them in that system 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.