Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Thanks for your question. No, there is no way to turn this off.
This is illegal in the EU. You're not complying with the GDPR.
Will you offer a solution to this issue?
A few points on GDPR:
- Consent has to be explicit. Merely showing the EULA and having you press accept is not satisfactory (very few people actually read it). Especially when the data collection isn't necessary for the game to work (it's a single player game that should be playable completely offline). Most people playing this game won't even be aware it has telemetry.
- It requires that collection of personal data be limited to what is necessary to the purposes for which they are processed. If the telemetry is for bug fixing/improving the game, they have no reason to need to know WHO that data is connected to. And they do collect account information (which can be anything really). Collecting PII (personally identifiable information) also means that GDPR is a lot more strict about it.
- A user has the right to object and withdraw consent at any time. The game does not provide an option to turn off telemetry. In addition, as mentioned earlier, the telemetry isn't necessary for the game to function. Which brings us to the following:
- Consent must be "freely given". In the context of GDPR, this means that the player must have a real choice. If you are not able to play the game without giving consent, and that data isn't necessary for the game to function (like login information in an online game, for example), it would be viewed basically as coercion under GDPR. Which means it's not "freely given".
- GDPR explicitly states that the provision of a service should not be conditional upon the consent to process personal data that is not necessary for the performance of the service. See all the points above about how it's a single player game that doesn't need the telemetry to function and the previous point about "freely given".
If you live in a country protected by GDPR, you should probably contact the relevant authorities about it. Just explain the above, about how it collects personal information not required for the service to function, and provides no way of opting out of said collection.
Thank you.
Upon launching the game, I got to the options menu and see this:
https://pasteboard.co/EECuwFvnXzWb.png
Everything turned off by default. Let's you select what you want to share. Lets you see what information has been uploaded, etc.
It's not that hard.
There's a chance that the game exe calls some other program installed on your computer and routes data out that way, I've seen other games do it this way to be sneaky. If that's the case you simply repeat the steps above. Firewalls don't just keep things out, they can keep things in. You can do this same process for other games.
I was interested in the game and this kind of issue is frankly an immediate no-buy from me, and furthermore will put the entire studio on my ignore list in the future.
Same here. Not a good look and I really enjoy the SteamWorld games. The publisher was hoping no one would notice and this makes the Dev's look bad even though id bet they had no choice in the matter.
It's number 4 in the TOS. How did you miss that, resulting in "looking into it" after releasing the game?
Wew
It outright states no you're responsible for everything. Maybe you shouldn't just contact the authorities, but Microsoft as well. I wonder if they'd continue offering their services if they know that the devs are trying to make them liable. Point 4.10. has information on how to contact them.
I understand your frustrations, but I would like to point out that I am in fact the community manager and I had no say or input in the implementation of this.
The concerns raised by the community have been noted and shared with the wider team, who are now looking into this matter diligently.
When I have more information to share, I'll be able to do so.
I have noted and raised the community concerns about this matter with the team. When I know more, I will be able to share. I kindly ask for your patience.
Many of us are still very interested in this title if the "oddities" can be worked out in the future.
Thank you,
My role is to share community feedback with the team. There isn't anything more I can do at present. I can, however, reassure you the correct people are dealing with the matter as quickly as possible.