Oddwire uses optional gameplay reporting to improve Mythspire. You can decline and still play the whole game, including offline.
Play summaries include run starts and finishes, content unlocks, heroes, spells and builds, visible pre-run choices and menu navigation, damage, deaths, boss fights, available upgrade, replacement, inscription, chest and encounter offers and choices, short damage and danger histories, ultimate timing, healing, shields, control effects and supported attack outcomes, gold earned and spent, purchase affordability, shrine and chest outcomes, voluntary health payments, levels and enemy pressure over time, equipment and build modifiers, gameplay frame timings, sampled render timings and process memory, device thermal state, battery level, charging and low-power state where supported, device model, operating system and game version. Random installation and session identifiers connect play reports. If you choose to share your Support ID, we can look up your retained play reports; the ID does not contain your name or store account. Problem reports include the text you choose to send and the technical context shown before sending.
Crash and script error reporting includes stack traces and technical device information. We disable screenshots, saved-game attachments, logs and local script variable capture. We do not request your name, email, Apple or Steam account, advertising identifiers, contacts or location for gameplay reporting. We do not use advertising or cross-app tracking.
Cloudflare hosts gameplay collection and our private dashboard. Sentry processes crash and error reports. Those providers necessarily handle connection information, including IP addresses. We do not store IP addresses in the gameplay database. Store operators process purchases and downloads under their own privacy policies.
The game can queue play reports offline, up to 10 MB or 30 days, and sends them between fights. Detailed server run reports target 30 days; activity and feedback target 90 days. Compact playtime, activity, run-to-run timing, content-unlock and boss-attempt history linked to a random installation ID, and daily grouped totals, remain for 13 months. The compact history supports unique-player counts, first-victory analysis, repeat-play and unlock-pacing reports and is included in Delete Play Reports. Maintenance is incremental and cleanup can lag under load. Version and patch history does not contain player identities and is retained indefinitely. Private recovery backups, when enabled, target seven days of retention; cleanup can lag after backup failures. Deletion removes active identifiable gameplay records, while existing backup copies expire through this rotation. Deletion requests must be reconciled before a backup is restored. Crash reports use the retention configured for the Sentry project.
Use Settings → Privacy & Reports to turn sharing off. This clears pending play reports and stops new reporting. Delete Play Reports also queues an authenticated deletion request for identifiable gameplay records; it takes effect when you next connect. It does not affect saves, progress or purchases. Grouped history contains no installation IDs and cannot be linked back to your installation. This button does not remove crash reports already held by Sentry.
For questions, crash-report removal requests or other privacy requests, contact oddwiregames@gmail.com. Please do not include passwords or other sensitive information in a problem report.