- Can we drop support for Windows 7?
- Can we drop support for Direct3D Feature Level 9_1 and 9_3?
What data will be collected?
You can browse the code updates which display the information in the log file and utilities, which will also be used for this telemetry. The following example shows what we'll collect about the application (Open Rails), runtime (.NET), system (OS), and hardware:
Application = Open Rails U2023.11.23-0122 (X64) Runtime = .NET Framework 4.8.9181.0 System = Microsoft Windows 11 Home 10.0.22621 (X64; en-GB; en-GB,en-US,ja-JP) Memory = 32,592 MB CPU = 12th Gen Intel(R) Core(TM) i7-1255U (GenuineIntel; 12 threads; 2,600 MHz) GPU = Intel(R) Iris(R) Xe Graphics (Intel Corporation; 1,024 MB) Direct3D = 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Where will data be sent?
All telemetry will be sent to telemetry.openrails.org (nothing there currently). It will be collected by this web application (nothing there currently), which will also provide processing and analysis functions later.
How is it anonymised?
Only the information shown above will be collected, which contains no personally identifying information. However, since specific combinations of data (e.g. CPU + GPU) might narrow down data to specific users (even if we cannot identify them), we will only store and process the data in the following ways:
- Analysing a single field's range of values (e.g. users grouped by GB of system memory)
- Analysing multiple fields as cutoffs (e.g. how many users have >= 8 GB system memory and Direct3D >= 10_0)
Additionally, if any analysis we perform returns too few users in a group, we may choose to keep the results private to avoid potential singling out users.
What about IP addresses?
We cannot avoid IP addresses when an application communicates with a server; however, we will not be able to link them to any telemetry because:
- IP addresses will only be recorded in the standard web server access logs
- Telemetry data will be recorded without a timestamp (i.e. only the date)
Thus, we will not be able to link the data back together later. The code for this web application (nothing there currently) will be public to validate this claim.
Who will have access to data?
All telemetry data will be securely stored on my server, which already hosts a number of other Open Rails items (e.g. update checks). Nobody else has been granted access to the server, but Chris (ORMT) and Mythic Beasts (the hosts) may be able to access it through the administrative control panels.
We will be providing processing and analysis functions in this web application (nothing there currently), which will read the data and provide aggregated information as a public website.
How will opt-in work?
We want to collect this data from only a small sample of users (at least initially) so, when you launch Open Rails, it will assign you a random number from 1-1000 and save it. If that number within the chosen boundary (e.g. 1-10 would select 1% of users), we will explicitly ask you about the telemetry. You will have three options:
- Yes - opt-in saved
- No - opt-out saved
- Later
If you choose to opt-in or opt-out, we'll save that and never ask again (unless we want to change the data collected). You will always be able to change your decision in the menu and we will not be collecting any information on opt-in or opt-out. Even if you are not "selected", you will always be able to opt-in or opt-out in the menu, so anyone can participate.
When is the data collected?
Similar to the existing update checks, the telemetry is only collected and sent when you run Open Rails. If you do run Open Rails, telemetry will only be collected once per week. It will be automatically uploaded after collection. Your computer will need to be online to send the telemetry.
Current status
Decide on data to collectDecide on data format- JSON- Decide on data collection system - probably .NET web app?
- Update Data Collector and log file with new data - in progress
- Add invitation system
- Add invitation screen
- Add data collection system
Questions?