Privacy Policy Shotclock 24 Pro

Note on languages. This is the English version of the privacy policy. A German version (Datenschutzerklärung) is available as well. Both versions are meant to say the same. If you notice a difference, please write to hallo@mk-mc.eu.

This policy covers the iOS app Shotclock 24 Pro (iPhone and iPad) from version 1.0 on. It does not cover the website www.ki-agent.pro. That website has its own privacy policy (in German).

1. Controller

The controller within the meaning of the GDPR and the publisher of the app (called “the publisher” below) is:

MKMC | marketing & consulting
Owner: Matthias Grevelding Kiesche
Zu den Birken 14a, 51515 Kürten
Germany
E-mail: hallo@mk-mc.eu

The app has no server of the publisher, no accounts, no login and no cloud sync, and it contains no analytics or crash-reporting software of its own. The app does not send personal data to the publisher, so the publisher does not receive personal data from the app. What leaves your device while you use the app is traffic of third-party software and services: Google’s ad and consent software, and Apple for purchases and system dialogs. These are described below. Aggregated statistics and crash reports that Apple makes available to developers are described in section 11.

When you write to the publisher

If you write to the publisher, for example through the support page, the publisher processes your e-mail address and the content of your message to answer your request. The legal basis is Art. 6(1)(b) GDPR where your request concerns a purchase or a comparable contractual relationship, and otherwise Art. 6(1)(f) GDPR. The legitimate interest is to answer requests about the app. The data is deleted once the request is dealt with, unless statutory retention periods apply.

The publisher’s legal notice is available at the page Impressum (in German).

2. Overview

• No accounts, no own server. The app has no login, no cloud sync and no server of the publisher. It contains no analytics or crash-reporting software of its own and no network code of its own. The Google software described in section 4 may collect diagnostic and performance data for its own purposes.
• Settings stay on your device. Durations, buzzer sound and switches are saved locally (section 3).
• Advertising. The free version shows one banner ad, delivered by Google. Where required in your region, Google’s consent form is shown first, and iOS asks once for the tracking permission (section 4 to section 6).
• Optional purchase. A one-time in-app purchase, “Remove Ads”, is handled by Apple. After it, the app shows no banner. From the next launch on it shows no consent form or tracking prompt and makes no calls to Google’s ad software (section 7).
• Permissions. The tracking permission is the only permission the app asks for. The app does not request access to your microphone, camera, location, photos, contacts, calendar, notifications, motion data or health data. The buzzer is played as normal audio output only. If you use a Bluetooth speaker, you pair it in iOS Settings. The app does not scan for or pair Bluetooth devices itself.

3. Data stored on your device

The app saves its settings in the local storage for app preferences on your device (UserDefaults). The app does not send this data to the publisher or to third parties, and it has no function to transmit it. Deleting the app removes it. If you back up your device (for example to iCloud or to a computer), iOS may include the app’s data in the backup. You control this in iOS settings.

The app saves:

• the main duration and the secondary duration of the shot clock (defaults 24 and 14 seconds, any value from 1.0 to 99.0 seconds);
• whether the buzzer sounds at zero, and which of the five built-in buzzer sounds is selected;
• whether haptics (vibration feedback) are switched on, on devices that offer it;
• whether the clock has been started once on this installation, so that the hint shown on the first launch appears only until then;
• whether ads have been removed. This is only a local copy of the purchase status, because the purchase itself is checked with Apple (section 7).

Google’s software also keeps its own data on your device, in particular your consent choice (section 4). The app itself neither reads nor writes these entries.

Because this data is only on your device and the publisher has no access to it, the publisher does not process it itself. Where the storage of your settings (durations, buzzer, sounds, haptics) and of the “ads removed” marker nevertheless counts as processing by the publisher, it is based on Art. 6(1)(b) GDPR (providing the app functions you use) and on Section 25(2) No. 2 TDDDG, because it is strictly necessary for the service you expressly requested.

What the app does not store

The mute state is kept for the current session only, and the app always starts unmuted. The state of the clock and the remaining time exist only in memory while the app runs. The app does not store an account, name, e-mail address, location, contacts, photos, or microphone or camera data. The app itself does not read or store an advertising identifier. It uses no iCloud storage, no CloudKit and no Keychain, and it writes no files of its own. Google’s software may store further data on your device (section 4).

Technical log on the device

The app writes technical events to Apple’s system log on the device (for example the phases of the consent process, banner events by name with an error code if one occurs, and the type of audio output used for the buzzer). The app’s logging rules exclude secrets and personal data, and the app logs no device names. The app does not read the log back and does not send it anywhere.

4. Advertising (Google AdMob)

The free version of the app shows one banner ad at the bottom of the main screen. Ads are delivered by Google (Google LLC or Google Ireland Limited, depending on Google’s terms for your region) through its AdMob service and the Google Mobile Ads SDK. Your consent choice is handled by Google’s User Messaging Platform (UMP) SDK.

The banner ad

• The banner has a fixed size (320 × 50 points, 728 × 90 points in large windows).
• For each banner the app makes one plain ad request. The app adds no keywords, no content address, no location and no other extras. The Google SDK may refresh the ad and retry on its own.
• The banner is hidden, and not refreshed, while the menu or Options is open and while the app is not active.
• Tapping a banner usually opens the advertiser’s page or the App Store outside the app. Depending on the ad, an overlay of the SDK or of the App Store may appear instead. What the advertiser or the App Store processes after the tap is outside the control of the app. The privacy policy of that provider applies.

When ads are requested

At each launch, the app goes through these steps in this order. No ad is requested before step 5:

1. The app checks whether ads have been removed by purchase. If so, the remaining steps are skipped and the Google software is not called at all.
2. The app waits until it is active, meaning in the foreground.
3. Google’s consent software checks whether a consent form is required for your region and, if so, shows it. This check is itself a connection of your device to Google’s servers, also in regions where no form is shown. Ads are requested only if the result allows it.
4. If Google’s consent software allows ad requests and you have not yet decided on the iOS tracking permission, iOS asks once (section 5). This also applies after a refusal in Google’s form. Your answer to the prompt does not decide whether ads are shown.
5. The Google Mobile Ads SDK is started and the banner is loaded.

If ads are removed, the banner is taken down. If you withdraw consent later, the banner is taken down only if Google’s consent software then no longer allows ad requests. If ads are not allowed, the check may be repeated when you return to the app.

Consent form (Google UMP)

Google’s consent software decides, based on your region, whether a consent form is required. The consent message is configured in AdMob for the European Economic Area, the United Kingdom and Switzerland. In these regions the form is shown over the main screen. It lets you consent, manage your options or refuse with one tap. In regions where no form is required, it is not shown and the app requests ads without a form.

If you refuse, the app does not decide by itself whether ads are shown. It asks Google’s consent software. As the consent message is set up, ads can still be requested after a refusal (Google then serves limited ads), so the banner and the iOS tracking prompt can still appear. Only if Google’s consent software does not allow ad requests does the app request no ads and show no banner. The clock works unchanged. You can change your choice at any time (section 6).

Google’s consent software stores your choice on your device, in the format of the IAB Transparency and Consent Framework, and Google’s ad code reads it. Google declares in the privacy manifest of the consent SDK that it may use coarse location, performance data and product interaction data, not linked to you and not used for tracking, for the functioning of the app. The app has no influence on how Google determines your region.

Personalized and less personalized ads

Whether and how far ads are personalized depends on your consent choice and on the tracking permission. The advertising identifier of your device (IDFA) is available to the Google SDK only if you allow tracking. Without it the SDK still serves ads, but they are less personalized. The app does not make this selection itself. Google’s ad code reads the stored consent choice and the tracking status.

The publisher itself makes no automated decisions, including profiling (Art. 22 GDPR). Whether and how Google personalizes ads on the basis of usage data (profiling) is determined by Google. Details and options to object are given by Google in the consent form and in its privacy information.

Limit on ad content

The app always sets the maximum ad content rating to “General” (suitable for all audiences) in the Google SDK before the SDK starts. This is a request to the SDK. The selection of ads within this limit is done by Google.

What Google processes

When a banner is requested, your device connects to Google’s servers. The app does not log or control what the Google SDKs transmit. Like every request over the internet, an ad request inherently involves your device’s IP address and technical device and connection data. In addition, Google declares in the privacy manifest of the Google Mobile Ads SDK that the SDK may collect the following data types, for the purposes of third-party advertising, developer advertising and analytics:

• a device identifier, advertising data, product interaction data and coarse location, each linked to you (the device identifier is marked by Google as used for tracking);
• performance data, crash data and other diagnostic data, not linked to you.

Google also declares that the SDK uses the app’s local preferences storage, the system boot time and information about free storage space.

The privacy details of the app in the App Store (“App Privacy”) also cover data collected through the Google Mobile Ads SDK.

Which signals Google processes in detail, how long it keeps them, in which role it acts and how it transfers data is described by Google itself:

• Google Privacy Policy
• How Google uses information from apps that use its services

Legal basis

Where the consent form is shown and where iOS asks for the tracking permission, the legal basis is your consent, Art. 6(1)(a) GDPR. Because information is stored on your device or read from it, Section 25(1) TDDDG (the German Telecommunications Digital Services Data Protection Act) also requires your consent. You can withdraw consent at any time with effect for the future (section 6). Consent is voluntary. If you refuse or withdraw it, the app stays fully usable. After a refusal in Google’s form, Google may still serve limited ads. Google names the legal bases for this in its privacy information and in the form.

Where the check whether a consent form is required already processes personal data, the publisher relies on Art. 6(1)(f) GDPR. The legitimate interest is to obtain and respect your consent decision lawfully.

Where Google processes data under its own responsibility, Google names the legal bases in its privacy information and in the form. In regions where no form is required, Google’s terms and the law applicable in each case apply.

Responsibility and Google’s information

The integration of Google’s software is the publisher’s decision. For the processing by Google, Google’s own privacy information applies. How responsibility is divided between Google and the publisher in detail is governed by Google’s terms for AdMob. You can direct questions about advertising in the app to the publisher at any time. Where Google processes data under its own responsibility, you can also exercise your rights directly against Google.

5. App Tracking Transparency

The iOS tracking permission is the only permission the app asks for. It controls whether the Google SDK may use the advertising identifier (IDFA) of your device for tracking and personalized ads.

• The app asks once, and only if you have not decided yet, the app is active and the consent step allows ads. iOS shows this prompt at most once per installation, in the EEA and also outside it.
• The prompt is not shown if ads have been removed, if Google’s consent software does not allow ad requests, or if you have already decided. A refusal in Google’s form does not by itself prevent the prompt: it can still appear after “Do not consent”.
• The prompt is a separate decision under Apple’s rules; your answer does not depend on your choice in Google’s form.
• The prompt explains the purpose: the advertising identifier is used to show personalized ads. It is shown in German if your system language is German, and in English otherwise.
• Apple stores your answer. The app only reads the status. If you decline or the status is restricted, the app works the same and still shows ads, but they are less personalized.

The legal basis is your consent, Art. 6(1)(a) GDPR, and Section 25(1) TDDDG. You can change your answer at any time (section 6).

6. Changing or withdrawing consent

1. Privacy Options in the app. In regions where Google’s consent framework requires a consent form (as set up: the EEA, the United Kingdom and Switzerland), the menu has an entry “Privacy Options”. It is shown while ads have not been removed. Tapping it closes the menu and reopens Google’s form, where you can change your choices or refuse. If Google’s consent software then no longer allows ad requests, the banner is removed. Otherwise the banner stays. If ad requests were not allowed before and are allowed now, the app continues with the steps in section 4. In other regions, this entry is not shown.
2. iOS Settings. Under Settings > Privacy & Security > Tracking you can switch tracking on or off for this app, and for all apps with “Allow Apps to Request to Track”. The app has no setting of its own for this.
3. Remove Ads. After you buy “Remove Ads” (section 7), the app shows no banner. From the next launch on it makes no calls to Google’s advertising and consent software (no consent form, no tracking prompt). Data that Google already holds and the consent entries on your device are not affected (section 10 and section 12).
4. Deleting the app. This removes the data stored on your device, including your stored consent choice. It only affects data on your device.

Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal (Art. 7(3) GDPR).

7. In-app purchase “Remove Ads”

The app offers one in-app purchase, “Remove Ads”, which removes the banner ads. You open it through Menu > Remove Ads. The purchase screen shows the localized price supplied by the App Store, a buy button and “Restore Purchases”. It explains that this is a one-time purchase, that the ads are removed for good on every device with the same Apple Account, and that there is no subscription.

• Who processes what. Apple processes the payment, your Apple Account data, the price lookup, the signing of transactions and restoring, under Apple’s terms and privacy information. The app never sees your card or account details. The app receives only signed transactions and checks them on the device. The app only uses the product, the transaction identifier, whether the transaction is verified or revoked, and whether it is your own purchase. The app’s own code sends nothing to Apple and uploads no receipts. The exchange takes place between Apple’s StoreKit and Apple’s servers. The app has no server of its own and no accounts.
• Checks. The app checks your purchase through Apple’s StoreKit at every launch and whenever it becomes active, and it listens for purchase updates while it runs, so that purchases completed later, for example after an approval request such as Ask to Buy, are recognized. Only verified purchases of this product that have not been revoked count. After a refund the ads return. The local marker mentioned in section 3 is only a cache.
• Restore Purchases. This is available only on the purchase screen. It asks Apple to synchronize your purchases, which may ask you to sign in with your Apple Account, and then re-checks.
• After a purchase. The app shows no banner. From the next launch on it shows no consent form and no tracking prompt and makes no calls to the Google software. Data that Google already holds and the consent entries on your device are not affected (section 10 and section 12).

The legal basis is Art. 6(1)(b) GDPR (performing the purchase you made), insofar as the publisher processes any data at all. The data that Apple processes for the purchase is Apple’s responsibility under its own terms (section 11).

8. Rating prompt

Version 1.0 of the app has no rating prompt, stores no counters or dates for one and has no “Rate App” row in the menu. A rating prompt and a “Rate App” row may be added in a later version. This policy is then updated (section 13).

9. Children

Shotclock 24 Pro is a general-purpose basketball shot clock, for example for coaches, organizers, referees and scorekeepers, PE teachers and parents who run youth practice. It is not directed at children and not intended for the Kids category of the App Store. Because the display can be in front of children in sports settings, the app asks Google to serve only ads up to the content rating “General” (see section 4). It does not tag its ad or consent requests as child-directed or as coming from users under the age of consent. The processing by Google’s software described in section 4 therefore applies in principle to everyone who uses the app. The publisher itself receives no data from the app, not even from children. If you are a parent or guardian and have questions, write to hallo@mk-mc.eu.

10. Retention

• Settings on your device: until you change them or delete the app. Deleting the app removes them.
• Mute state, clock state and remaining time: only in memory while the app runs.
• Consent choice and other data of Google’s software on your device: the Google SDKs manage these entries. Deleting the app removes them from the device.
• Data processed by Google: the retention periods are set by Google (see the links in section 4). The publisher has no server and stores no app data.
• Purchase, tracking-permission and App Store data: processed and kept by Apple under its own terms.
• System log on the device: managed by iOS. The app does not transmit it.
• E-mails to the publisher: until your request is dealt with, and where a contractual relationship exists, longer in accordance with statutory retention periods.

11. Recipients and transfers to third countries

Google

Google LLC or Google Ireland Limited, depending on Google’s terms for your region, provides the ad service and the consent software (section 4). The data goes directly from your device to Google, not through the publisher.

Advertising partners

Further providers can be involved through Google in delivering and measuring ads (advertising partners, for example providers of advertising technology, and advertisers). Where Google shows a consent form, the partners are listed there under “Manage options”. Google gives further information in the form and in its privacy information. The publisher has no influence on the selection of these partners.

Apple

Apple provides the App Store, the in-app purchase and the tracking permission (section 5 and section 7). Apple processes the data it receives under its own privacy policy. In addition, Apple makes sales and download figures available to developers in App Store Connect. Aggregated app analytics and crash reports are available only for users who have switched on in iOS the sharing of diagnostics and usage data with app developers. These reports are produced by Apple. The app contains no code of its own for it.

Links that open outside the app

• “powered by KI-Agent.pro” on the main screen. This is a plain link to https://ki-agent.pro, which forwards to https://www.ki-agent.pro. The app makes no request itself. Your browser does, only when you tap the link. For the visit, the privacy policy of the website (in German) applies. The link is hidden in short windows, such as an iPhone in landscape orientation.
• “Privacy Policy” row in the menu. It opens the privacy policy of the app on the publisher’s website in your browser (the German and the English version are linked at the top of the page).
• Banner ads. See section 4.

Opening the privacy policy or ki-agent.pro is a visit to www.ki-agent.pro. The website’s hosting provider processes connection data such as the IP address in server logs. Details are in section 2 of the privacy policy of the website (in German).

The publisher itself passes no data from the app on to further recipients, because it receives none from the app. Recipients of data that arises when you use the app are the third parties named above: Google and the advertising partners (section 4), Apple and, if you tap a banner or a link, the operators of the pages that open.

Third countries

The publisher itself transfers no personal data to third countries, because the app sends none to the publisher. Google and Apple may process data outside the European Economic Area, including in the USA. They describe the safeguards they apply in their own privacy documents.

12. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR) and data portability (Art. 20 GDPR). You also have the right to object to processing based on legitimate interests (Art. 21 GDPR). You can withdraw consent at any time with effect for the future (section 6).

Please contact the publisher at hallo@mk-mc.eu. Because the publisher receives no personal data from the app and cannot identify you as a user of the app (Art. 11 GDPR), it cannot give access to data that is only on your device, at Google or at Apple, and can neither correct nor delete it. For the data on your device you have the options described in section 3 and section 6. For data processed by Google or Apple, please contact these companies; their privacy documents explain how. If you provide additional information that would allow the publisher to identify you, it will review your request accordingly (Art. 11(2) GDPR). The publisher gladly gives information about your e-mail correspondence with it.

You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. The authority responsible for the publisher is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen).

13. Changes and date

This policy is updated when the app, the services it uses or the legal requirements change. The version at this address applies. Last updated: 7 October 2026.