Before this service launches publicly
This is the policy for the current development site. The operator's legal identity, dedicated privacy contact, hosting provider and location, and backup retention details still need to be confirmed and published before public deployment. The planned game telemetry described below is not collecting data yet.
What a bug report contains
If you send a report, we store its title, category, platform, description, any reproduction steps and expected behaviour, and the game version if you provide one. An email address is optional. We also record when the report arrived and the team's private triage notes, status and priority. You can report a bug without creating an account or providing your name.
We use this information to understand problems, investigate them, improve the game and, if you supplied an email address, ask about your report. Providing an address does not sign you up for marketing. Reports are private to the team; they are not displayed on the website or sold to advertisers.
Send only what you are comfortable sharing
Please leave out passwords, login tokens, payment details, sensitive personal information and other people's details. Remove personal file paths and usernames from any text you copy. The current form accepts text only; it does not upload screenshots, saves, crash dumps or other files.
We encrypt the optional contact email in the database. Other report text is not separately encrypted by the application, so please keep private information out of it. Authorized administrators can read reports and contact addresses to handle support. Encryption does not make information anonymous.
Cookies and connection information
The website uses first-party session and form-security cookies to keep forms working and protect them from forged submissions. Administrator sessions also use cookies for sign-in security. These cookies are not used for advertising or to follow you around other websites. The current public site has no analytics scripts, advertising trackers or tracking pixels, and its fonts and images are served locally.
Like other websites, the server receives your IP address, browser information and the page requested. This information may appear in hosting access or security logs and is used to operate the service, rate-limit requests and investigate abuse. Your IP address and browser details are not added as fields to your bug report. We do not use them to build advertising profiles.
Links to Steam or other external services take you to sites with their own privacy policies. They do not receive a copy of your bug report from this website.
How long information stays
The application has a daily cleanup for bug reports older than 180 days, including any contact address and internal notes stored with them. That cleanup must be enabled and checked when the website is deployed. We may remove a report earlier when it is no longer needed or following a valid deletion request.
The recommended public hosting setup keeps access logs for 14 days; the actual hosting log settings and backup expiry must be confirmed before launch. Deleted information may remain in restricted backups until those backups expire. We will publish those periods here before the service opens publicly.
Who can access it
Access to reports is limited to authorized team administrators using an additional authentication factor. Hosting and backup services may process stored information to run the website on our behalf. No live provider, storage region or international transfer arrangements have been selected for this development site; those details will be added before deployment. We may need to share relevant information if legally required, or to address a security incident.
Optional game telemetry
We are building an optional reporting service at playturnaround.com. The client and API are implemented for testing, but production uploads are locked until Turnaround has its own Steam AppID, server credentials and a reviewed deployment. Purchasing the domain does not enable collection. Leaderboard submissions are not open.
The game asks before collecting information for upload. Four independent choices start off: performance information, progression information, crash diagnostics and community totals. You can continue without sharing and play offline normally. Settings lets you inspect and change each choice. Declining does not start a telemetry login or upload, and sharing does not add advertising or tracking scripts.
- Performance: a frame-time histogram and frame/hitch counts over a short sample, rendering mode, graphics preset, game speed and the number of stands, passengers and vehicles. These help us find slowdowns. We do not send frame-by-frame recordings or hardware serial numbers.
- Progression: selected milestones such as a first flight, airport grade, goal, equipment unlock or hire, with a random career ID, source-event sequence, minutes played, game day and game speed. We do not send your airport layout, money history, passenger names or the full career log.
- Crash diagnostics: an unexpected-exit or managed-exception category, a diagnostic signature, uptime and a coarse game phase. When available, a managed exception can include its type and up to 20 structured stack frames containing type, method and module identifiers. No exception message, file path, raw log, save, screenshot, crash archive or memory dump is uploaded automatically. An unexpected exit may also be a force quit or loss of power.
- Community totals: new completed-flight events with their career ID, source sequence and game day. We may later publish reviewed combined counts, for example flights turned around by participating players. Collection is not a guarantee that a count is accurate; it remains client-reported, and individual histories are not public. Passenger totals are not part of this initial upload format.
Each upload also contains a schema version, an opaque account identifier and random installation/session/event identifiers, game build and release channel, operating-system family, a timestamp rounded to the minute and the current consent revision. We use those fields for compatibility, deduplication and understanding which release a report concerns. This information is pseudonymous, not anonymous.
Steam authentication and your choices
Only an enabled online choice, or a pending withdrawal/deletion that you requested, can start the reporting connection. Steam supplies a service-specific authentication ticket. Our server checks that ticket and game ownership with Valve. It stores a keyed hash of your Steam ID rather than your public profile or raw Steam ID, and issues a short-lived reporting token. Tickets and raw tokens are not retained in analytics. Administrator sign-in is separate; a game account cannot enter the admin panel.
We record the selected choices, notice version, decision time, receipt identifier and revision so we can enforce and evidence your choice. Consent is checked again when a batch is accepted. A stale device cannot silently overwrite a newer withdrawal. Account-linked data and the connection's IP address mean we cannot describe these uploads as anonymous.
Turning a choice off stops collection on that device and clears its unsent data immediately. The game sends the withdrawal when it can connect; until the server acknowledges it, Settings shows that it is pending. The game keeps working throughout. The server removes stored raw events for withdrawn purposes. Re-enabling sharing does not upload events from the period when it was off.
Delete my uploaded data in the game requests removal of your reporting account, raw measurements and associated consent/deduplication records and revokes its reporting tokens. It does not delete local airport saves or a separately submitted website bug report. Offline requests remain pending locally; completion is shown only after the server confirms deletion. Restricted hosting logs and backups expire separately. No public leaderboard entries are created by this telemetry service.
Telemetry retention and access
The implemented daily cleanup removes raw telemetry after 30 days, deduplication hashes after 90 days and consent receipts after 180 days. Inactive reporting accounts are removed after 180 days, including their linked records. Career sequence watermarks prevent replayed events returning while the account exists. Cleanup depends on running the scheduler in the deployed service.
Telemetry is private to authorized team administrators for debugging and game improvement. The first version publishes no player-level telemetry or automatic public counter. Any future public totals require a separate review and only non-identifying combined results. Leaderboards, public names and their moderation will have their own participation flow before they open.
The hosting service receives connection data, including your IP address. Our operational logging periods and backup limits above apply separately. Valve receives the authentication/ownership checks under its own privacy arrangements. Before production activation, we will publish the actual operator, contact, processing locations and providers, and update this notice if the enabled fields or purposes change.
Questions, corrections or deletion
You can ask what personal information we hold about you, request a correction or deletion, or raise a concern about its use. Depending on applicable law and the circumstances, you may also have rights to restrict processing, object to it or receive a copy. We may need enough information to identify your report and confirm that it belongs to you, without asking for unnecessary identity documents.
Until a dedicated privacy contact is published, use the report form with “Privacy request” in the title and an optional email address if you want a reply. Share only enough to locate the relevant report; do not send passwords or identity documents. If you omitted an email from your original report, identifying it may take more information. You can also raise a concern with your local data protection authority; in the UK, that is the Information Commissioner's Office.
When this policy changes
We will keep this page dated and update it when the service changes. We will explain new collection before it begins and request a new choice where needed. Sending a bug report does not grant permission for unrelated game analytics.