4FGHTRKampfsport. Gemeinschaft. Haltung.
← Zur Startseite

Privacy Policy

Last updated: 2 November 2026. Deutsche Fassung.

Quick links: Website, PWAs, Fight Timer PWA, SkillMix PWA, Android, Web advertising, Your rights.

1. Data Controller

Daniel Schulz, Satemin 44, 29439 Lüchow, Germany. Privacy contact: info@4fghtr.de.

2. Scope

This notice covers 4fghtr.de, www.4fghtr.de, apps.4fghtr.de, our Fight Timer and SkillMix browser apps, and Fight Timer for Android (com.fghtr.fighttimer). The sections identify different processing by platform; naming an Android SDK does not mean it is installed in a PWA.

The homepage and app overview require no registration and do not load Google Analytics, AdSense or AdMob scripts. An ads.txt file does not itself load advertising or set advertising cookies. Basic app use does not require an account with us.

The separately operated merchandise shop has its own privacy notice. External community, Amazon, YouTube and app-store pages have their own processing when you visit them.

3. Hosting and server access logs

Our website and PWAs are delivered from our Windows/IIS server at STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany. STRATO provides hosting infrastructure; see its processing terms and privacy information.

Requests necessarily transmit connection information. IIS access logs can contain IP address, date/time, requested host/path and query parameters, browser user-agent, referring page, response code and technical request information. These data support delivery, troubleshooting and protection against misuse, not advertising profiles. The legal basis is Article 6(1)(f) GDPR: our legitimate interests in operating and securing the service. Without the necessary connection data, the requested content cannot be delivered.

Our own IIS access-log files have a 30-day cleanup threshold. A daily task removes files whose last write is over 30 days old, so removal can occur at the next daily run. Information required for a concrete security incident or legal obligation can be kept separately for that purpose while necessary. This rule concerns our IIS logs, not Google or shop-provider records.

4. PWAs: browser storage and offline operation

Training functions run in your browser. localStorage, IndexedDB and Cache Storage provide requested settings, saved content, history and offline operation. Storage is separated by browser profile and website origin. Service workers cache our app files and sounds; downloads, updates and online features still produce server requests. We do not automatically upload your saved training records to a developer account or synchronisation backend. The checked PWAs have no separate analytics or cloud-diagnostics SDK.

Fight Timer PWA

Fight Timer saves language, round/pause and training settings, sound/display preferences and custom templates locally. Its PWA does not use the native AdMob SDK, Google Play Billing, Android credit/entitlement storage or Firebase Crashlytics. A running session is not guaranteed to survive reload. Optional screen-wake functionality keeps the display active; it does not record sound or measure your movements.

SkillMix PWA

Exercise packages, entered names, selections and settings are kept in localStorage. IndexedDB holds training history with session/exercise identifiers and names, selected techniques, training day and active seconds. Statistics are calculated from those records, without sensor-based movement/repetition recognition. Import reads a file you select; exports are generated as local downloads. There are no developer accounts, automatic history uploads, synchronisation or automatic trainer updates in this implementation.

Managing local data

Use browser site-data controls to remove stored data. Removing a PWA or its shortcut alone may leave browser data behind. Storage limits, browser/OS cleanup and backup/restore can affect persistence. Exported files remain where you save them until removed. We cannot remotely read or erase records held only on your device.

Storage strictly necessary for explicitly requested local/offline functions is assessed under Section 25(2)(2) TDDDG. Processing of personal data necessary to provide the requested service is based on Article 6(1)(b) GDPR. Optional advertising storage is separate.

5. Android local data and Google Play Billing

Fight Timer for Android stores settings and templates locally in WebView storage. Credits, credit-window expiry, cached ad-free entitlement and last store-check time use platform secure storage. The crash-report sending preference is stored locally.

Google Play Billing handles permanent ad-removal purchases and restoration. The app processes purchase/entitlement status and uses the purchase token to acknowledge eligible purchases with Google. We receive no payment-card details through this integration and operate no separate purchase-validation backend. Our entitlement processing uses Article 6(1)(b) GDPR; Google processes the transaction under its own service terms.

Uninstalling does not delete Google purchase records or reports already sent. OS backups may restore local data. Ad-free access does not undo previous processing or automatically change a separate diagnostics choice.

6. PWA advertising and consent management

The checked Fight Timer and SkillMix PWA source configurations currently have web banners disabled, with no active publisher/slot/CMP configuration. An equipment link or ads.txt is not a live AdSense banner or proof of Google approval.

The prepared module can be enabled in a later configured release. It uses a Google consent-management message and a manual AdSense banner, separately from native AdMob. Once enabled, the consent provider receives technical request information to display and store choices. An eligible current decision is checked before the advertising script is requested.

For optional advertising, Google and partners named in the actual consent message can process IP/device/browser information, cookies or other identifiers and ad interactions for delivery, measurement, security and, where selected, personalisation. Consent-based processing uses Article 6(1)(a) GDPR; optional device storage/access uses Section 25(1) TDDDG. Advertising storage is not classified as necessary merely because you decline consent.

Use the app's advertising privacy-options entry to review or withdraw choices. Withdrawal affects future consent-based processing, not earlier lawful processing. Clearing browser data does not erase all provider records. Partners, storage periods and choices are identified by the actual enabled consent setup and the linked provider information. A newly enabled advertising/CMP configuration must be reflected in this notice before processing starts.

7. Android AdMob and UMP

Fight Timer for Android integrates Google AdMob for app-open/rewarded ads and UMP for advertising choices. Processing can include device/network information, ad/installation identifiers, approximate location derived from IP, ad interactions and diagnostic/security information. The app does not collect precise GPS location for this purpose.

Where required, UMP obtains advertising choices, which can be changed through the app's privacy options. Optional consent-based advertising uses Article 6(1)(a) GDPR and applicable device-access rules. Opening this notice or purchasing an app is not advertising consent. Google's own information explains its further processing.

8. Optional Android crash-report sending

Fight Timer's Android integration contains Firebase Crashlytics. Sending is initially off. The app offers a setting and can ask about sending a pending report after a crash. Declining leaves sending off and discards pending reports in that flow. Already released reports cannot be recalled by changing the setting.

Sending relies on your voluntary choice under Article 6(1)(a) GDPR. The sending switch does not promise that the included SDK cannot initialise or record diagnostic information locally beforehand. This integration adds neither Google Analytics nor a developer-defined user ID.

Reports can include crash traces, device/OS/app information and installation/session identifiers. Our added context concerns technical training state and a bounded history of predefined actions; it does not add custom template names, purchase tokens, payment receipts or advertising-consent identifiers. Native SDK error information may add technical details.

Google states that relevant Crashlytics traces and identifiers are kept for 90 days before removal from live/backup systems begins, not that deletion is completed on day 90. See Firebase privacy information. The PWAs above do not contain this Android integration.

9. YouTube and external/affiliate links

An embedded YouTube player is loaded only after you select the labelled video button. It then connects to Google's privacy-enhanced player, transmitting request/device information and enabling processing of viewing activity or association with an existing account. Privacy-enhanced mode does not mean no transmission. Loading the optional player relies on consent under Article 6(1)(a) GDPR and, where relevant, Section 25(1) TDDDG. Reloading closes this page's player, not provider records already created.

Marked Amazon affiliate links open Amazon when clicked. Amazon can attribute qualifying purchases through the affiliate reference and its own technologies. We receive no payment details through that link. The link alone does not load an Amazon ad script on this homepage. See Amazon privacy information.

Links to Shopify, Skool, external YouTube pages and stores cause a connection when clicked. The destination receives usual request information and potentially referral information according to browser settings. Its own privacy notice applies there. Our locally hosted text and images do not require opening those services.

Email inquiries involve your address, message and supplied information. Article 6(1)(b) GDPR applies to contract-related inquiries; otherwise Article 6(1)(f) applies to responding to requests. Correspondence is kept while needed for the matter, applicable retention duties or specific legal claims.

Necessary browser functions, local training data, consent preferences and optional advertising identifiers serve different purposes. They are not covered by one blanket consent. The homepage does not set an advertising-consent cookie merely because it links to an app.

11. Recipients and international transfers

Recipients depend on the selected service: STRATO for hosting; relevant Google entities and partners listed in an enabled consent message for advertising/consent functions; Google for store transactions and Android diagnostics; and external services you choose to open. Google's notice identifies Google Ireland Limited for EEA consumer services; individual product contracts can identify another Google entity. We do not sell your training records.

Google processing can take place outside the EEA, including the US. Depending on the recipient/service, safeguards include an applicable adequacy decision, an eligible EU-US Data Privacy Framework transfer or standard contractual clauses. Advertising consent does not replace a required safeguard. See Google's transfer information. You can contact us about safeguards relevant to our processing.

12. Retention summary

13. Your rights

Subject to applicable conditions, you can request access, correction, deletion, restriction and portability, and withdraw consent for the future. For legitimate-interest processing, you can object for reasons relating to your situation; direct marketing can be opposed at any time. Contact info@4fghtr.de. Proportionate information may be needed to identify the records and verify a request.

You can complain to a supervisory authority, including where you live/work. The Lower Saxony authority offers a complaint channel for our location; contacting us first is not required. Browser-only records can be managed on your device because we have no server copy. We make no solely automated decisions with legal or similarly significant effects using your training data.

14. Provider information

STRATO, Google privacy, Google partner services, Firebase and the merchandise shop provide service-specific information.

15. Changes to this Privacy Policy

We update this notice when actual processing changes. New apps/features, enabled advertising/CMP setups, accounts or diagnostic changes require review before being offered. The date above identifies this version. The existing app-policy URL remains available for installed apps.