This notice explains what information Enter the Chronosphere may collect, what it is used for, and the important difference between anonymous analytics and optional bug reports.
Publisher and Contact
Enter the Chronosphere is developed by Effort Star and published by Joystick Ventures.
For privacy or data protection questions, contact us at contact@effortstar.games.
How Data Is Captured
Analytics are sent only if analytics are enabled in the game. Optional bug reports are sent only when you choose to submit a bug report from inside the game.
Analytics
If analytics are enabled, the game may send anonymous usage and performance information to Google BigQuery. These analytics are used only to understand whether the game is working as intended, how it is performing, and where improvements are needed.
Analytics help us answer practical development questions, such as which features are being used, which areas may need more attention, how many people return to the game over time, daily and monthly active use, and performance measurements such as boot-up time.
Analytics are anonymized. Each player is represented by a generated identifier that lets us connect related analytics events together, but the identifier is not connected to your name, email address, Steam account, or other directly identifying information. Analytics may include basic technical information such as your operating system, for example Windows or macOS.
Analytics may include error events or error counts so we can understand how often problems happen. Analytics do not include Unity logs, save data, screenshots of the game, or crash reports.
Bug Reports
Bug reports are optional. If you choose to send a bug report from inside the game, the report is sent to us through a Discord webhook and may include save data, Unity logs from your previous and current session, screenshots of the game, and crash reports.
Logs can be more sensitive than analytics. They may include technical details such as your Steam user ID, local file paths, your operating system username as part of a file path, hardware or operating system details, error messages, and recent game activity related to the issue. Bug reports do not ask for explicitly identifying information, but logs can sometimes contain information that is indirectly identifying.
We use bug reports only to reproduce, diagnose, and fix problems with the game.
How Data Is Used
We use analytics to check game performance, understand whether features are working as intended, measure general use such as daily and monthly activity, and decide where the game needs improvement. We use bug reports to investigate specific issues reported by players.
Sharing and Sale
We do not sell, rent, or monetize analytics or bug report data. We do not use this data for advertising, ad targeting, or profiling outside the operation and improvement of the game.
We do not share this data with third parties for their own purposes. Data is handled only through the services needed to operate these systems, including Google BigQuery for analytics storage and Discord for optional bug report delivery.
Retention
We may keep analytics, bug reports, and related records indefinitely. This helps us understand long-term game performance and stability, investigate issues over time, maintain records of fixes, and improve the game.
Your Choices
You can choose not to enable analytics. You can also choose not to send bug reports. Not enabling analytics or not sending a bug report does not stop you from playing the game.