Privacy

Privacy notice

How Ensline handles personal data on ensline.com and in our online tools, such as the “Know what you ship” assessment and the “Know who builds it” repository scorecards: what we collect, why, how long we keep it, and what you can ask of us.

Last updated 19 November 2026

Who is responsible

Ensline AB, Vallgatan 3, 411 16 Göteborg, Sweden, is the controller of the personal data described here.

Questions about privacy, or requests about your data: privacy@ensline.com.

What we collect and why

When you take an assessment

While you answer, your answers stay in your own browser. When you submit the assessment, we store your answers, your results, the role you picked (if any), your browser type and the page you came from. This is not linked to your name, email or organisation unless you ask us for a review.

We use it to show you your results, and to build statistics and improve the assessment. The legal basis is our legitimate interest in developing and improving our tools (Article 6(1)(f)).

When you ask for a review

If you ask us to review your results, we store your work email address, your organisation and its size, and that you agreed to be contacted, linked to your assessment. A notification with these details and your scores goes to our team by email.

We use this to prepare your review, contact you about it, and keep track of our follow-up. We may also note that the same email address or the same organisation’s domain has used the tool before. The legal basis is your consent (Article 6(1)(a)), which you can withdraw at any time.

If you subscribe to news

If you tick the option to receive news and offers, we keep your email address on our news list, with when and where you signed up. The legal basis is your consent. Every news email contains a personal unsubscribe link, and you can also unsubscribe here at any time. After you unsubscribe we keep your address marked as unsubscribed, so that we do not mail you again by mistake.

Your shareable scorecard

When you ask for a review, you get a link to your scorecard: the overall rating, the chart and the maturity levels. Anyone you give the link to can see it. It does not show your answers, your name, your email or your organisation. The link is random and cannot be guessed, and search engines are asked not to index it.

When you ask for a repository scorecard

About you, the person asking. We store your email address, the repository you asked about, when you asked, and a keyed hash of your network address (used only to limit how many scorecards one network can request). If you choose “tell me more about the Ensline approach”, we also store your organisation and its size if you give them, and our team is notified so that we can contact you. We email you the link to your scorecard. The legal basis for emailing the scorecard is your request (Article 6(1)(b)); contacting you about Ensline and sending news is based on your consent (Article 6(1)(a)), which you can withdraw at any time.

About the people who contribute to the repository. To build the scorecard we read the repository’s public commit history: author email addresses, names, dates and time zones, and commit message trailers such as Signed-off-by. On GitHub, GitLab and Forgejo hosts (such as Codeberg) we also read public issue, pull request and release information: when items were opened, answered, merged and closed, by which account, with which labels, and whether the forge lists that account as a maintainer. Email addresses, names and account names are used only while the analysis runs and are not stored. What we keep are aggregates: per email domain (for example example.com), the number of commits and of distinct people in the last year, and per month or quarter, counts and medians such as response times.

An email domain used by only one person (a personal domain) can identify that person. We never show such a domain on a scorecard, where it counts as “Independent”, and we delete it 24 months after we last saw it, unless it belongs to a company or other organisation.

What we use it for. To build the scorecard that was asked for; to improve the tool, for example by mapping more email domains to the companies they belong to and by better recognising bots and bug reports; and to build reports with insights, such as blog posts, articles and presentations by Ensline. Those reports are about open source projects and the companies that contribute to them; they may name public projects and companies, never individual contributors. The legal basis is our legitimate interest (Article 6(1)(f)): the data is already public, we keep only aggregates, and the purposes are limited to these. If you contribute to a repository and object, email us: we can exclude your email domain from our data.

Scorecard links and badges. A scorecard link shows the cards for the repository and when it was analysed, never who asked for it. Anyone with the link can see it and embed its images, and search engines are asked not to index it. Scorecards are built only from public repositories, so we may also show the scorecard for a repository you asked about to other visitors, for example as an example in the tool or on our website. We show the cards and when the repository was analysed, never who asked for it.

Preventing abuse. To stop the tool from being misused, we may keep a block-list entry for an email address, email domain or network that misused it, for as long as the block applies. Email addresses and networks are stored on the block list only as a keyed hash, not in readable form. The legal basis is our legitimate interest in keeping the service available and secure.

When you visit the website

We record technical information about each request, such as the IP address, time, requested page and browser type, to keep the site running and secure. The legal basis is our legitimate interest in operating a secure website.

Cookies and local storage

We use only what the website and tools need to work. There is no analytics, advertising or tracking, and no third-party scripts, fonts or embeds, so we do not ask for cookie consent.

NameTypePurposeKept for
sessionidCookieLets you see your own results and connects your answers to your assessment.Two weeks
csrftokenCookieProtects the forms against forged submissions from other sites.One year
kwys-v1Local storageRemembers your answers in your own browser, so you can continue an assessment later. Cleared when you submit.Until you submit or clear your browser data

If we ever add anything that is not strictly necessary, we will ask for your consent first.

Who can see your data

Your data is available to the Ensline staff who handle reviews and follow-ups. We also build statistics from it used to produce reports with insights, such as blog posts and presentations; these never identify you. We do not sell your data or share it with others for their own marketing.

We use service providers who process data only on our behalf and under data processing agreements:

For repository scorecards we also read public data from the hosts where repositories live, such as GitHub, GitLab and Codeberg. They are sources of public information, not processors of your data: we send them only the repository’s address.

Our data is stored within the EU/EEA. Microsoft keeps our Microsoft 365 data in the EU, but as a US-based company it may in limited cases access data from outside the EU/EEA, for example for support or security. Such transfers are covered by the EU–US Data Privacy Framework and the EU standard contractual clauses in Microsoft’s data protection terms.

How long we keep it

Your rights

Under the GDPR you can ask us to:

Email privacy@ensline.com from the address concerned, so that we can confirm it is you. We reply within one month.

Changes

We update this notice when our tools or practices change. The date at the top shows the latest version.

People. Open source. Security.