Store compliance notes
This page is a practical checklist for filling store forms. It is not legal advice.
Minimum URLs usually needed
- Privacy Policy URL: privacy.html
- Support URL: support.html
- Terms URL: terms.html (often optional, recommended)
App Store Connect — App Privacy
Based on the current implementation, the App itself stores gameplay/settings locally and does not require login. However, because Yandex Mobile Ads is included, App Store privacy answers should account for third-party advertising SDK data. Review current Yandex SDK documentation before final submission.
Likely categories to review:
- Identifiers: advertising/device identifiers may be used by ads.
- Usage data: ad interactions may be used by ads.
- Diagnostics: SDK/network diagnostics may be processed by third-party services.
- Data linked/tracking: answer according to the final Yandex SDK behavior, ATT consent flow, and Apple’s tracking definition.
Google Play Console — Data safety
For the App’s own code: no account, no user-provided personal data, local-only high score/settings. For Yandex Mobile Ads: disclose ad/analytics-related collection according to the SDK’s current Data Safety guidance.
Likely items to review:
- Device or other IDs: advertising ID/device IDs for ads.
- App activity/ad interactions: ad delivery and measurement.
- Diagnostics: crash/diagnostic data if provided by SDK/platform.
- Purpose: advertising or marketing, analytics/measurement, fraud prevention/security.
RuStore
RuStore typically asks for a privacy policy URL when the app processes personal data or uses third-party SDKs. Use the Privacy Policy URL and ensure ad SDK disclosures are consistent with the submitted APK/AAB.
Current Yandex ad unit IDs
- Android banner:
R-M-19426972-1 - Android rewarded:
R-M-19426972-2 - Android interstitial:
R-M-19426972-3 - iOS banner:
R-M-19424796-1 - iOS rewarded:
R-M-19424796-2 - iOS interstitial:
R-M-19424796-3