Quote from: seoincorporation on Today at 01:44:47 AM

There is a risk when we install extensions in our web browsers... i know it was made to collect the bets information, but we are not sure if it collects other kind of data, or if it can do some other stuff like make withdrawals or tip users on the casino. Even it could change the deposit address in the casino.

Is there a chance that you make from your extension an opensource project? That way we could take a look at the code and verify if it doesn't have any kind of malware on it.

You are absolutely right—extensions with access to all sites can indeed pose a potential threat, and such concerns are completely justified.
Our extension also requests access to all sites. This is necessary to automatically maintain mirrors of betting sites—the user doesn’t need to reinstall the extension every time the bookmaker’s site URL changes.
We plan to open-source the code, but we cannot provide exact timing yet. At the same time, it’s important to understand that even with open source, the extension itself will not be completely autonomous—it obtains parsing rules from our server, and these rules can be updated. Therefore, security depends not only on the extension code but also on the server side.

Within the team, we conduct code audits of all components—the extension itself, the API, and the parsers. We value our reputation and will not allow malicious functionality into the project.

If you still have doubts, here are two simple ways to reduce risks when using it:

Create a separate browser profile or use a different browser exclusively for working with betting sites and the extension.
Enable the extension only when you need to load betting history, and keep it disabled at all other times.

This minimizes any risks and helps you use the tool safely, even if there’s a lack of trust.