Privacy & Policy - PolityForge

PolityForge Privacy Policy

Last updated: 22 July 2026

Effective date: 22 July 2026

Service: PolityForge (the "Game")

Publisher/data controller: Brixx Games Studio ("we", "us", "our")

Contact: meharmuzammal0019@gmail.com

Postal address: Chak No 519 GB Ramsar, Tehsil & District Toba Tek Singh

This policy explains how we handle information in the PolityForge mobile game, related websites, support channels, and services (together, the "Services"). It is written for Google Play and general privacy transparency. It is not a substitute for advice from a lawyer qualified in the countries where you publish.

1. The short version

The current game is primarily an offline, local-save simulation. The current build does not require an account and, based on our present implementation, does not intentionally collect or transmit your name, email address, contacts, precise or approximate location, camera, microphone, photos, payment details, or gameplay telemetry to us. Campaign data is saved on your device. The game uses Unity and platform services needed to run the app; those services may process limited technical information under their own terms.

We plan to add Google Mobile Ads/AdMob and Firebase Analytics in a later release. Those integrations are not covered as current collection unless and until the relevant SDKs are included and enabled. Before enabling them, we will update this policy, the in-app privacy notice, consent flows, and Google Play Data safety form to match the exact SDK versions and configuration.

2. Information we may handle

A. Information stored locally by the current game

The game can save a campaign and settings on your device. A save may contain the simulated country, date, government, elections, parties, laws, budgets, debt, trade, industry, social indicators, events, decisions, and other game-state values you create or that the simulation generates. It is gameplay state, not a player profile. The current implementation stores the save under the platform's application data directory and uses an Android Keystore-backed protected save path where available. A small local preference records whether a save exists.

This information normally stays on your device. It can be removed with the in-game "clear/delete save" action, by uninstalling the game, or through the operating system's app-data controls. Device backup or migration features controlled by the platform may copy app data; we do not control that process.

B. Information you send to us

If you contact support, we receive the information you choose to include, such as your email address, device/build details, screenshots, purchase or platform transaction references, and the contents of your request. Please do not send passwords, payment-card numbers, government ID numbers, health information, or other sensitive information unless we specifically request it through a secure channel.

C. Information automatically processed by platforms and future SDKs

The operating system, Google Play, Unity, hosting providers, crash-reporting tools (if later enabled), Firebase, and advertising providers may process technical information such as IP address, country/region inferred from IP, device model, operating-system version, app version, language, time zone, network information, diagnostics, and a resettable advertising or app-instance identifier. Whether a particular item is collected depends on the SDK, device, permissions, and settings in the released build. We will disclose each enabled SDK and purpose in the in-app notice and Play Data safety form.

3. Planned Firebase Analytics disclosure

When Firebase Analytics is enabled, we expect to configure it to measure aggregate product performance and gameplay engagement, for example app launches, sessions, screen/view events, tutorial or feature completion, country/simulation mode selected, month advanced, errors, and broad device/app information. We will not intentionally send the contents of free-form support messages, passwords, payment-card data, government IDs, precise location, contacts, microphone recordings, camera images, or other sensitive data to Analytics. We will not use the simulation's fictional political choices to make decisions about your real-world eligibility, credit, employment, housing, insurance, or government services.

Firebase may assign an app-instance identifier and process technical data on Google systems. We will use Google's documented retention and deletion controls, restrict access to authorized personnel, and configure consent/analytics storage controls where required. Firebase Analytics can be disabled in the game's privacy settings where technically available; device-level controls may also apply. Google's processing is governed by Google's privacy documentation and Firebase terms.

4. Planned advertising/AdMob disclosure

When ads are enabled, Google Mobile Ads/AdMob and its mediation or measurement partners may process ad-request data, including IP address or coarse region, device/app information, ad interaction, frequency/capping information, and (where available and permitted) the Android Advertising ID or another resettable advertising identifier. This can be used to deliver, limit, measure, and protect ads, prevent fraud, and produce aggregate reports. We will not sell your name, email, support messages, or local save file to advertisers.

Personalized ads will be used only where permitted and after any consent required by applicable law. In the European Economic Area, United Kingdom, and Switzerland, we will use a Google-certified consent-management flow integrated with the IAB Transparency and Consent Framework where required, offer a non-personalized/limited-ads option where available, and provide a persistent "Privacy and cookie settings" control for withdrawing or changing choices. We will honor applicable US state opt-out signals and provide the choices shown in the released app. You can also reset/delete Android's Advertising ID or disable ad personalization in Android settings. Ads will not be targeted using the contents of your campaign save.

We will not knowingly serve personalized ads to children or transmit prohibited identifiers from children. If the Game is ever directed to children or a mixed audience, we will use only SDKs and ad settings permitted by Google Play Families requirements and will revise the age/consent experience before release.

5. Why we use information

We use information only as necessary to:

• operate, provide, maintain, secure, troubleshoot, and update the Game;
• save and restore local campaigns;
• answer support requests and handle rights requests;
• understand aggregate stability, feature use, and performance after analytics is enabled;
• show, limit, measure, and protect advertising after ads are enabled;
• detect abuse, fraud, security incidents, or violations of our terms;
• comply with law, lawful requests, platform rules, and accounting obligations; and
• establish, exercise, or defend legal claims.

We do not use gameplay data to infer sensitive personal characteristics, make real-world political profiles, or provide real-world political advice. We do not use the Game to make automated decisions with legal or similarly significant effects about a person.

6. Legal bases and choices

Depending on your location, our legal bases may include performance of the contract to provide the Game, our legitimate interests in security and product improvement, compliance with law, and your consent for personalized advertising or optional analytics where consent is required. You may withdraw consent at any time through the in-game privacy controls or by contacting us; withdrawal does not affect processing that occurred before withdrawal.

Local gameplay is generally necessary to provide the offline Game. You may choose not to provide support information, but we may then be unable to answer your request. You may decline personalized ads; the Game may show contextual or non-personalized ads, or an ad-supported feature may be unavailable where no lawful ad option exists.

7. Sharing and recipients

We may share the minimum information needed with:

• Google Play and platform providers for distribution, licensing, purchase verification, device services, and platform security;
• Unity and infrastructure providers that host, deliver, secure, or support the Game;
• Google Firebase for Analytics and related diagnostics if enabled;
• Google AdMob and authorized ad/mediation partners if advertising is enabled;
• support, hosting, security, legal, and professional service providers acting under confidentiality and instructions; and
• authorities, courts, or transaction parties where legally required or reasonably necessary to protect rights and safety.

We do not rent or sell personal information. We do not share local save files with advertisers. We do not share personal information with third parties for their own direct marketing unless we separately disclose it and obtain any consent required by law.

8. International transfers

Recipients may process information in countries other than where you live, including countries whose privacy laws may differ. Where required, we use an appropriate transfer mechanism (such as an adequacy decision, standard contractual clauses, or another lawful safeguard) and apply contractual and technical protections. Google's own processing is also subject to Google's privacy terms.

9. Retention

Local saves remain until you delete them, uninstall the Game, or the operating system removes them. Support correspondence is retained only as long as needed to respond, maintain security records, resolve disputes, and meet legal/accounting duties. If Firebase or AdMob is enabled, retention will be configured to the shortest practical period and disclosed in the in-app notice; aggregate or de-identified reports may be retained longer. Backups may persist for a limited disaster-recovery period before secure deletion.

10. Security

We use reasonable administrative, technical, and organizational safeguards appropriate to the information and risk, including access controls, encryption in transit where data is transmitted, protected local saves where supported, least-privilege access, and supplier review. No device, network, or storage system is completely secure. If a breach legally requiring notice occurs, we will notify affected people and authorities as required.

11. Your rights

Subject to local law and exceptions, you may request access to, correction of, deletion of, restriction of, or portability of personal information, object to certain processing, withdraw consent, or complain to your data-protection authority. Because the current game does not create an online player account, there may be no server profile to retrieve or delete; local saves can be deleted in the Game or device settings. If a future version permits account creation, it will provide an in-app account-deletion path and an external request method, and deletion will cover associated account data subject to legal exceptions.

Send requests to meharmuzammal0019@gmail.com with "PolityForge privacy request" in the subject. We may verify identity using reasonable, proportionate information and will not request unnecessary sensitive data. We generally respond within the period required by applicable law. You may use an authorized agent where local law permits. We do not discriminate against you for exercising privacy rights.

12. Children

The Game is not directed to children under 13 unless we expressly publish it as child-directed. We do not knowingly collect personal information from children. If you believe a child provided personal information, contact us and we will investigate and delete it where required. If the audience, age rating, ads, or analytics configuration changes, we will complete the required Google Play Families and consent review before release.

13. Third-party links and services

The Game or our website may link to Google Play, support pages, or other services. Their privacy practices are controlled by their own policies. Review them before using those services. A link is not an endorsement or representation that we control the linked service.

14. Changes

We may update this policy when the Game, SDKs, law, or our practices change. We will change the "Last updated" date, provide prominent in-app notice for material changes where required, and obtain fresh consent where legally necessary. Continued use after the effective date means the updated policy applies to future processing.

15. Contact and complaints

Privacy questions, requests, and complaints: meharmuzammal0019@gmail.com.

Data controller: Brixx Games Studio.

If you are in the EEA/UK, you may also contact your local supervisory authority. If you are in another jurisdiction, you may contact the authority identified by your local privacy law.

Google Play implementation checklist (not part of the user-facing policy)

Before publishing or enabling an SDK:

• Host this policy at a stable, public, non-geofenced HTTPS URL and link it inside the Game and Play Console.
• Complete Play Console Data safety for the exact release, including every third-party SDK; update it whenever collection changes.
• Audit the final Android manifest and SDK versions for permissions, Advertising ID, crash logs, and diagnostics.
• If enabling AdMob, integrate UMP/Google-certified CMP flows for EEA/UK/Switzerland, US state choices as applicable, and a persistent privacy-settings control.
• Configure Firebase consent mode/analytics storage, retention, deletion, and no-sensitive-data rules before production events are sent.
• Add an in-app privacy page and a clear local-save deletion control. If accounts are added, implement in-app and web account deletion before launch.
• Reconcile the policy, in-app notice, Play Data safety, content rating, Families answers, and actual network traffic; the release configuration controls what must be disclosed.