Privacy Policy
This notice explains the actual data flows of the Trenchfront iOS app and this website.
1. Controller
Philip Grabner
Widerinstraße 18B/26
3100 St. Pölten
Austria
Email: grabner.labs@gmail.com
Natural person, not registered in the Austrian Commercial Register. Privacy requests may be sent to the stated email address. Do not send passwords, complete payment details, or Apple Account credentials.
2. Scope
This notice applies to the Trenchfront iOS app, this support and privacy website, and voluntary contact by email. It describes services actually used in version 1.0.
3. Processing overview
| Activity | Data, purpose, and source | Recipient, retention, and choice |
|---|---|---|
| Local game | Progress, settings, statistics, high scores, challenges, unlocks, and local purchase status generated by use. | Primarily on the device. Delete by removing the app; Trenchfront normally has no direct access. |
| Apple services | Purchase status and voluntary Game Center values used for purchases, leaderboards, and achievements. | Apple under its terms; managed through the Apple Account. |
| Advertising | Depending on choices, device, usage, advertising, diagnostic, and security data for ad delivery and fraud prevention. | Google and participating ad partners under their policies; Premium stops new ad requests. |
| Optional analytics and diagnostics | After separate activation, aggregated gameplay events and crash and diagnostic data. | Google Firebase; both features are off by default and can be withdrawn independently. |
| Support | Email address, name, message, and voluntary technical details used to handle a request. | Philip Grabner and Gmail/Google; only as needed for handling, documentation, or claims. |
| Website | IP address, time, requested resource, browser/device data, and referrer where transmitted. | Netlify; technical delivery, security, and diagnostics under its rules. |
4. Local game data
Game save, audio and gameplay settings, statistics, high scores, challenges, unlocks, currencies, progress, and local purchase status are stored through iOS system storage on the device. The developer normally has no direct access to this purely local data.
Version 1.0 has no in-app delete-data control and no enabled cloud-save service. Local data can be removed by deleting the app. Without cloud storage, reinstalling does not automatically restore local progress; restorable purchases are separate.
5. StoreKit and in-app purchases
Purchases are processed through Apple StoreKit. Trenchfront does not process card or bank data. The app checks product, transaction, and entitlement status to unlock content and restore eligible purchases. Consumable content cannot be provided again through Restore Purchases.
Apple may process data for payment, tax, fraud prevention, and legal duties. Trenchfront does not determine Apple's retention. See Apple Privacy and Report a purchase problem or request a refund.
6. Game Center
Game Center is optional and the game remains usable without signing in. When enabled, Apple processes a player identifier and display name as well as submitted leaderboard scores, achievements, and progress values. The display name appears in the Trenchfront interface. Trenchfront does not send Game Center names or identifiers to AdMob.
Game Center cloud saves are disabled in version 1.0. Game Center data is managed through the Apple Account and Apple's features.
7. Google AdMob
Free use supports interstitial ads at natural breaks and voluntary rewarded ads for the displayed in-game reward. There are no banner ads and no ads during an active battle.
Depending on consent, region, and SDK configuration, Google and participating ad partners may process IP address, approximate region derived from it, device identifiers, the advertising identifier where available and permitted, ads displayed, advertising and product interactions, diagnostics, crash and performance data, and security and fraud-prevention information. Purposes include ad delivery, measurement, security, fraud prevention, and technical optimization. The current partner list may be available in a displayed UMP message.
8. Optional Firebase analytics and error diagnostics
Anonymous usage analytics and technical error reports can be enabled separately in the game settings. Both features are disabled by default. Analytics then processes aggregated information such as game mode, map, difficulty, battle duration, result, score, deployed units, abilities, and technical purchase, advertising, and Game Center categories. When enabled, Crashlytics processes crash and diagnostic data to resolve technical issues.
Trenchfront does not send names, email addresses, telephone numbers, postal addresses, free-form text, payment details, Game Center player identifiers, or proprietary persistent user identifiers to Firebase. The Analytics Core variant does not include IDFA collection capability; Analytics IDFV collection and analytics ad personalization are also disabled. Either consent can be withdrawn at any time in Settings. See the Google Privacy Policy.
10. UMP and privacy options
On every normal app launch, before the first ad request, the app updates UMP consent information, loads required messages, and checks canRequestAds. No ad is requested while UMP does not permit it. Errors do not interrupt gameplay.
The “Manage ad privacy choices” entry appears in Settings only when UMP reports it as required for the region and status. Available choices can then be reopened. Refusing personalized advertising does not block purchased content; advertising may be limited or non-personalized.
11. App Tracking Transparency
When ads are enabled, UMP allows an ad request, and Apple's status is undetermined, the app presents Apple's separate ATT system prompt. It concerns access to the advertising identifier for ad measurement or more relevant advertising. Refusal does not restrict gameplay or purchased content and is not bypassed, but it does not prevent all technically necessary processing.
12. United States privacy rights
To the extent applicable law provides, US users may request access, correction, deletion, portability, non-discrimination, and an opt-out of sale, sharing, or targeted advertising. An authorized agent and appeal of a denial may be available where applicable.
Trenchfront does not sell personal data for money. Advertising flows may nevertheless be treated as a sale, sharing, or targeted advertising under individual laws. Until the US UMP message is confirmed as published and tested, related requests may be sent to grabner.labs@gmail.com; this website does not claim an already active technical UMP opt-out.
13. Support communications
An email may process address, sender name, subject, content, time, and voluntarily supplied app version, iPhone model, iOS version, language, game mode, issue description, screenshots, or attachments. Purposes are replying, diagnostics, purchase assistance, security, and stability improvement.
Legal bases are Article 6(1)(b) GDPR for use- or purchase-related requests, otherwise Article 6(1)(f) for support, security, and troubleshooting, and where applicable Article 6(1)(c) for legal duties. Email is handled through Gmail/Google and retained only as needed for handling, documentation, abuse prevention, legal duties, or claims.
14. Website and Netlify
The static website is delivered by Netlify. For delivery, security, diagnostics, and attack detection, Netlify may process IP address, date and time, requested resource, browser/device information, and a technically transmitted referrer in server and security logs. Processing outside the EEA may occur under lawful mechanisms such as adequacy decisions or standard contractual clauses.
The website uses no first-party analytics, ad trackers, marketing cookies, social pixels, forms, or user accounts. See the Netlify Privacy Statement.
15. Recipients and international transfers
Depending on the activity, recipients may include Apple, Google and ad partners, Gmail/Google, Netlify, and legally authorized public authorities. Providers may act in different privacy roles depending on the processing. Transfers outside the EU/EEA may rely on adequacy decisions, the EU-US Data Privacy Framework where applicable, standard contractual clauses, or other lawful safeguards.
16. Legal bases
Local game delivery, purchases, and purchase-related support generally rely on Article 6(1)(b) GDPR. Consent-required personalized advertising and tracking rely on Article 6(1)(a). Security, fraud prevention, general support, and technical website logs rely on Article 6(1)(f). Legally required processing relies on Article 6(1)(c). The applicable basis depends on the activity and law.
17. Retention and deletion
Local game data remains until the app is deleted. Apple, Game Center, purchase, and Google advertising data follow the providers' rules and legal duties. Consent choices are managed by UMP on the device and through supported standards. Support emails and Netlify logs are retained only under the described purposes and provider rules.
Deleting the app does not automatically delete data processed by Apple, Google, or Netlify under their own legal bases. Purchases can be restored in the app, Game Center data managed through Apple, and privacy requests sent by email.
18. GDPR rights
Where requirements are met, individuals have rights of access, correction, deletion, restriction, portability, objection, and withdrawal of consent for future processing. A complaint may be lodged with the Austrian Data Protection Authority or another competent authority.
The developer may have no access to device-only data; it must be removed by deleting the app.
19. Children and young people
Trenchfront is not directed to children under 13 and is not intended for Apple's Kids Category. The developer does not knowingly ask children under 13 to submit personal data directly. Parents or guardians may contact support with concerns. Advertising and age settings must be checked separately against the App Store age rating before release.
20. Automated decisions
Trenchfront itself makes no solely automated decisions with legal or similarly significant effects. Depending on consent and law, advertising providers may use data for ad selection and measurement.
21. Changes
This notice is updated for material new features, SDKs, providers, or legal requirements. A new version receives a new manually maintained effective date. Individual email notice is not provided because Trenchfront has no account or mailing list.