WORLD OF FINAL FANTASY® takes a different path than usual products when it comes to game analytics and telemetry services. This is where the service provider Valve Corporation takes over the work and provides the respective services.
What does this product do?
As soon as the product is initialized, the Valve Corporations error reporter activates in the background and sends system, & - user data to the network.
In addition to data collection, the game includes an optional multiplayer mode, which was also implemented via the Valve Corporation server structure.
Since Steam is of course allowed in everyone's own security environment, it is difficult to notice that unwanted data loss takes place here while the product WORLD OF FINAL FANTASY® itself does not reveal any irregularities. For manufacturers a good method to transfer data past security software since everything runs via the client.
Privacy,- User Agreement
An
End user licence agreement can be found on the
product page on Steam in several languages.
Who is running the product?
Square Enix Co. Ltd.
Where are the service providers located?
Square Enix Co. Ltd. - Shinjuku, Yamanashi, Japan
Valve Corporation - 10400 NE 4th St, Suite 1500, Bellevue, WA 98004 United States
Akamai Technologies, Inc. - Cambridge, Massachusetts, United States
Akamai provides the server structure for Valve Corporation and thus serves as the endpoint
What data is collected?
BuildIDs, timestamps, Ipv4, Notes, Plattform, Productname, Start/Endtime of using the product, Steamuniverse, Theme, Url, UserID, Vendor, Version, Upload of Minidumps/System data and more
Means to an end uploads are realized via multiform upload. Depending on each file, several MB may be required.
Can the behaviour be blocked?
Yes, and it should. Because the so called Error-Reporter is used by several games and the platform itself as telemetry service. Uploads of user data are usually not even made with consent or even notice.
Deletion of files
Many paths are known to lead to the goal. So also here, because users have different possibilities to counteract the behavior.
Step 1: Deletion of files - Method 1
Delete "steamerrorreporter64.exe" and "steamerrorreporter.exe" from Steam installation folder. Please note that unless the Steam software is blocked by the update process at every start, these files will be renewed again and again.
To prevent this, a new file must be created in the installation directory. This is called "steam.cfg"
To be created with a simple text editor. Opens the file and adds
BootStrapperInhibitAll = enable
BootStrapperForceSelfUpdate = disable
This will exclude the client from updates and give you peace of mind. If you still want to update the Steam client, delete the CFG or rename/copy it to another location at short notice.
The CFG is also helpful if you generally do not want the client to update itself. Currently interesting for people with Windows 7 or for people who are simply fed up with the "improvements".
Step 1: Deletion of files - Method 2
1. Create a desktop shortcut for Steam on your desktop
2. Right click, settings, target
Target path directs to your "steam.exe" as example "c:\programs\steam\steam.exe"
After that, paste following:
-nobootstrapupdate -skipinitialbootstrap
The whole then looks like this
"c:\programs\steam\steam.exe -nobootstrapupdate -skipinitialbootstrap
Apply and start Steam.
1. nobootstrapupdate: Blocking Update checks of Steam
2. skipinitialbootstrap: Disable integrity checks of Steam files and processes
Step 1: Deletion of files - Method 3
Instead of using the commands " -nobootstrapupdate -skipinitialbootstrap" use "-noverifyfiles" for the Steam shortcut.
"c:\programs\steam\steam.exe -noverifyfiles
The dis/advantage of this method is that when the client updates itself, it also simply rewrites files that have already been deleted, so that they have to be deleted repeatedly. However, the client remains updateable.
Step 2: Block Ipv4
Block IPv4
208.64.203.140, 208.64.203.173, 23.55.163.64
The Ipv4 addresses should be blocked in a firewall. Unfortunately, Valve now also performs secret uploads via "steam.exe" and directly via IP, so that, for example, a block in a hosts or PI-Hole alone is no longer sufficient.
Step 3: Block URI
crash.steampowered.com
collector-01.valve.net
collector-02.valve.net
Use a host file to block connections or (if available) systems such as Pi-Hole, PF-Sense or others.
Note at the end
The product can only be launched via the compatibility mode in Windows. Admin rights are required via the Steam Client, no admin rights are required via the direct start in the installation directory.
DRM?
Yes,
SteamStub
