No. Fluxer doesn't ask contributors to sign a contributor licence agreement (CLA), and you keep the copyright in your work. Fluxer is licensed under the GNU AGPL, version 3.0 or later, and your contributions are licensed under that same licence.
Fluxer Platform AB can't relicense your work under any licence other than the AGPL without your permission. The only exception is work sent before 18 February 2026 by contributors who signed the CLA that Fluxer had from 5 January 2026 until that day.
Relicensing can't take the AGPL away from any version of Fluxer that has already been published, and anyone can keep running and forking that code.
What you agree to when you contribute
Each commit you send needs a Developer Certificate of Origin sign-off, which you add with git commit -s. The sign-off confirms that you have the right to submit your change under the AGPL. The contributing guidelines list what else a pull request needs, and the LLM usage policy says what you can and can't use an LLM for.
Why Fluxer had a CLA at first
When we opened fluxer.com to everyone on 2 January 2026, we didn't know yet whether Fluxer could fund itself. We wanted to keep the option of also offering Fluxer under a commercial licence to organisations that couldn't follow the AGPL. To do that, we needed the right to relicense every contribution, so we added a CLA on 5 January 2026.
On 9 February 2026, a product decision by another chat app changed Fluxer's scope overnight, and it became clear that Fluxer could fund itself without a second licence. People on Reddit also said that the CLA asked too much of contributors, and Hampus removed it on 18 February 2026, about six weeks after it had been added.