Privacy Policy for Idleventure

Last updated: November 2, 2026

Idleventure is an offline-first fantasy idle RPG published under the developer name SalTech Games. This notice describes local game data, optional analytics, crash diagnostics and support communications.

1. Data Controller and Contact

The data controller is Salvatore Granata, an individual developer based in Italy, publishing under the name SalTech Games.

For privacy requests, contact saltech.games@gmail.com. The game does not require registration, a player account, or direct contact information in order to play.

2. Local Game Data

The game stores the nickname selected by the player and information such as character levels, class, progression, inventory, equipment, virtual currencies, talents, pets, achievements, daily rewards and preferences on the device for gameplay and saving progress. This information is not automatically uploaded to a developer-operated cloud-save service. The nickname is not intentionally included in Firebase events or diagnostic custom data.

Clearing app data, uninstalling or resetting the device may erase progress. Android/OEM transfer behavior may vary by device configuration.

3. Exporting and Importing Saves

Players can choose to export and import game backups. The exported JSON file is readable and may contain the nickname and game progress. Players choose where to save it, including external storage or a cloud provider. If a third-party destination is selected, that provider's own privacy terms may apply. The developer does not automatically receive exported backups, and removing local game data does not delete previously exported copies.

4. Optional Firebase Analytics

The game integrates Google Firebase Analytics to understand features used and improve gameplay and balance. Analytics collection is disabled by default and can be enabled only through the in-game choice. Players can accept, refuse or later withdraw consent in Settings. Refusal does not restrict core gameplay.

When enabled, Analytics may process gameplay events, app interaction and engagement statistics, device and app information and technical SDK-generated identifiers such as app-instance IDs. These data are not necessarily anonymous. The developer does not intentionally send player names, email addresses or chosen nicknames as event parameters. Advertising ID collection is disabled for Firebase Analytics, and the release manifest does not declare the Advertising ID permission.

Purpose and legal basis: measurement and improvement of gameplay based on the player's consent (GDPR Article 6(1)(a)). Withdrawal prevents further collection through the configured SDK controls; it does not automatically erase previously collected records.

Retention: the Google Analytics property is currently configured for 2 months of event-data retention and 14 months of user-data retention for records covered by these controls. Reset on new user activity is enabled. These settings do not govern every aggregated report or all records held by Google.

5. Firebase Crashlytics

Google Firebase Crashlytics helps identify and fix application crashes and technical failures. It operates independently of the Analytics consent choice. Crash reports may contain device model, Android and application version, stack traces, crash timestamps, technical logs, installation or session identifiers and, when recorded by the application, gameplay diagnostic context. These data can constitute personal data and should not be described as completely anonymous.

Purpose: troubleshooting, technical maintenance and app stability. The developer considers the legitimate interest in maintaining a stable and secure app (GDPR Article 6(1)(f)) as the basis for necessary diagnostic processing, subject to applicable requirements, including rules on access to information stored on devices. This is distinct from consent to optional Analytics. For questions or objections regarding processing, contact the developer using the email in this notice.

Google's published Firebase documentation describes Crashlytics retention of relevant diagnostic data for approximately 90 days before its deletion process begins. See Firebase privacy information.

6. Local Notifications

The game may schedule local Android notifications concerning gameplay reminders or available rewards. This does not require a developer-operated remote notification service or Firebase Cloud Messaging. Notifications can be managed through Android's settings.

7. Advertising and Purchases

Idleventure currently has no advertisements, in-app purchases or subscriptions. There is no required player login. If these features are introduced later, this notice and applicable disclosures will be updated beforehand.

8. Support Requests

If a player voluntarily emails the developer, the email address and any information included in the message will be processed to respond. The relevant basis depends on the request, including steps requested by the player, legitimate interests in providing support and applicable legal obligations. Correspondence is kept only as needed for the request and applicable obligations. Please avoid including unnecessary sensitive information.

9. Third-Party Services and International Transfers

Google provides Firebase Analytics and Crashlytics. Related technical data may be processed using Google's international infrastructure, including outside the European Economic Area. Where international transfers occur, applicable Google contractual measures and safeguards, including standard contractual clauses when relevant, govern the service relationship. Details are available in Firebase Privacy and Security, Firebase terms and Google's Privacy Policy.

The developer does not sell player data. The handling of Google as a service provider for app-store data-disclosure purposes is assessed separately under the applicable rules.

10. Retention and Deletion

Local game progress remains on the player's device until removed using the game's or Android's controls, or until the app is uninstalled. Exported files remain at the locations chosen by the player. Analytics and Crashlytics retention are described above. Disabling Analytics does not necessarily delete data sent before withdrawal. Requests about available access or deletion options can be sent to the privacy contact address.

11. Data Security

Local game data is stored using Android application storage and platform protections. Exported JSON backups are readable and should be stored carefully. Firebase services use the protection measures described by Google. No data processing system can guarantee absolute security.

12. Privacy Rights

Where GDPR applies, individuals may have rights of access, rectification, erasure, restriction, portability (where applicable), objection to certain processing and withdrawal of consent without affecting previous lawful processing. Requests may be sent to saltech.games@gmail.com. Because the game does not use accounts, locating some technical records may depend on available identifiers. Individuals may also lodge a complaint with the relevant supervisory authority, including Italy's Garante per la protezione dei dati personali.

13. Children

The game does not require account creation or directly ask for a child's name or email address to play. The intended target audience is stated in its Google Play listing. Applicable safeguards for children's data remain in effect, including requirements concerning consent where relevant. Parents or guardians with privacy concerns can contact the developer.

14. Updates and Contact

This notice will be updated when the game, data practices or legal requirements change. The revision date appears at the top of this page.

Controller: Salvatore Granata (independent developer; public name SalTech Games), Italy.
Email: saltech.games@gmail.com
Privacy policy: https://saltaek.github.io/idleventure/privacy_policy.html