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
You will probably find the client makes a connection but sends no telemetry.
Telemetry doesn’t imply personal data, it’s ANY data. If you disable it, no data should be sent. Ideally, they shouldn’t even attempt to connect to telemetry server.
Telemetry does not include PD according to their over-arching PN, which is why I stated the above re. GDPR: Only PD is in scope of GDPR, if it's not in the telemetry (and they state it is not) then the OP does not have GDPR compliance concerns. That does not mean he/she may not have other concerns, but they are not GDPR concerns.
Technical behaviour ultimately depends how the app is architected, it could make a connection to the endpoint but policy determines nothing goes over that connection or, more usually, only something very specific is sent (i.e., not the opt out data). e.g., very often MAU related signals are sent to drive understanding of consumption.
That said, when I check their privacy statement at the Telemetry Settings link, it's 'access denied':
https://legal.kingdomcomerpg.com/privacy/kcd2_pp_eng.html
I have just raised a privacy concern to the Plaion DPO and KCD2 support address, as that should be available so people can contact the privacy officer, check subject rights, determine exactly what is sent via telemetry, etc. Whilst there is a Plaion PN, the lack of a PN at this link is a concern because it could imply a gap against the over-arching Plaion PN and this element.
EDIT: I got a response from Plaion's DPO within 4 hours stating this is being looked into.
This again confirms that telemetry does not contain PD, so is out of scope for GDPR.
But as the poster said if you turn it off, it may still make a connection but doesn't send anything.
Paranoia isn't healthy, Don't worry about it. the devs are honorable.