Privacy policy

Last updated 9 August 2026

This policy explains what data Eriksen Labs handles, and what it does not. It covers our Atlassian Marketplace apps and this website.

Eriksen ENK, trading as Eriksen Labs, registered in Norway under organisation number 937 027 834. We are the data controller for the limited processing described below.

Contact: [email protected]

The app collects no data and transmits nothing to us. This is a design decision, not a policy promise, and it can be verified:

• The app requests no Atlassian permission scopes. You can confirm this on the install screen — it has no access to your Confluence content, users, or spaces.
• Diagrams are rendered entirely in your browser. Diagram text is never sent anywhere for processing.
• Your diagram content is stored by Atlassian as part of the Confluence page it lives on. We never receive, store, or have access to it.
• We operate no servers that receive app data. There is no backend to breach.
• The app sets no cookies and contains no analytics, tracking, or third-party scripts.

Atlassian's handling of your Confluence content is governed by Atlassian's privacy policy.

This app does store personal data, inside your own Atlassian instance. We say so plainly because the alternative — a blanket claim that none of our apps store anything — would be untrue.

What it stores, and why:

• The Atlassian account ID of the customer who creates a schedule or a template. A scheduled request has to be raised as the person who asked for it rather than as the app, which is only possible if the app remembers who they are.
• The details of the request being repeated — its field values and the answers of any attached form. Those answers are whatever the customer typed, which often includes names, phone numbers and email addresses. They are kept so the repeated request can reproduce the original.

All of it lives in Forge storage, which is Atlassian's own infrastructure, scoped to your installation. Eriksen Labs cannot read it. We operate no servers that receive it and have no mechanism to retrieve it. It is not transmitted anywhere outside Atlassian.

How long it is kept. A schedule's details are stored until the customer cancels it or an admin stops it; a template's until the customer deletes it. Uninstalling the app removes all of it. The app reports the account IDs it holds to Atlassian each week and erases everything associated with an account once Atlassian reports that account closed.

An admin can see and stop every schedule in their own project, and a customer can see, pause and cancel their own from the portal at any time.

The scanner makes no network requests at all. It reads your code on your own machine and writes a single HTML file beside it. There is no account, no telemetry, no usage reporting and no update check. You can disconnect from the network and it works unchanged — which is the honest way to verify this claim, and better than taking our word for it.

The pull request check runs inside your own CI runner. Your source code is read there and never leaves it. Where a repository is private and a licence key is configured, the Action makes exactly one outbound request: it sends the licence key, and nothing else, to Polar to ask whether it is valid. No repository name, no file, no finding and no identity travels with it.

The number of active committers used to decide your pricing tier is computed from your own git history inside your own runner, used there, and discarded. It is not transmitted to us or to anyone else.

Because none of your content reaches us, we hold no personal data from your use of this product and there is nothing for us to lose, sell or be compelled to hand over.

Payments are handled by Polar as merchant of record. They collect what a payment requires — your name, email, billing address and payment details — as an independent controller under their own privacy policy. We never see your card details. What reaches us is your email address and what you bought, which is what we need to support you and to issue your licence key.

This site is static and sets no cookies. It is hosted on Cloudflare Pages. Cloudflare processes technical information such as IP addresses in server logs to deliver the site and protect against abuse, acting as our processor. We use no analytics on this site.

If you email us, we receive your address and whatever you choose to include. Our mail is hosted by Zoho, acting as our processor. We use support correspondence only to answer your question, and keep it for up to 24 months so we can follow up on recurring issues. We do not use it for marketing, and we do not sell or share it.

The legal basis is our legitimate interest in providing support for software you use.

Under the GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or object to our use of it.

Support correspondence is the only personal data Eriksen Labs itself holds. Email [email protected] and we will respond within 30 days.

Data held by an app inside your Atlassian instance — such as the schedules and request details stored by Recurring Requests — is a different matter, because we have no access to it. A customer can delete their own schedules and templates from the portal, and a site admin can stop any schedule or uninstall the app, which removes all of it. If you need something erased and cannot reach it yourself, ask your site administrator; write to us as well and we will explain exactly what the app stores and where.

If you are unhappy with our response you can complain to the Norwegian Data Protection Authority (Datatilsynet).

Where one of our apps processes personal data on behalf of an Atlassian customer, that customer is the controller and we are the processor. The terms governing it, including sub-processors, breach notification and deletion, are in our Data Processing Addendum.

If this policy changes we will update the date at the top. Material changes affecting app behaviour will also be noted in the app's release notes on the Atlassian Marketplace.