Zocker Zocker
Privacy Policy
This policy explains which data the Zocker app, this website and e-mail support process, for what purpose, on which legal basis, for how long – and which rights you have.
1. Controller
Paul MünchhausenRichard-Wagner-Str. 22
66773 Schwalbach
Germany
E-mail: paul@muenchhausen.dev
2. Scope and summary
This policy covers the Zocker app from version 1.1.5 for iPhone and Android, the website zocker.muenchhausen.dev and requests sent to paul@muenchhausen.dev. Earlier app versions (up to 1.1.4) had no account feature; an older policy describing only local processing applied to them.
In short:
- Without an account everything stays on your device. Names, rounds, results, net scores, stakes and payment status never leave your phone.
- An account is optional. It is only needed to find other registered players, connect with them and compare new net scores automatically. Sign-in is via Apple or Google and handled by Clerk; profile, connections and shared net scores are stored by Convex in a data centre in Ireland.
- Only net scores and the day of play are shared – solely with players you are connected to, and only from the moment of the connection. Stakes, payment status, manual corrections and older rounds stay local.
- No advertising, no analytics, tracking or profiling services, neither in the app nor on this website.
- An account is not a cloud backup. Your local ledger is not uploaded and cannot be restored from the account.
3. Using the app without an account
The app stores the following data exclusively in its protected storage area on your device:
- names of your fellow players as you enter them, and their archive status
- rounds with date, result per player (won, draw, lost, absent), net scores, stakes, payment status and optionally the golf club
- a list of your golf clubs and a favourite
- settings such as appearance (light/dark) and whether the welcome screen has been shown
- possibly data from the former Bellek trip still present from older versions; this version does not fetch new trip data
Without signing in, the app transmits none of this data to us or to third parties. We have no access to it. Processing serves your own use of the app (Art. 6(1)(b) GDPR, insofar as the GDPR applies to purely local processing at all).
Permissions: For export and import Zocker uses the system file and share dialogs. The app does not request access to contacts, photos, location, microphone, camera or advertising identifiers and sends no push notifications.
4. Backup and restore
Only on your explicit action does the app create a JSON backup file or read a previously chosen file. The file contains your local data in plain text (names, rounds, results, stakes, payment status, clubs and any cached online links) but no sign-in tokens and no pending uploads. Where you store or send the file is up to you via the system dialogs; the app never uploads backups automatically. Imported online links stay inactive until the same account confirms them again; imported rounds are not published online retroactively.
5. Optional account
5.1 Sign-in with Apple or Google (Clerk)
Sign-in and session management are handled by Clerk, Inc. (USA) as our processor. You sign in with your Apple or Google account – directly in the app or, as a fallback, on a sign-in page operated by Clerk in your browser. Clerk processes:
- the identifier of your Apple or Google account provided by that provider, the associated e-mail address (for Apple possibly a relay address from “Hide My Email”) and – if the provider supplies it – first and last name
- a user identifier assigned by Clerk, which serves as your account identifier in Zocker
- session data: sign-in times, device type or browser identifier and IP address at sign-in, session tokens
- for browser sign-in, the technical connection data of the sign-in page request
The app sends no usage statistics to Clerk; the Clerk SDK’s optional telemetry is disabled.
Apple and Google process the sign-in at their respective services under their own responsibility and privacy policies (Apple Distribution International Ltd., Ireland, and Google Ireland Limited, Ireland). Whether your name is passed on and whether Apple shares your real e-mail address is your choice in the provider’s sign-in dialog.
Legal basis: Art. 6(1)(b) GDPR (providing the account features you requested). Session data for abuse prevention: Art. 6(1)(f) GDPR.
5.2 Profile, connections and shared net scores (Convex)
The app’s account data is stored by Convex, Inc. (USA) as our processor in a deployment in region eu-west-1 (Ireland). The following is stored, each linked to your Clerk account identifier:
| Data | Content | Purpose |
|---|---|---|
| Profile | Display name (confirmed or edited by you), a normalised search form of the name, a random six-character player code, optional home club, search visibility, sharing status with timestamp, creation and update time | Being found and identified by fellow players |
| Connections | Identifiers of both connected accounts, who initiated the connection, status (active/ended), time and day of play of the connection, end | Determining with whom new net scores are shared |
| Blocks | Identifier of the blocked account and time | Preventing unwanted contact; blocked profiles can no longer find each other |
| Own net scores | Net score, day of play and device time zone, version counter, time of first capture, withdrawal status, sharing status at capture | Comparison with connected players |
| Share entries | Which net scores are visible to which connected account for which day | Limiting access to connections |
| Operation identifiers | Random identifier, type and result of each upload | Prevents duplicate processing when retrying after connection loss |
| Search counter | Number of your searches in the current 30-second window | Limit of 10 searches per 30 seconds |
| Deletion marker | After account deletion: account identifier, time, deletion status, number of attempts, last error code, result of the Apple revocation | Rejecting old tokens, completing deletion reliably |
Search terms themselves are not stored. The app does not upload existing offline rounds retroactively; only net scores captured after the connection and while sharing was enabled are shared. Convex logs function calls (function name, time, duration, errors) briefly for debugging; we have not set up a persistent log export.
Legal basis: Art. 6(1)(b) GDPR. Search counter, operation identifiers and deletion marker: Art. 6(1)(f) GDPR (operational security and abuse prevention).
5.3 What others can see
- While “Visible in search” is on, signed-in users can find you by display name or player code and see display name, player code and home club.
- A connection requires both accounts to have online sharing enabled. From then on connected players see your new net scores with the day of play. If you end the connection or sharing, access ends; results they already copied into their own ledger remain there.
- A block ends the connection and hides both profiles from each other.
- At most 100 active connections per account.
6. This website
The website is static and delivered via Cloudflare Pages by Cloudflare, Inc. (USA). When you visit, Cloudflare processes technical connection data (IP address, time, requested address, browser identifier, referrer) for delivery, attack mitigation and troubleshooting. We have not enabled access logging, set no cookies, use no web analytics and embed no third-party content (not even fonts). The pages work without JavaScript.
Legal basis: Art. 6(1)(f) GDPR (secure and efficient provision of the website).
7. E-mail support
If you write to paul@muenchhausen.dev, we process your e-mail address, the content of your message and its time in order to handle your request. The mailbox is hosted by Google (Google Ireland Limited, Ireland). Account deletion by e-mail follows the procedure on the Delete account page; we verify that the request belongs to the account via the e-mail address stored in it.
Legal basis: Art. 6(1)(b) GDPR (handling your request); for data protection requests Art. 6(1)(c) GDPR.
8. Recipients and transfers to third countries
| Recipient | Role | Location of processing | Safeguards |
|---|---|---|---|
| Clerk, Inc., USA | Processor (sign-in, sessions) | USA (hosted on Google Cloud and Cloudflare) | Data processing agreement with EU standard contractual clauses; Clerk states it is certified under the EU-US Data Privacy Framework |
| Convex, Inc., USA | Processor (app account data) | Deployment in Ireland (AWS eu-west-1); administrative access by the provider from the USA possible | Data processing agreement with EU standard contractual clauses |
| Cloudflare, Inc., USA | Processor (website delivery) | globally distributed network | Data processing agreement with EU standard contractual clauses; Cloudflare is certified under the EU-US Data Privacy Framework |
| Google Ireland Limited | Processor (support mailbox) | EU/EEA, access from third countries possible | Data processing agreement with EU standard contractual clauses |
| Apple Distribution International Ltd. / Apple Inc. | Independent controller (Sign in with Apple, App Store) | Ireland / USA | Apple’s privacy policy |
| Google Ireland Limited / Google LLC | Independent controller (Sign in with Google, Google Play) | Ireland / USA | Google’s privacy policy |
Beyond this we only disclose data when legally obliged to do so. Other users receive only the information described in section 5.3.
9. Retention
| Data | Duration |
|---|---|
| Local app data and backup files | Until you delete them in the app, uninstall the app or delete the file yourself |
| Profile, connections, blocks, net scores, share entries, operation identifiers, search counter | While the account exists. After a deletion request access is blocked immediately and the data is removed in steps, usually within minutes |
| Deletion marker after account deletion | 30 days after the Clerk account was deleted successfully, then removed automatically. If deletion at the provider fails, the marker remains until completion and deletion is retried automatically |
| Sign-in data at Clerk | The Clerk user account is deleted as part of account deletion. Contractually Clerk must remove remaining copies no later than 90 days after the end of the contract |
| Backups at Convex | If backups of the deployment are taken, Convex keeps manual and daily backups for 7 days and weekly backups for 14 days according to its documentation. Deleted records additionally remain in the database’s internal transaction log for a limited technical period |
| Function logs at Convex | Only a short history of recent calls; no persistent export |
| Website connection data at Cloudflare | Not stored by us; Cloudflare processes it briefly for delivery and security under its own terms |
| Support e-mails | We delete the correspondence no later than 3 months after the request is closed, unless a statutory retention duty (e.g. tax law) applies to an individual message. Deletion requests are documented until completion is confirmed |
10. Deleting your account
You can delete your account at any time in the app under Einstellungen → Konto → Konto löschen (Settings → Account → Delete account) or – without the app – by e-mail. Scope, procedure and limits are described on the Delete account page. Results already copied by fellow players into their local ledgers, your own backup files and your Apple or Google account are not affected.
11. Your rights
You have the right to access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on Art. 6(1)(f) GDPR (Art. 21). Send requests to paul@muenchhausen.dev. For account data you can largely exercise access, rectification and erasure yourself in the app: edit your profile, end connections, delete the account. Data that exists only locally on your device is entirely in your hands.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the member state of your residence or of the alleged infringement.
There is no automated decision-making or profiling. You are not obliged to provide data; without an account only the online features are unavailable.
12. Platform services
Download, purchase, updates and reviews of the app via the Apple App Store or Google Play are the responsibility of the respective platform operator, who processes data independently under its own privacy policy. We receive no personal data of individual users from them.
13. Changes
We update this policy when the app or the services used change. The current version with its date is always available at this address; the app links to it. We announce material changes in the app.