PROJET AUTOBLOG


Free Software Foundation Europe

source: Free Software Foundation Europe

⇐ retour index

Mise à jour

Mise à jour de la base de données, veuillez patienter...

Legal Corner: The War on Ad Blockers – Axel Springer’s Assault on User Freedom

mardi 16 septembre 2025 à 01:00

Legal Corner: The War on Ad Blockers – Axel Springer’s Assault on User Freedom

For many internet users, an adblocker is an important piece of software that allows them to control the digital information they receive from their browsers, providing the option of an ad-free browsing experience. Despite this, a recent decision by the German Federal Court of Justice is giving Axel Springer a second chance to erode user freedom.

CC-BY-NC-SA by Rahak

The original lawsuits brought by Axel Springer

We wrote in 2023 about the outcome of a series of suits filed by Axel Springer SE (Axel Springer), one of Germany’s largest media and publishing companies, against Eyeo GmbH (Eyeo), the creator of Adblock Plus. Eyeo and Adblock Plus prevailed in the courts back then, allowing for the continued use of adblockers such as Adblock Plus by internet users in Germany. A new recent decision by the German Federal Court of Justice has unfortunately given Axel Springer a second chance to make its arguments against adblockers.

Adblock Plus is a Free Software browser extension licensed under the GPLv3 that allows its users to bypass ads and pop-ups when accessing websites, for an ad-free internet browsing experience. This was done according to filter rules maintained in a so-called “black list”, which users use as a default setting. The extension offers ad providers the possibility of having their ads excluded from this black list (and included in a “white list”) by complying with “acceptable advertising standards”, disclosing their annual turnover, and paying a fee to Eyeo. Users will then only see ads that have been included in the white list, although they also have the option of blocking ads from both white and black lists altogether if they so choose.

Axel Springer’s legal complaints in their suits against Eyeo were on the grounds that how the Adblock Plus extension functioned constituted:

  1. targeted obstruction and aggressive business practice; and
  2. a violation of freedom of the press.

Back then, the Hanseatic Higher Regional Court (the HansOLG) in Hamburg ruled in favour of Eyeo. In doing so, they stated that using adblockers such as the Adblock Plus extension is a decision that users are entitled to freely make, as user rights not only include the freedom to express an opinion and to receive information, but also the rights to refrain from expressing an opinion, and to refuse receiving imposed information. This meant that Adblock Plus’s business model was a marketable service offer not primarily aimed at impairing the competitive development of Axel Springer. Adblock Plus therefore constituted a product whose use is decided solely by the internet user, and does not directly interfere with Axel Springer’s business.

Axel Springer’s current re-litigation of user freedom

This brings us to the unfortunate current situation. After the HansOLG ruling in 2023, Axel Springer appealed this ruling to the German Federal Court of Justice (the BGH), which led to the BGH issuing a judgment on 31 July 2025 allowing the case to be remanded back to the HansOLG.

Specifically, the BGH held that Axel Springer’s exclusive rights to reproduce and modify their computer programs, granted to them under Section 69c of the German Copyright Act (the UrhG), can possibly be infringed by an ad-blocker. In a situation where a browser and its engines are not controlled via object code, but by bytecode from which the browser’s virtual machines generate object code, the BGH stated that such bytecode (or the code generated from it) may be protected as a computer program. The BGH was of the opinion that if a third party computer program, such as adblockers like Adblock Plus, alters this code in the course of reproduction, this may possibly infringe upon the exclusive rights provided for by the UrhG.

It is important to note that the BGH’s statements here about bytecode and object code are merely speculative, and what the BGH thinks to be a possible interpretation of German copyright law. The actual substance of the BGH’s ruling is to compel the lower court of the HansOLG to re-consider the case for further fact finding. In other words, it is the responsibility of the HansOLG to definitively state what the actual interpretation of German copyright law is.

What this also amounts to is that Axel Springer has essentially been given a second opportunity in the court system to question the legality of adblockers. In this second opportunity, the actual interpretation of the law that the HansOLG now has to produce will be influenced by the direction given by the BGH to focus on Axel Springer’s arguments about whether the DOM, CSS, and bytecode are to be considered as protected computer programmes under the UrhG, and whether an adblocker’s modifications of these elements amount to a violation.

The implied conflict of corporate vs user freedoms: a balancing of rights

Back in the original suit before the HansOLG, Axel Springer’s arguments were that their websites could be protected under German copyright law as a copyrighted computer program, and that their HTML code would come under this same protection because of the control components it included. Because of how Adblock Plus interacts with their websites, Axel Springer therefore claimed that copies and adaptations of the code amounted to violations of the copyright protections preventing modification and reproduction.

Axel Springer’s line of argumentation was rejected in the HansOLG’s ruling in 2023. The court ruled that the use of Adblock Plus solely affects the program flow through external commands, without altering the program’s essence or generating a changed version. The use of the Adblock Plus extension therefore results in what was deemed at the time to be a mere browser configuration carried out by users according to their preferences.

It is therefore interesting to compare and see the different perspectives taken in the judgement issued by the HansOLG in 2023, and the appeal judgement by the BGH this past July. The HansOLG’s judgement seems to take a firm view of user freedoms, particularly placing greater weight on an individual internet user’s freedom to configure their browsing experience, and their rights to third party software to do so. Conversely, the ruling of the BGH seems to be hyperfocused on questions of ownership of copyrights, and the technicalities of how adblocker code can interfere with such copyrights.

Legal disputes often arise because two parties are trying to exercise rights that come into conflict with each other, and the resolution of such disputes come about when the courts find what they deem to be a satisfactory balancing of rights within the context of the law. Finding a satisfactory balance will depend on how much weight or importance the court gives to each right argued by the parties. In this situation, in our opinion it seems that the BGH is remanding the case back to the lower courts as it is uncertain about the question of which is more important:

  1. The rights of internet users to control, configure, and filter the type of information that they receive when using the internet; or
  2. The rights of Axel Springer as a website creator to have the exact configuration of content on their website to be delivered unchanged to an internet user, in the extent to which it is protected by copyright.
Will the court prioritize our individual user freedoms to control how the average internet user is able to use digital technology, or will it prioritize copyrights that prevent the alteration by adblockers of the website code of Axel Springer? In our opinion, this question is an easy one to answer. The freedoms of tens of millions of internet users in Germany to be able to self-regulate the information that they wish to receive through their own web browsers far outweigh the interest of a multinational enterprise that reported an estimated €3.9 billion in revenue in 2023 to be able to capitalize more effectively on ad revenue.

For this reason, we are of the opinion that the HansOLG made the correct call in prioritizing user freedoms in their 2023 ruling, and hope that the court will find the same outcome in this second round of trial.

Consequences of a possible pro-Axel Springer verdict

The immediate goals of Axel Springer in this court battle can be said to be the effective disabling of the use of Adblock Plus when viewing Axel Springer produced websites. Nevertheless, it is important to keep in mind that the effects of legal verdicts are often not limited to just the immediate parties. In many cases, the court’s reasoning and interpretation of the law can have larger societal effects than just on the immediate subjects of each case. A court ruling rarely affects just the specific topic of the verdict; more often than not the philosophical underpinnings in a judicial reasoning is its legacy and lasting impact.

A pro-Axel Springer verdict therefore could have disastrous consequences on user freedom for German internet users. While the immediate effect of the case may be that internet users will no longer be able to use Adblock Plus to block ads on Axel Springer websites, the broader reasoning behind such a decision could open the doors for any website with ads to benefit from such a ruling as well. This could effectively spell the end for internet users in Germany to effectively block unwanted ads on all websites beyond just Axel Springer’s, by rendering adblockers illegal in Germany.

Additionally, the BGH’s insistence on focusing on examining whether copyrights are preserved through the alteration of bytecode (or the code generated from it) by third party computer programmes can possibly be applied in the future for other web apps or extensions beyond just adblockers. There are many such apps and extensions in existence today that allow users to customize their internet browsing experience, including some that allow users to preserve their freedoms and rights in other areas.

For example, the Free Software extension Privacy Badger (licensed under the GPL3-or-later), maintained by the Electronic Frontier Foundation, blocks hidden trackers to help users stop companies from harvesting personal data. If apps such as Privacy Badger are deemed by the courts to alter copyrighted code in the same way as Ad Blocker Plus, a pro-Axel Springer verdict could therefore work to prevent the use of programmes that internet users use to protect their privacy, security, and autonomy.

Existing problems in the 2023 verdict

It is nevertheless also important to note that, while the support for user freedom by the HansOLG judgement in 2023 was certainly welcome, this verdict is not without its faults. Although it supported user freedom to configure browsing activity, the HansOLG nevertheless preserved Axel Springer’s right at the time to exclude users with an activated adblocker from accessing its content. This can be understood to be an approval of the use of adblock detection tools by companies like Axel Springer to exclude user access to information. Indeed, Axel Springer has deployed such tools on a number of its websites, which significantly hinder a user from accessing its content if an adblocker is used.

This is a particularly unfortunate aspect of the 2023 verdict, as tools to detect the use of adblockers are in violation of Art. 5(3) of the ePrivacy Directive, which mandates that websites must seek consent before accessing or storing information about the user’s device. Such information includes scripts in the terminal equipment of users to detect if they have installed, or are using adblockers.

Open possibilities in case of a ruling

This ongoing saga is yet another example of how our rights and freedoms are not immutable. Rather, they require effort to be maintained, and constant vigilance to ensure their preservation, especially against entities that are incentivized to erode them for profit.

That being said, court cases are very much insulated in nature; apart from those immediately involved in the litigation, there tends to be little that the average member of the public can do to directly affect the outcome of a specific case, regardless of how much the verdict of such case may affect third parties. Nevertheless, if a pro-Axel Springer verdict is reached, action can still be taken afterwards.

One option available would be an appeal to the European Court of Justice (the ECJ) on the grounds of a violation of the aforementioned ePrivacy Directive. While this does not necessarily reverse any adverse ruling on adblockers that the current case before the HansOLG may bring, an ECJ ruling that explicitly declares tools detecting the use of adblockers to be a violation of the ePrivacy Directive would be useful to make enforcement of an adblocker prohibition much more difficult, and would be a useful legal tool in the fight to support user freedoms.

Additionally, such a verdict can be countered by working towards policy goals that enact legislation (whether in Germany, or EU wide), that prioritize the protection of user freedom, security, and independence when using the internet, and other digital services and technology.

If you have a legal or licensing question related to Free Software that is not covered here or in any of our other resources, you can consider asking our License Questions team by sending them an email at licence-questions@fsfe.org.

Support FSFE

SFP#38: Policy and EU: Free Software Software Stack(s)

vendredi 12 septembre 2025 à 01:00

SFP#38: Policy and EU: Free Software Software Stack(s)

During the debate on digital sovereignty, the term “software stack” started to float around. This term quickly started to fill up with different ideas, and a discussion about it took root. Follow Alex and Bonnie in this episode to learn more about Free Software Software stacks and their connection with public administration.

Software stacks do not advance digital sovereignty merely by avoiding US components, but they must be 100 % Free Software. Find out, together with Alexander Sander and Bonnie Mehring, why it is so important that these stacks must be completely Free Software and discover the current debates on this topic in the EU.

Listen to our Software Freedom Podcast and stay up to date with the discussions about technological topics in Europe and the European Union.

In our 38th episode you can learn more about the FSFE's policy work and how we as a charity advocate for software freedom. You can support our work by donating.

Show notes

We are happy to receive your feedback on the Software Freedom Podcast and especially on the transcript of the episode. Please, send us an email to: podcast@fsfe.org. If you liked this episode and want to support our continuous work for software freedom, please help us with a donation.

Support FSFE

Legal Corner +++ CRA +++ Public Awareness

mercredi 3 septembre 2025 à 01:00

Legal Corner +++ CRA +++ Public Awareness

Last month we published a new article in our Legal Corner, we checked how the German government is doing after 100 days, and we provided a deeper look at the CRA on our podcast. We also attended several conferences and continue working on making gatekeepers accountable under the DMA.

Table of contents

Quote of the Month

"Free Software should be celebrated and appreciated just as much as the concepts of democracy, the rule of law, equal opportunities, and the free exchange of other information than just Software! [I Love Free Software Day] is a great way to remind people that lots of community spirit has gone into creating the tools we use every, which is often more and more powered by software".

Steven Maddox from FSFE Potteries group-

Legal Corner: Bringing SumUp to compliance: a case study of license enforcement

What happens when those who benefit from the four freedoms fail to comply with the terms of a Free Software license? We take a look at the experience of license enforcement by one of our FSFE volunteers against the fintech company SumUp, and examine the lessons that supporters of Free Software can take away from it. Read it now!

SFP#37: Policy and EU: The most famous of them all – we are talking about the CRA

Most of you have heard of the famous Cyber Resilience Act (CRA), legislation introducing CE labels for digital products. In our latest episode of the Software Freedom Podcast, Bonnie and Alex have an easy to follow conversation about the CRA and what will be happening next.

After 100 days: Germany’s government still lacks a Free Software push

On 14 August 2025, Germany’s government marked 100 days in office. CDU, CSU, and SPD had pledged ambitious Free Software goals. Yet it remains unclear what these goals actually are, how they will be achieved, and what role Free Software will play in securing Germany’s technological sovereignty.

ilovefs: How "I Love Free Software Day" is celebrated in Potteries, UK

Every year on 14 February we celebrate our "I Love Free Software Day". On this day we thank all Free Software contributors for their commitment to use, study, share, and improve Free Software. We have talked with our local group in Potteries (UK) to learn a bit more about them and how they celebrate this day.

At the stages: FrOSCon, Scambi Festival, COSCUP...

In August we travelled to Sankt Augustin to attend FrOSCon once again. The day before, our local group there held a community meetup in Bonn, attended by around 30 people. And during the two day conference, we had a booth (thanks to our volunteers for giving a hand there!) and two talks: one analysing the first 100 days of the current German government and another one discussing the current state of the CRA implementation.

The city of Sanremo also welcomed us for the Scambi Festival in which we had an “Ada & Zangemann” reading and a workshop about Free Software basics. We also had the chance to gift a 'Ada & Zangemann' book to the town public library, which was accepted by the Deputy Mayor of Culture of Sanremo.

And we also travelled to Taiwan! At this year's 20th anniversary of COSCUP, the FSFE was present with a booth and several talks!

In September we hope to see you at InselChaos and at Vegamania in Vienna!

Big Tech greed is here. Software freedom needs you!

A few weeks ago we sent you an email about how software freedom needs your support as currently owning a mobile device is not the same as controlling it. Apple and Google, which the EU considers gatekeepers under the Digital Markets Act, have created tightly controlled ecosystems that limit software freedom and shut out competition. We want them to change this kind of behaviour!

Join us today as an FSFE supporter and be part of the movement fighting for your right to control your own device.

Besides, we are still gathering feedback from Free Software developers with our Digital Markets Act Interoperability Survey. We need your feedback about requesting software interoperability.

Contribute to our Newsletter

We would love to hear from you. If you have any thoughts, pictures, or news to share, please send them to us at newsletter@fsfe.org. You can also support us, contribute to our work, and join our community. We would like to thank our community and all the volunteers, supporters, and donors who make our work possible, with a special mention to our translators who make it possible for you to read this newsletter in your mother tongue.

Your editor, Ana

Support FSFE

How we celebrate "I Love Free Software Day" in Potteries, UK

mercredi 27 août 2025 à 01:00

How we celebrate "I Love Free Software Day" in Potteries, UK

Every year on 14 February we celebrate our "I Love Free Software Day". On this day we thank all Free Software contributors for their commitment to use, study, share and improve Free Software. Without them there is no software freedom. We want to thank the all for contributing to Free Software <3

To mark this special occasion the FSFE's local groups organise local events and celebrations. Each celebration is unique and show-casts the commitment of our community. From local gatherings with pizza and fun Free Software games from our toolkit to larger events addressing new people with talks and networking.

One local group has been celebrating the “I Love Free Software Day” for the past 3 years – our group in Potteries, UK. But to take you back to the beginning of the FSFE local group meetings in the UK we have to go back to 1999. In 1999 a local Linux user group started and organised meetings, talks and many other activities. In 2019 the local group met a long-term volunteer from the FSFE at a conference. They hit it of and started talking about Free Software and this was the beginning of a new era for the local FSFE group in Potteries. For now six years the local group has stayed active and participated in various FSFE activities. Read more about the only FSFE local group on British soil and their celebration of the “I Love Free Software Day”.

FSFE: How many people are active in the group ? Can you also give us an overview of what Potteries is?

Steven, FSFE local group Potteries coordinator: It is tough to put a number on it as we communicate through lots of different channels, but it is not uncommon to see more than a dozen regulars at meetings, plus new faces that then often become new regulars!

We are situated right in the middle of England between Manchester and Birmingham. Most of the urban area of North Staffordshire is known as ‘The Potteries’ due to the city of Stoke-on-Trent and the surrounding towns being historically instrumental in the ceramic industry. It is a name that everyone local knows and understands, which is why we chose it. It is not uncommon to see many local groups using the Potteries in its name, and the FSFE President signed off on the name!

FSFE: What are the usual activities the Potteries local group does?

Steven: Online the activities are mostly just organising meetings, people sharing their experiences, and offering help and recommendations where they can. Workshop meetings involve using Free Software itself and attending talks given by anyone that fancies sharing their knowledge. We also have socials particularly in the summer, as well as trips to unconferences such as Oggcamp. At the moment we have two annual larger events which are ILoveFS and our end of year Flörgåsbord! event which we co-run with other groups too.

FSFE: When was the first time you celebrated the “I Love Free Software Day” and how did it work out?

Steven: The first time was Tuesday 14 February 2023 which initially we thought the date worked really well. This is because we cooperatively take turns to run meetings on Tuesday evenings with other similar local groups, increasing turn out as attendees always know to keep that evening free. We also used the same location that we used for formal scheduled talks, which was not really a particularly social venue, more like a computer lab.

Unfortunately that is also Valentines Day and people in the UK take it quite seriously and so the turn out was not great! We often got told their significant other would lynch them if they did not spend the evening with them!

First "I Love Free Software Day" celebrations in Potteries.

FSFE: How did the celebration of the “I Love Free Software Day” evolve over the next years and what was you personal highlight while celebrating this special day?

Steven: Well in subsequent years we were told we could use a date near to the 14 instead! So doing that, together with using a great new sociable space, has meant things have worked perfectly ever since! I would have to say my personal highlight was playing the games at ILoveFS 2025 event, that really helped to bring people together competing as teams, rather than lots of little groups talking amongst themselves.

"I Love Free Software Day" celebrations in Potteries.

FSFE: What did you do for the I Love Free software Day 2025?

Steven: Well we had the upstairs room of the KPA Clubhouse (on the Keele University campus) which is a great free venue with plenty of character and comfortable seating. The room was decorated with plenty of balloons and promotional material, as well as laptops loaded with Free Software that people could just pick up and try. Add to that some great company, as well as free food and drinks and it was a brilliant atmosphere for playing the Free Software quiz game, a quick presentation, and socialising about our love of Free Software, particularly those often forgotten smaller and hidden projects we take for granted.

FSFE: What would you recommend to others when they want to organise an “I Love Free Software Day” celebrations and what are pitfalls you would say should be avoided?

Steven: The first thing I would say is that if your event is not set up to easily explain what Free Software is and why it is important, to literally anyone walking in off the street, then you’re not doing it right! Accessibility of the topic is key, so if you have got a few spare laptops to run software that people will find familiar, but perhaps did not associate with Free Software, that’s a great start! Add to that some welcoming regulars who have the patience and skill to explain things without confusion (or fighting about which distro is better!) and you’re already off to a winning start. Try to steer conversations away from being too heavy, keep things social and lighthearted, and offer people comfortable seating, drinks, and food to get them willing to open up about their experiences.

FSFE: Why do you think I Love Free Software Day is important and why should everybody be celebrating this day?

Steven: Free Software should be celebrated and appreciated just as much as the concepts of democracy, the rule of law, equal opportunities, and the free exchange of other information than just Software! Things that people take for granted but took years of work to establish and constantly need defending. It is a great way to remind people that lots of community spirit has gone into creating the tools we use every, which is often more and more powered by software.

FSFE: Do you already have plans for celebrating “I Love Free Software Day 2026”?

Steven: We plan to have a plan! The venue we used for the least two years has been a great success, so we’ll be looking to mostly replicate that again in 2026 but this time with the focus on thanking maintainers.

FSFE: Steven, Thank you very much for your time!

Support FSFE

Legal Corner: Bringing SumUp to compliance: a case study of license enforcement

mercredi 20 août 2025 à 01:00

Legal Corner: Bringing SumUp to compliance: a case study of license enforcement

What happens when those who benefit from the four freedoms fail to comply with the terms of a Free Software license? Today we take a look at the experience of license enforcement by one of our FSFE volunteers against the fintech company SumUp, and examine the lessons that supporters of Free Software can take away from it.

Photo by SumUp on Unsplash

Enforcing your rights under a Free Software license

The four freedoms of Free Software are important foundations on which user freedom in a digital society is built upon. In practice, the four freedoms in a particular piece of software are recognized, legitimized, and supported by the legal system through the application of a Free Software license. However, like many other rights, the four freedoms will merely be pipe dreams if they are not enforced and complied with.

Because of the construction of Free Software licenses as permissions granted by the copyright holder of the software, the use of Free Software creates a kind of legal relationship between the copyright holder and the user. Violating the terms of a Free Software license therefore results in legal consequences, including revocation of the license to the specific violating user or demands for corrective actions, the specific performance of the software license, and lawsuits.

“Specific performance” is a legal term referring to the act of fulfilling a requirement in a legal agreement in exactly the way that it is specified in that agreement.

It is important not to conceptualize software license violations simply as individual users not complying with the license of a single software project. The widespread use of Free Software licensed components in many significant commercial software products means that violators can often be large companies and organizations. Because of this, enforcement of Free Software rights against larger violating entities in practice can feel daunting and intimidating for many individual users.

Nevertheless, ensuring that Free Software license terms are complied with is ultimately a crucial factor contributing to the adherence of the four freedoms. Enforcement is therefore an important stepping stone to achieving the transparency, autonomy, and liberty that we value so much in software freedom.

Bringing SumUp to compliance: how it started

SumUp is a financial tech company that produces payment terminals and other point-of-sale systems used primarily by business entities for financial transactions, as well as the corresponding software that is loaded into them. One of SumUp’s products is the SumUp Solo (the Solo), a contactless payment terminal with many digital and software components that facilitate its operation.

In July of 2024, German FSFE team member Nicole Faerber’s place of work acquired a Solo payment card terminal. Nicole noticed that neither the documentation for the Solo, nor the software provided, nor the SumUp website provided any Free Software disclosures. In other words, Nicole noticed that users of the Solo:

  1. did not have access to any identification of Free Software components present in the retail version of the Solo device;
  2. did not have access to the corresponding licensing information related to these Free Software components;
  3. did not have access to any copyright notices conveying information about copyright ownership of these Free Software components;
  4. were not provided any offers for the source code.

This lack of disclosure was curious, especially as Nicole was aware of the work of Aaron Christophel, a German engineer who showcases how he disassembles and tinkers with his various devices. In 2023, Christophel took apart a Solo device and demonstrated how he was able to find several security issues with the device. Of interest as well was that Christophel’s disassemble showed that the Solo was working off of an Open Root Shell and a Linux system, which would imply a certain level of necessary Free Software disclosure, as well as corresponding source code, to its users.

With this in mind, Nicole privately obtained her own Solo, and conducted her own investigation into the device. In addition to the Linux kernel, she found that the device also functioned with a lot of Free Software, including:

Correspondence with SumUp

With the knowledge that the Solo was loaded with numerous Free Software components, and that the lack of any FOSS disclosures meant that the Solo device was not in compliance with its license obligations, Nicole contacted SumUp support. She requested their compliance through disclosure and provision of the “complete corresponding source code” (CCS). The initial response was that such information was protected by copyright and constituted trade secrets, and accordingly her request would not be fulfilled.

Nevertheless, Nicole persisted with following up emails explaining the principles of Free Software and its licensing, and the general obligations that SumUp is obliged to comply with by including Free Software components in their devices. Without divulging too much information about the internal state of their licensing affairs, SumUp eventually responded that they were working on licensing compliance and would get back to Nicole as soon as they could.

Despite this, almost half a year after her initial contact and request, Nicole still had not received any disclosures by December 2024, nor the CCS from SumUp. In a follow-up response to indicate that she had not forgotten their obligations and her request, Nicole specified to SumUp that if their inability to provide the CCS as well as proper FOSS disclosure persisted, this could void their rights to continue properly and legally retailing their Solo devices. In response, SumUp asked Nicole to provide the legal basis for her statements, despite such information being readily available online.

Shortly thereafter, SumUp finally provided some initial disclosure documentation to Nicole as well as what they claimed to be the CCS for the Solo device. Such disclosures were insufficient, as the disclosure document was provided directly and only to Nicole, and not on a public forum, and the source code provided appeared to be incomplete. Nicole therefore requested that SumUp do the disclosures locally on the Solo devices themselves, by adding something in the Solo user interface that displays a list of software components, as well as all required licensing and copyright information.

In June 2025, after almost a year since the initial contact made with SumUp, Nicole finally received a USB stick containing the required disclosures and the CCS. Additionally, SumUp also updated their Solo device software to now show the relevant FOSS disclosures, and also to indicate where users will be able to access the CCS.

While some additional work is required to ensure if this provided information is fully accurate and fully compliant, this is nevertheless a positive outcome that contributes to SumUp’s users being able to enjoy software freedom.

Summing Up the SumUp experience

Enforcement requests can in egregious situations take time to yield results: In general, Nicole’s experience tells us that, unfortunately, enforcement against a violator can often take a fair amount of time before there can be any substantial change from a violator that yields concrete compliance results. This is particularly because if the violator had not paid attention to licensing requirements before, it will take a lot of work for a large project to come into compliance. Additionally, internal administrative procedures can also play a part in slowing down the overall compliance process.

Expect to be told that default copyright protections apply: Another factor that contributes to these delays is the defensiveness that many violators are prone to display when confronted with their non-compliance. Copyright protections are generally more well-known to the general public, relative to Free Software licensing. Because of this, a typical knee-jerk reaction experienced when requesting disclosure or CCS would be to invoke copyrights and trade secrets as a tactic, as was the case here with SumUp.

Bear in mind which department you are speaking with: Defaulting to the argument that the CCS cannot be shared because it is “copyrighted”, “trade secrets”, or other legal jargon, happens also because, especially when dealing with larger organizations, it is quite likely that the first contact you will have is usually with a customer service representative operating from a generic contact email address. The first response to a license compliance request will therefore not usually be entirely productive, unless you have a direct contact to those who have the requisite expertise in licensing to fully understand the context of a license compliance request.

Indeed, if you would like to expedite your own enforcement process of a particular company violator, it is generally a good idea to look for the contacts of people working either in a software development or legal capacity within that company. You can try to find this information from various sources, including the “About” pages of the company website, publicly available employee personal pages, or from public repositories such as GitHub where the company in question may have contributed to.

Non-compliance is not necessarily a malicious act: It is important to keep in mind that violations are not necessarily malicious; often times, non-compliance with Free Software license terms are based in ignorance of best practices. Additionally, even if you get through to those specifically dealing with legal issues in a non-compliant organization, there is unfortunately also a fair amount of misunderstanding or ignorance of Free Software legal and licensing issues within the legal profession. As Hanlon’s Razor states: “Never attribute to malice that which can adequately be explained by incompetence”.

“Accidental/unintentional non-compliance” is nevertheless losing credibility: That being said, Hanlon’s Razor is merely a general observation, not an immutable natural law. Conversations and information around Free Software licensing have grown significantly in the past few decades, and many professional software developers and IT lawyers should have a passing understanding of Free Software licensing and the obligations that come with it. Ignorance as a defence can therefore only go so far, and especially with large entities handling large projects, can often cease to be credible.

In certain cases, it is also possible that companies have strategically neglected their licensing obligations for a number of reasons. One possibility is that putting in the work to ensure full disclosure and compliance might take up too much time, effort, and/or cost, and a particular company may choose to ignore the problem in favour of utilizing their workforce in other priorities.

We should always keep in mind that the reasons given by a violator may explain past non-compliance, but it should never be used to justify and/or excuse continued and ongoing non-compliance. For individuals seeking compliance, it may nonetheless ultimately be more productive and worthwhile to focus on practical strategies that ensure that the end result is compliance, rather than to assign blame.

Some tips for when you are enforcing your rights

Bearing all the observations above in mind, if you suspect that an organization is violating the obligations of a Free Software license, by withholding disclosure or the CCS, and you’d like to enforce these license obligations by requesting Free Software disclosure, here are some things to keep in mind.

Be aware of the kinds of Free Software components present in the systems that you are seeking the source code for. This allows you to also understand which Free Software licenses apply for the device or software in question, and therefore the precise license obligations that the potential violator is under. Awareness of your legal rights, and their legal obligations to provide disclosure, will allow you to be more assertive in pushing for compliance.

You should also be prepared for efforts by violators to resist making substantive changes to their practices that would result in compliance, and sometimes can resort to defensive measures in an attempt to stop your enforcement efforts. Persistence is unfortunately necessary in order to see the process through to your end goal of proper disclosure.

Additionally, the FSF and the SFC have also developed the Principles of Community-Oriented GPL-Enforcement (the Principles), which lays out their recommendations on how community users can go about enforcing licensing obligations in a manner that enables users to understand the violator’s situation without excusing the violation, but rather to allow for collaboration to bring the violator into compliance.

An important takeaway as well from the FSF and SFC’s perspective in creating these Principles is that the focus of enforcement processes should always be on bringing about compliance with licensing obligations. Indeed, they stress that:

“[c]opyleft licenses do not state specific enforcement methodologies (other than license termination itself) in part because the real world situation of GPL violations varies; rigidity impedes success.

In particular, this list of principles purposely does not seek to create strict criteria and/or “escalation and mediation rules” for enforcement action. Efforts to do that limit the ability of copyright holders to use copyleft licenses for their intended effect: to stand up for the rights of users to copy, modify, and redistribute free software.”

Concluding remarks

Free Software licensing formalizes our ability as users to enjoy the four freedoms of Free Software. Without proper adherence to these licensing obligations, and without the ability to enforce these rights, the proper and guaranteed enjoyment of our user freedoms will be at risk.

Unfortunately, the history of Free Software license enforcement has shown that often, large amounts of effort has to be expended in order to for users to be able to properly enjoy these freedoms. Nicole’s experience in this example is indicative of how much time and effort currently needs to be spent in order to effectively enjoy what is actually a legal right for users, especially from larger companies that work with digital technology.

Nevertheless, this example does indicate that some positive changes have taken hold in the past decades since the early days of GPL enforcement, where compliance had to be litigated in, and enforced by, the courts. In this example case, despite being initially defensive and protective over their CCS and Free Software disclosures, SumUp has since been relatively proactive in taking steps to ensure Free Software license compliance with their devices, which is always good to see. This can be indicative that companies are progressively becoming more aware of Free Software legal requirements, and growing awareness of their obligations to comply.

We therefore encourage all our readers to start asking questions about your devices and the software that they contain. When more users hold vendors of digital technologies accountable, even if it is just through a simple request for the CCS and Free Software disclosures, this can be a way to force companies to have to substantively conceptualize and understand their obligations in a digital society where openness and collaboration has been baked into many of the software components that enable their products to function.

Nicole’s efforts show that individuals can have outsized positive impacts on software freedom, and many little steps like Nicole’s, when taken together, can amount to a large enough movement to further develop the Free Software ecosystem in a positive direction.

If you have a legal or licensing question related to Free Software that is not covered here or in any of our other resources, you can consider asking our License Questions team by sending them an email at licence-questions@fsfe.org.

Support FSFE

I'm richer than you! infinity loop