Privacy Policy for Hispania: Royal House

Last updated: 2026-09-15

Publisher: Halolex Studios. Game creator: KroryenDev / Kroryan. Privacy contact: Hololex@kroryandev.com.

Summary

Hispania: Royal House is a narrative Android card-decision game. The planned version does not include advertising, third-party analytics, in-app purchases, account creation or user tracking. The game optionally supports cloud save functionality through Google Play Games Services.

Data we do not collect

We do not directly collect name, email address, precise location, contacts, photos, camera, microphone, browsing history, financial data or health data. We do not sell personal data. If the user chooses to use cloud saves through Google Play Games Services, Google may process account identifiers and game progress data as required to provide synchronization features. Halolex Studios does not access, store or use this information for advertising or profiling purposes.

Local save data

The game may save progress, language, theme and dynasty state locally on the device through preferences or local files. If the user enables cloud saves through Google Play Games Services, game progress data may also be synchronized and stored using the user's Google account. Local data remains on the device and is deleted when the user clears app data or uninstalls the app, except for Android system backups or cloud saves managed by Google.

Optional bug reports and logs

If a bug report button is enabled, sending a report will be initiated by the user. The report may include the description written by the user, app version, device model, Android version and technical logs related to the failure. This data will only be used to diagnose and fix bugs. It will not be used for advertising and will not be sold.

Data sharing

We do not share personal data with advertisers. If cloud saves are enabled, game progress data is transmitted to and processed by Google through Google Play Games Services solely to provide synchronization and backup functionality, in accordance with Google's privacy practices. For more information, please refer to Google's Privacy Policy. Bug reports, if enabled, may be received through technical services needed to manage issues, for example email, GitHub Issues or another system indicated on the report screen.

Security

When a bug report is transmitted, it should use modern encrypted channels when the service allows it, for example HTTPS or TLS email. Please avoid writing passwords or personal data in bug reports.

Retention and deletion

Local data is retained until the user clears app data or uninstalls the app. Cloud save data managed through Google Play Games Services is retained according to the user's Google account settings and Google's retention policies. Bug reports are retained only for the time reasonably necessary to investigate, fix and document the issue. You can request deletion of bug reports through the privacy contact channel.

Children

The game is not designed to collect data from children and does not contain behavioral advertising. If we discover that personal information from a child was received in a bug report, it will be deleted when reasonably possible.

Changes

This policy may be updated if features such as bug reports, logs, analytics or external services change. The version published at this URL is the current version.

Note for Google Play Console

Complete the Google Play Console Data safety section consistently with this policy. If cloud saves through Google Play Games Services are enabled, declare the corresponding data processing required for save synchronization. If optional bug reports with logs are enabled, declare exactly which technical data is sent, that it is optional, user-initiated and used for app functionality and diagnostics.