Ruinveyl Privacy Policy

Effective date: September 2, 2026

Ruinveyl is developed and published by NgDinhNha. This policy describes privacy-relevant behavior for the Android version of Ruinveyl covered by release version 0.0.1.

Advertising and rewarded ads

Ruinveyl offers an optional rewarded advertisement that can reduce a selected pet-hatching timer after the advertising SDK reports that the reward was earned. Ordinary gameplay remains available when an ad cannot be loaded, consent is unavailable, or the advertising service fails.

The Android app integrates Google AdMob / Google Mobile Ads and Google's User Messaging Platform (UMP) consent flow through the project's reviewed native advertising bridge. Development and debug builds use Google's public test advertising identifiers. Production builds use Ruinveyl's production AdMob application and rewarded-ad identifiers.

Data handled by Google Mobile Ads

According to Google's current Google Play data-disclosure guidance for the Google Mobile Ads SDK, the SDK may automatically collect and share the following categories for advertising, analytics, and fraud-prevention purposes:

• IP address, which can be used to infer approximate/general location;
• user product interactions, such as app launches, taps, and video/ad interactions;
• diagnostic information related to app/SDK performance;
• device and account identifiers, including Android advertising-related identifiers where available and enabled.

Google states that data handled by the Google Mobile Ads SDK is encrypted in transit using TLS. Android advertising-ID handling is subject to platform/user controls and the exact packaged manifest/SDK configuration.

Google's disclosure guidance can change as the SDK changes. The release checklist for Ruinveyl therefore requires the Play Console Data Safety declaration to be checked against the exact SDK and manifest that are actually shipped.

Consent and privacy choices

Ruinveyl requests current consent information through Google's UMP flow before production rewarded ads are requested. Where a Google-configured privacy message is required, the app uses that consent flow before enabling ad requests. If the consent path cannot establish that ads may be requested, rewarded advertising remains disabled and gameplay continues without granting an ad reward.

Where the installed advertising bridge and Google-configured message require a privacy-options entry point, that entry point must be exposed and verified before public rollout. Consent test geography and test-device settings are development-only and must not be used as production-user consent substitutes.

Users can also manage platform-level advertising/privacy controls through Android settings and any privacy choices offered by Google's consent message.

Game data

Ruinveyl stores gameplay progress and settings locally for game functionality. The rewarded-ad integration does not grant gameplay rewards merely for loading, showing, dismissing, or failing an ad; a reward is applied only from the native earned-reward callback and is guarded against duplicate grant for one impression.

This policy does not claim that the advertising SDK collects no data. It also does not designate Ruinveyl as child-directed. Any age-rating, target-audience, families, or child-directed declaration must match the app's actual Google Play and AdMob configuration.

Retention and security

Ruinveyl does not define independent retention periods for data processed by Google Mobile Ads. Google's handling is governed by Google's applicable terms, policies, user controls, and the configured advertising/consent products. Local game saves remain on the device unless the user or operating system removes them; the current release does not describe an account/cloud-save service.

Release signing credentials, keystores, passwords, API tokens, and other private release material are not stored in the public source repository.

Third-party service

Google AdMob / Google Mobile Ads and Google User Messaging Platform are Google services. For current information about Google's privacy and advertising practices, consult Google's published policies and Mobile Ads documentation.

Contact

For privacy or support questions about Ruinveyl, visit the Contact page.

Changes to this policy

This policy may be updated when Ruinveyl's data practices, advertising SDK, consent configuration, or legal/store requirements change. The effective date above identifies this source revision; the public hosted copy should be updated whenever the shipped behavior materially changes.