GDPR compliant version still phones home
I just tested AOMEI Backupper Free For GDPR Compliance (what a name!).
So, basically, this is just Backupper v4.1.0 Standard, with some nonsense about the GDPR. All the info that's included has no real meaning to the end user.
The real difference is in the form of two sentences in the User Agreement, stating that the User Experience Program is optional. However, there is no way whatsoever to check whether the UX program is enabled or disabled from within Backupper, even though the User Agreement states that it should be possible to enable/disable this at any time. The file
What's more, at every start-up, AOMEI Backupper still tries to phone home, even if "Check for updates automatically" is disabled (which can be configured from within Backupper, or in the file
Another possible explanation is that versions after v4.1.0 have new telemetry / data collection methods implemented, and that this older version is simply the only version that is still agreeable to be used by users in the European Union.
So, basically, this is just Backupper v4.1.0 Standard, with some nonsense about the GDPR. All the info that's included has no real meaning to the end user.
QtNetwork4.dll
and QtWebKit4.dll
are included just to be able to show this "information":AOMEI's mission is "Always Keep Global Data Safer". Data security and its protection are our priority. We are committed to providing users with products and services that are ready to be used in accordance with GDPR.<br> * Examine our products and websites, and change the way of personal data collecting. <br> * Ensure the appropriate, transparent and plain contractual privacy statement is in place. <br> * Continue to invest in our infrastructure against security breaches. <br> * Monitor the guidance around GDPR compliance and adjust our privacy if it changes.<br>
other.ini
does include the setting[UserExperience]<br>ExperienceValue=0However, this exact value is also present in AOMEI Backupper Standard (non-GDPR) and there is no way to check if this setting is actually honored.
What's more, at every start-up, AOMEI Backupper still tries to phone home, even if "Check for updates automatically" is disabled (which can be configured from within Backupper, or in the file
backuprecovery.ini
via[CheckUpdate]<br>AlwaysCheck=0<br>
Conclusion
As far as I can see, there is no actual difference between Backupper Standard and the GDPR Compliance version, other than some vague statements in a dialog. Backupper GPDR still connects to the AOMEI servers at start-up and there is no new or improved way to control what is being sent. All this, combined with the fact that they're dedicating a whole page to these separate versions (and the accompanying publicity it got) makes it seem like it is merely a publicity stunt, without the actual implementation of changes towards the betterment of the end user's privacy.Another possible explanation is that versions after v4.1.0 have new telemetry / data collection methods implemented, and that this older version is simply the only version that is still agreeable to be used by users in the European Union.
Comments
What still remains is that the program always phones home on start-up, even when both "Check for updates" and the UX program are disabled. Could you explain why?