Privacy Policy

Takeover Group (Takeover Tools / Takeover Games / Gamest / Takeo and related publishing names) 
Last Updated: [25.02.2026] 

This Privacy Policy (“Policy”) applies to websites, mobile games, applications, software, and developer tools created and/or published by Takeover Tools and/or Takeover Games, and also to titles that may be published under the names “Gamest”, “Takeo”, or other store/brand names used by our group (collectively, the “Services”). 

This Policy explains what data may be processed when you use, download, visit, or otherwise interact with our Services, for what purposes such data may be used, with whom it may be shared, how it is protected, and what choices and rights you may have.

Transparency Note: Our Services are generally designed not to collect direct identity data (such as full name, email address, phone number, or street address). However, certain identifiers used for advertising and measurement (e.g., IDFA/GAID) and SDK-based metrics may be considered personal data in some jurisdictions. For this reason, we use precise language and treat many telemetry items as pseudonymous rather than “fully anonymous”. 

1) Definitions
Personal Data: Any information relating to an identified or identifiable individual. In some jurisdictions, device and advertising identifiers may also be treated as personal data.
Pseudonymous Data: Data that does not directly identify you (no name/email), but may be linked to a device, session, or installation (e.g., advertising identifiers).
Anonymous Data: Data that has been irreversibly de-identified so it cannot reasonably be linked to an individual.
Processing: Any operation performed on data, such as collection, storage, use, analysis, transfer, or deletion.
   
2) Age Limit and Children’s Privacy 
Our Services are not intended for children under the age of 13. If you are under 13, you must not use our Services. If we become aware that we have processed personal data from a child under 13, we will take reasonable steps to delete such data and address the situation as required. 

3) What Data We May Process 
The data processed depends on which Service you use and which features are enabled. 

3.1 Device and Technical Data 
Platform (iOS/Android/PC, etc.)
Device model, operating system version
Hardware indicators such as RAM/GPU
Screen resolution
Connection type (Wi-Fi/mobile)
App version, language settings
Performance metrics (e.g., FPS, memory usage)
Error and crash logs
Purpose: Stability, debugging, performance improvements, and security. 

3.2 Session / Gameplay / Usage Data (Behavioral) 
Session identifiers (e.g., session_id), session start/end, session duration
In-game event stream (e.g., event name, optional level_id, success status)
Gameplay flow and balancing metrics
Feature usage metrics (which screens/menus/features are used and how)
Purpose: Product quality, UX improvements, balancing, and operational insights. 

3.3 Advertising and Measurement Data 
If a Service displays ads or performs ad measurement, we may process: 
- Ad impressions and clicks
- Placement and format (banner/interstitial/rewarded)
- Technical ad response information (SDK response metadata where applicable)
- Viewability / engagement metrics (e.g., viewability seconds)
Purpose: Ad delivery, measurement, reporting, frequency control, and fraud prevention. 

3.4 Advertising Identifier 
- (IDFA/GAID) and Similar Identifiers IDFA (iOS) / GAID (Android) and similar advertising identifiers
- Technical identifiers used for integrity and anti-fraud signals (where applicable)
Important: Even without a name/email, advertising identifiers may be treated as personal data in some jurisdictions. We use these identifiers primarily for advertising operations, measurement, and fraud prevention. 

3.5 Approximate Location 
Our default approach is not to collect precise GPS location. Where needed for reporting or operational purposes, we may process approximate location at the country level, often derived from network signals (e.g., IP-based country inference). Note: Our systems can be configured to limit or disable location processing depending on the product’s requirements and applicable rules. 

3.6 Age and Gender (Optional User-Provided Information) 
In some Services, we may ask users to optionally provide age range and gender. 
This information: 
- Is entirely optional
- Can be skipped via a “Prefer not to say” option
- Is based on user input and is not identity-verified
Purpose: General product insights and audience understanding (not mandatory for use). 

3.7 Anti-Fraud / Abuse Prevention Data 
To protect our Services and ad ecosystem, we may process: 
- Device integrity signals (e.g., emulator/root detection where available)
- VPN detection and network metadata (e.g., ASN signals where applicable)
- Technical signatures used to detect ad fraud or abuse
Purpose: Preventing abuse, cheating, invalid traffic, and fraud. 

4) Takeover Tools (Developer Tools) - Specific Terms 
Takeover Tools products (e.g., Translator Pro and related modules) may process certain developer-provided technical data for translation quality and contextual consistency, such as: 
- GameView screenshots (for contextual analysis)
- Scene / GameObject hierarchy information
- Technical analysis JSON outputs (e.g., component names as metadata)
- Localization tables and text content

4.1 Default Retention Behavior 
By default, such analysis data is processed only for the duration of the analysis and is designed not to be stored permanently. After the analysis completes, data is intended to be removed from our systems in line with our default non-retention approach. 

4.2 User-Enabled Retention 
If (and only if) the developer explicitly enables a feature such as “store outputs”, “retain for reprocessing”, or similar, certain outputs may be retained. Default behavior remains no persistent storage unless explicitly enabled. 

5) Why We Process Data
We process data for the following purposes: 
- Providing, operating, and maintaining the Services
- Debugging, stability, and performance improvements
- Improving user experience (UX), balancing, and product quality
- Advertising delivery, measurement, and revenue reporting
- Preventing fraud, invalid traffic, cheating, and abuse
- Maintaining security and system integrity
- For Takeover Tools: improving translation quality and contextual integrity

6) Third-Party SDKs, Advertising Providers, and Partners 
Our Services may integrate third-party SDKs and service providers, including: 
- Advertising providers and mediation platforms 
 -- Examples: Google AdMob, AppLovin MAX
 -- And additional ad networks connected via mediation
- Game engine and engine services 
 -- Example: Unity and Unity-related services/analytics if enabled
- Analytics, crash reporting, and performance monitoring services
- Cloud hosting, storage, and logging infrastructure providers

6.1 What Third Parties May Process 
Depending on their role, these third parties may process: 
- Advertising identifiers (IDFA/GAID)
- SDK identifiers and measurement signals
- Ad impression/click data
- Device/app technical data
- Approximate location (e.g., country-level)
Third parties’ processing may be governed by their own privacy policies and terms. We aim to integrate only what is necessary and follow a data-minimization approach where reasonably possible. 

7) Consent, Personalization, and Your Choices 
In jurisdictions where required (for example, certain regions in the EEA/UK), we may present a consent flow (e.g., via standard consent tooling supported by our advertising stack) for purposes such as ad personalization and related data processing. Users may: 
- Decline personalized advertising (where applicable)
- Reset or limit advertising identifiers through device settings
- Skip optional fields (such as age/gender) via “Prefer not to say”
Where personalization is declined, we aim to respect that choice by limiting personalization-related processing and configuring ad delivery accordingly, subject to the capabilities and requirements of our third-party providers. 

8) Do We Sell Personal Data? 
No. We do not sell personal data. 
However, we may share limited technical data with service providers and partners strictly to: 
- Deliver and measure ads
- Analyze crashes/performance
- Host infrastructure
- Prevent fraud and abuse

9) Data Retention 
Retention periods vary depending on the type of data and purpose: 
- Crash/performance logs: retained as needed for troubleshooting and security
- Analytics: retained as needed for product improvement and reporting
- Anti-fraud signals: retained as needed to prevent abuse and invalid traffic
- Takeover Tools analysis data: default is non-retention after processing, unless the developer explicitly enables retention features
We may also retain certain records longer where required by law or for legitimate business needs (e.g., financial compliance related to purchases), where applicable. 

10) Security 
We implement reasonable technical and organizational measures to protect data, such as: 
- Encrypted communications (HTTPS/TLS)
- Access controls and authorization practices
- Monitoring and logging for security purposes
- Data minimization
No method of transmission or storage is 100% secure; we continuously work to reduce risk through improvements and best practices. 

11) Your Rights and Requests 
Depending on your location and applicable laws, you may have rights such as: 
- Requesting access to your data
- Requesting deletion
- Objecting to or restricting certain processing
- Requesting correction (where applicable)
 -- Contact: connect@takeover.games 
(For Takeover Tools licensed products, including license/invoice details may help us locate and process requests more efficiently.) 

12) International Data Transfers 
Our infrastructure and service providers may be located in different countries. Where cross-border processing occurs, we apply reasonable safeguards and limit processing to what is necessary to operate the Services. 

13) Changes to This Policy 
We may update this Policy from time to time. Material changes may be communicated via our website and/or in-app notices.