Elaztek NTLauncher Data Collection & Logging


Being transparent and not keeping skeletons locked away is part of our mission statement at Elaztek Studios. This page shows details on the various logging levels in the Elaztek Launcher. By default, this is set to BASIC in order for us to get general system information. You are free turn off info logging outright, or set it to full to help us out a bit more if you wish. Keep in mind: we do not recieve ANY data if you have "Allow anonymous sending of logs to Elaztek Studios" disabled - it will only appear in local logs. This way, if you so desire, you can actually view EXACTLY what will be sent, exactly as we will see it before doing so. We also have a handy list here that details all the logging levels.
Level Information Gathered
None
  • No data is collected with this setting.
Basic
  • Operating System
  • Whether or not the OS is 64 bit
  • The name of your PC
  • Number of CPU's and/or number of CPU cores present in the system
  • The OS directory (by default, this would be C:/Windows/system32, or C:/WINNT/system32 on older computers)
  • CLR Version
  • The maximum size of the page/swap file
  • Amount of memory available to the launcher
  • Tick count
  • CPU Name
  • CPU Manufacturer
  • CPU Description
  • GPU Name
  • GPU Compatiability (Manufacturer)
  • Amount of System Memory (in MB)
Full
  • Operating System
  • Whether or not the OS is 64 bit
  • The name of your PC
  • Number of CPU's and/or number of CPU cores present in the system
  • The OS directory (by default, this would be C:/Windows/system32, or C:/WINNT/system32 on older computers)
  • CLR Version
  • The maximum size of the page/swap file
  • Amount of memory available to the launcher
  • Tick count
  • The username of the currently logged in user
  • The domain that the computer belongs to
  • Screen orientation
  • Whether or not a Security Manager present
  • Virtual screen size
  • Whether or not UI effects are enabled
  • Primary monitor resolution
  • Whether or not Windows for Pen Computing extensions are present
  • Whether or not DBCS Characters enabled
  • Whether or not a Debug USER.EXE is present
  • Kanji window height