OPTIONAL GAMEPLAY TELEMETRY · UPDATED FOR VERSION 0.14.1
Help us improve
the next voyage.
From version 0.14.1, Drydock’s gameplay telemetry is on by default for new profiles and profiles without a saved telemetry setting. Existing saved settings are preserved, including disabled settings from 0.14.0. A one-time popup explains collection before it starts and offers a “Turn telemetry off” button. You can also disable it at any time in Settings by unchecking “Share gameplay telemetry”. Turning it off stops collection, cancels pending requests, and clears events that have not been sent. Playing and updating the game work with telemetry disabled.
What is shared
- Game version, operating system, CPU architecture, and game language.
- Session starts, approximate session length, and a frame-rate category every two minutes.
- Which main screens are opened; campaign type, difficulty, modifier count, and progress.
- Battle mode, contract number, outcome, and simulated battle length. Replays are excluded.
- Update states such as “available,” “verified,” or “error.”
- For up to ten script errors per session: the game’s source file and line number. No error messages, paths from your computer, or stack traces are sent.
Each enabled session gets a fresh random identifier so related events can be grouped. There is no persistent player or installation identifier. Counts describe sessions, not unique people. An unfinished session marker may report that the previous session was interrupted; this does not establish that the game crashed.
What stays on your computer
Telemetry does not include your name, email, ship or captain names, designs, ship/run codes, save contents, typed text, device serial numbers, or precise location. Events waiting to be sent are kept only in memory and may be dropped when offline.
Where it goes
Events are sent over HTTPS to this website’s own collector at www.drydocks.space/api/telemetry, hosted on Fly.io. The collector does not put IP addresses, request headers, or user agents in its telemetry database, and request logging is disabled for this endpoint. Network providers still process connection information to deliver requests.
Events are available only to the game operator through authenticated server access. There is no public telemetry dashboard or public read API. Raw events expire from the active database after 30 days; a volume snapshot may retain an older copy for up to one additional day. Oldest events may be removed earlier if storage limits are reached.
Your choice
Use Settings → Share gameplay telemetry at any time. Turning it off cannot recall events already received; these expire automatically. Normal website requests and update downloads remain separate from gameplay telemetry and are needed to serve those pages and files.