Hi,
I'm not keen on doing that. I don't know what information is sent when I do.
I think a vicious circle is at play. Because Avast treats mining software as malware, it can only be installed by disabling shields. When re-enabling shields, all shields get activated, instead of just the ones that were previously active. This then includes anti-rootkit and anti-exploit shield. Which then delete mining software again. I set those shields to disabled, but then disable all via task bar options to reinstall the mining software, and when I then re-enable the shields there, it also re-enables anti-rootkit and anti-exploit.
Rinse and repeat.
I've set exceptions for folders and executables of mining software, but anti-rootkit and anti-exploit straight up ignore exceptions and quarantine files regardless. At least they did for a very long time. So now even if they don't, I don't trust they won't again in the future. Every Avast update is a gamble.
If Avast had an option to allow for mining software, and didn't ignore previous shield states when re-enabling, none of this would probably be an issue. These problems are a result of Avast not behaving logically or consistently.