Vampir Köylü Privacy Policy

Effective date: 21 August 2026

This policy describes the current offline game architecture and the Google AdMob / Google Mobile Ads SDK and Google User Messaging Platform (UMP) integration used in advertising-enabled Android builds.

1. Controller and contact

Developer/data controller: {{DEVELOPER_NAME}}.
Privacy and support contact: {{SUPPORT_EMAIL}}.

2. Information processed by the app itself

The app does not create user accounts, does not provide a sign-in system, and does not upload gameplay progress to a developer-operated server. The display name chosen by the player is processed locally on the device during the game session and is not sent by the game logic to developer servers.

3. Advertising and third-party services

Advertising-enabled builds may use Google AdMob / Google Mobile Ads SDK to display and measure advertising. Where required by regional law or Google policy, a consent/privacy choice flow may be shown through Google UMP.

Depending on platform and configuration, Google Mobile Ads SDK may process data such as:

Such data may be processed by Google and relevant advertising technology providers for ad delivery, measurement, analytics, fraud prevention, security, and compliance. Personalized advertising is provided only to the extent permitted by applicable consent/permission status and law.

4. Sharing

The developer does not upload the player's in-game display name or discussion text to developer servers. In advertising-enabled builds, device, advertising, interaction, and diagnostic data processed by the Google Mobile Ads SDK may be shared with Google and relevant advertising service providers.

5. Security

Google states that user data transmitted by the Mobile Ads SDK is encrypted in transit using TLS. Because core gameplay data is not sent to developer servers, the developer does not maintain server-side records of player names or game discussions.

6. Retention and deletion

The developer does not maintain a user account or persistent server-side player profile. Local app data can be removed through the operating system by clearing app data or uninstalling the app.

Retention and deletion of advertising data processed by Google/AdMob are governed by Google's policies and user controls. Android users can reset or delete the advertising ID in device settings. Where UMP privacy options are required, users can manage advertising choices through the available privacy options entry point.

7. iOS tracking permission

If advertising/tracking functionality is enabled in an iOS build, uses that link user or device data across third-party apps or websites for tracking require permission through Apple's AppTrackingTransparency (ATT) framework. If ATT permission is not granted, the app will not access IDFA or perform tracking that requires ATT permission.

8. Children's privacy

Vampir Köylü is not designed specifically as a service directed to children under 13. If the store target audience is changed to include children, additional child-directed advertising and data rules must be implemented and this policy must be updated.

9. Rights and choices

Depending on applicable law, users may have rights to information, access, correction, deletion, objection, or withdrawal of consent. Because the developer does not maintain a server-side user account, deletion of gameplay data is generally handled on-device. Google's advertising and privacy controls may also be used for advertising data.

10. Third-party information

How Google uses information from sites or apps that use its services: Google – Partner Sites & Apps. Google Privacy Policy: policies.google.com/privacy.

11. Changes

This policy may be updated when app features, advertising providers, or legal requirements change. The current version will be posted on this page with the effective date above.

12. Contact

Privacy requests and questions: {{SUPPORT_EMAIL}}