Does Rocket.Chat's license allow copyright removal?

Hello!

I see that Rocket.Chat is distributed under the MIT license, but at the same time some features, such as removing “Powered By”, are only available in the premium plan. My copy of Rocket.Chat is located on my server and I am using the Community Edition version. Can I make changes that remove copyright? For example:

  1. “Powered by” in workspace
  2. “© Rocket.Chat Technologies Corp.” in email template

Thank you. And thanks to the Rocket.Chat team for their hard work :slight_smile:

You have answered your own question.

It’s not so much copyright but licencing.

So as you are on CE and pay zero for using it, why do you want to remove your only acknowledgement towards their hard work? Devs can’t eat for free any more than you can.

If you really want to remove it correctly you’d have to run the fossify script, tidy up, and build yourself.

Unfortunately, I still don’t see a clear answer. Does Rocket.Chat’s license allow me to remove these lines by changing the source code and rebuilding app for yourself?

Because I want to maintain a unified design for my project and there are things that don’t fit into it. I am also a developer and I also release products, both Open Source and paid. When I want the product to bring me money, I release it with the appropriate license. If I release a product under the MIT license and it contains copyright, I fully understand that any user has the right to remove it and I personally gave it to him, so i don’t think i should worry about the fact that I’m supposedly taking money from someone using the right that he gave me :slight_smile: That’s actually why in this case I want to know if I have such a right :slight_smile:

You didn’t read my response. I did say quite specifically the correct route.

Please spend some time understanding the difference between copyrght and licencing.

They really are not the same thing (my main job is in promotional merchandise and I can assure you they are different)

You also need to see what is EE code and what is not. Some is MIT and some is not.

Sorry if a Rocket logo doesn’t fit into your unified design. The easy route is to use a Pro license and use what you want.

But as is the nature of open source and previously explained, you can build your own fossified version, and the team will be looking forward to all your contributions in due course.

Let me clarify my meaning to avoid any confusion. When I refer to “copyright” in this context, I specifically mean the visual text that credits the product author – for example, phrases like “Powered by Rocket.Chat”

I have reviewed the license and examined the code, but I want to save time by not having to analyze large portions of code to determine which parts are EE and which are MIT. That’s why I asked the question here – I was hoping to receive a precise answer based on people’s experiences.

Instead, I’ve received responses that come across as condescending, sarcastic, and passive-aggressive. Such communication makes me uncomfortable. If you find it difficult to respond respectfully, perhaps it’s better to refrain from answering others’ questions, especially if you automatically assume they are less knowledgeable.

Please note. I don’t work here. I’m not here to do anything apart from try to give you some facts, in my spare time, unpaid.

It’s not personal.

Again, Copyright and Licence are two different things.

It’ll take you 5 seconds and is documented and answered multiple times if you try a search.

Eg

Anything in the EE folder is… EE (and I mistakenly said ‘some is MIT’ - EE isn’t)

The rest is MIT.

The Rocket logo and text is copyrighted. You can’t alter it in any way. That’s not the same as licenced usage.

Under the licence of use you cannot modify it or remove it (from their built binaries eg docker, snap etc) unless you either pay for a subscription, or under MIT take the code, remove the offending sections, and re-build Rocket yourself.

Again I suggest you look at the fossify script which allows you to strip any EE code.

I hope that clarifies it for you.