English
1. Information we handle
- Account: email or private relay email, display name, sign-in provider subject, and internal player ID
- Rounds: course and date, score and holes, miss counts and directions, and private notes you enter
- Crew and safety: cards you post, reactions, report reasons, block state, and crew membership
- Purchase checks: store-confirmed product and transaction state, a random installation identifier kept on your device, and hashes used to prevent duplicate processing. The server retains transaction and installation hashes, not raw purchase proof.
2. Why we use it
We use this information for sign-in and account linking, round sync, personal reports, crew features, reports and blocks, purchase restoration, and account export and deletion.
3. Information kept on your device
- Share-card images are generated on the device and are not sent to our server when you save them or open the operating-system share sheet.
- Your account-export file is passed to the operating-system share sheet on your device.
- An invite code is placed on the clipboard only when you choose to copy it.
4. Photos, analytics, and tracking
The current app does not read your photo or video library. It asks only for permission to add a generated card when you save one. The app includes Google Mobile Ads and its UMP consent SDK. Ad requests are set to non-personalized ads; we do not request App Tracking Transparency permission. There is no separate analytics or crash-reporting SDK, and the app’s own optional analytics setting does not currently send data. Google SDK processing is described separately below.
5. Services and visibility
Sign-in uses Apple or Google, and purchases use the App Store or Google Play. The authenticated API and existing cloud infrastructure process account data. A card posted to a crew is visible to members of that crew; private round notes are never copied into the card. The current API uses existing Google Cloud infrastructure. The complete processing path will be checked again after the public API is connected.
Ads and consent
We do not request ads in your first session or while removal ownership is unverified. Verified Remove Ads ownership stops all ad requests. Requests require a confirmed connection country of the US, Canada, Australia, New Zealand, or Singapore and the relevant consent conditions. Country comes from our existing load balancer; device language and store country are not used as location. We do not request device location permission.
Non-personalized ads do not mean no data is processed. Google's ad SDK can process IP address and coarse location, device or app identifiers, ad views and interactions, and SDK diagnostic and performance information. We do not send rounds, notes, or account information for ad targeting. You can review ad-related choices in the app's privacy screen. See also Google's Privacy Policy.
Google Sign-In SDK
The packaged Google Sign-In SDK declares name, email address, phone number, coarse location, user and device identifiers, other data types and other usage data, with functionality and analytics purposes. This is separate from the app’s own optional analytics setting. mig.golf does not request a phone-number sign-in scope or device location permission.
Access logs
API infrastructure can record IP address, user agent, request URL, response status and timing, and request identifiers. The current application request logger is not configured to log request bodies or authorization headers. URLs may include query strings. This scope will be checked again after the public API is connected.
6. Retention, export, and deletion
We retain information needed to provide the service while the account is active. In Settings, you can export your data as JSON and permanently delete your account. Once deletion completes there is no recovery period, and all existing sessions lose access. See Account deletion for the steps.
The operational log storage checked for the current private API is set to 30 days. Required administrative activity and system-event audit logs are retained separately for 400 days. Deleting an account does not immediately erase these logs. Backup retention, additional organization-level log routing and logging after public API connection still need verification.
7. Contact
For privacy or account requests, email help@incode-labs.org. Do not email passwords, sign-in codes, tokens, or raw purchase proof.