Slingshot Master Privacy Policy

Effective Date: 2026-04-15 · Version: 2026-04-15

Design Future Games (the “Developer”) values users’ information in providing the mobile game Slingshot Master (the “Service”) and publishes this Privacy Policy in accordance with applicable laws and Google Play policies.

For information about the terms of use of the Service, please review the Terms of Service.

1. Developer Information and Contact

Developer: Design Future Games

Email: designfuturegames.cs@gmail.com

2. Information Collected and Processed

The Developer does not operate a separate in-house sign-up system or internal member database, and does not provide the Service on the basis of continuously storing users’ personal information on the Developer’s own servers. However, the following information may be processed during use of the Service.

  • Locally stored device data: game progress, settings, temporary data, and data stored on the device
  • When Google Play Games sign-in is used: player identifier information, sign-in status, achievements, leaderboard records, and information related to gameplay history
  • When Google Play Billing is used: purchase status, transaction-related information necessary to verify purchases, and restoration-related information
  • When Google AdMob is used: device identifiers, advertising identifiers, IP address, user interaction information, diagnostic information, and similar data for ad delivery, ad measurement, and fraud prevention
  • When Firebase Analytics is used: app usage status, event records, usage patterns, device and app environment information, and analytics-related identifiers
  • When Firebase Crashlytics is used: app crash information, error logs, device state at the time of a crash, OS information, app version, and diagnostic information necessary for stability analysis

A substantial portion of the information above may be processed automatically through external services and SDKs, including Google Play Games, Google Play Billing, Google AdMob, Firebase Analytics, and Firebase Crashlytics, rather than being directly entered by the user to the Developer.

3. Purposes of Processing

The Developer may process information within the following scope for the operation and provision of the Service.

  • Providing basic functions such as running the game, saving settings, and maintaining progress
  • Providing Google Play Games sign-in, achievements, and leaderboard features
  • Processing in-app purchases through Google Play Billing and verifying purchase restoration
  • Providing advertisements, measuring ad performance, and preventing ad-related abuse
  • Analyzing usage patterns, improving content, improving features, and optimizing service operation
  • Analyzing and responding to app crashes, errors, abnormal termination, and performance degradation
  • Detecting and preventing fraudulent use, abuse, and abnormal activity

4. Retention and Use Period

The Developer does not operate an internal server-based member database, so, in principle, the Developer does not directly retain personal information on a long-term basis.

  • Locally stored device data: may be removed when the app is deleted, app data is reset, the device is changed, or the user deletes it directly.
  • Information related to Google Play Games, Google Play Billing, Google AdMob, and Firebase services: may be retained for different periods depending on the policies, technical structure, account status, and applicable laws of each service provider.
  • Inquiry emails: may be retained for a reasonable period as necessary to respond to user inquiries and handle disputes.

5. Use of Third-Party Services and Information Processing

The Service may use the following external services, and those services may process related information according to their own policies and technical requirements.

  • Google Play Games
  • Google Play Billing
  • Google AdMob
  • Firebase Analytics
  • Firebase Crashlytics

The Developer does not sell users’ information and does not aim to independently provide users’ personal information to third parties at the Developer’s discretion. However, information may be processed through the external services and SDKs included for the provision of the Service.

6. Separate Permission Requests and Local Storage

As a general rule, the Service does not require separate sensitive permission requests. However, notices or consent procedures necessary for the operating system, store, advertisements, sign-in, payments, or applicable laws may be displayed.

Game progress, settings, and certain temporary data may be stored locally on the user’s device, and may be deleted together when the app is removed or app data is reset.

7. User Rights and How to Exercise Them

Users may take the following actions regarding their information.

  • Remove locally stored device data by deleting the app or clearing app data
  • Manage related game data through Google Play Games or Google account settings
  • Manage ad personalization or advertising identifier settings through Android or Google settings
  • Contact the Developer by email for inquiries or requests

However, information processed through Google Play Games, Google Play Billing, Google AdMob, Firebase Analytics, and Firebase Crashlytics may be managed in accordance with each provider’s systems and policies. Accordingly, certain requests relating to such information may need to follow the relevant provider’s own procedures.

8. Information Regarding Children and Minors

Minors must use the Service under the consent or supervision of a legal guardian. Matters relating to external platforms, including Google accounts, Google Play Games, payment settings, and advertisement settings, must be managed under the responsibility of the user and guardian.

9. Security Measures

The Developer considers reasonable administrative and technical measures for service stability and information protection. In addition, external services such as Google Play Games, Google Play Billing, Google AdMob, Firebase Analytics, and Firebase Crashlytics may process related information according to their own security policies and technical protection measures.

10. Changes to This Policy

This Privacy Policy may be revised in accordance with changes in applicable law, service features, SDKs used, platform policies, or operational methods.

If there is a material change, notice may be provided through a webpage update, in-app notice, or another reasonable method.

11. Effective Date

This Privacy Policy takes effect on April 15, 2026.