Privacy Policy

Effective date: 5 August 2026

This Privacy Policy describes how Al_Fom Dev ("we", "us", or the "Service Provider") handles information in the MiniGolf Helper mobile application. For privacy questions or requests, contact alfom.dev80@gmail.com.

Privacy summary

MiniGolf Helper is an offline-first scorekeeping application. Game names, player and team names, scores, identifiers, dates, and QR payloads stay on the devices used for the game unless a user intentionally shows a QR code to another participant. We do not operate a server that receives this game content.

On Android, Firebase Analytics and Firebase Crashlytics diagnostics are enabled automatically. They are used to understand app usage and diagnose failures, and our code does not send player names, scores, or QR contents to these services. Firebase telemetry is not enabled in the iOS version described by this policy.

RevenueCat is initialized only when a user opens a Premium purchase flow, reaches the Premium gate, restores a purchase, or manages a subscription. Merely opening the app, joining a QR game, or viewing locally saved games does not create a RevenueCat customer.

Data stored locally

The app stores the following data on the device:

This data is required for the app's local functionality. It is not uploaded to our servers. A user may delete all locally saved games and results from Settings → Data → Clear game history. Language, Premium status, and the persistent free-game counter are not removed by that action. Uninstalling the app removes its local data according to the operating system's behavior.

The app excludes its local files from Android cloud backup and device transfer. On iOS it marks the application documents directory as excluded from iCloud backup.

QR codes and camera

The camera is used only when the user chooses to scan a game or score QR code. Camera frames are processed on the device and are not saved or uploaded by MiniGolf Helper. QR payloads are exchanged directly between nearby devices under the users' control and may contain game details, player names, teams, scores, and identifiers.

Firebase diagnostics on Android

Google Analytics for Firebase

Usage analytics are enabled by default on Android. Google Analytics for Firebase may process an app-instance identifier, app interactions and lifecycle events, app and device information, operating-system information, approximate region derived from the network connection, and purchase-related events made available by the platform. It is used to understand feature usage and improve the app. It does not receive player names, scores, or QR contents from our code.

The Android release does not request Google advertising ID permissions, and Analytics advertising ID collection is disabled.

Firebase Crashlytics

Crash reporting is enabled by default on Android. Firebase Crashlytics may process crash traces, exception details, timestamps, app version, installation identifiers, device model, operating-system information, and technical state related to a failure. It is used to diagnose and fix crashes. It does not intentionally include player names, scores, or QR contents.

We rely on our legitimate interests in maintaining stability and improving MiniGolf Helper for this diagnostic processing. To raise a privacy concern, object to processing, or exercise an applicable data-protection right, contact alfom.dev80@gmail.com. Google states that Crashlytics keeps crash traces and associated identifiers for approximately 90 days before beginning removal from live and backup systems.

For Firebase's processing details, see Firebase Privacy and Security.

Premium purchases and RevenueCat

When a Premium flow is used, RevenueCat may process an automatically generated anonymous customer identifier, app and device information, network information such as IP address, product identifiers, purchase and transaction history, subscription status, and store-provided receipt data. Automatic advertising identifier collection is disabled in the app's RevenueCat configuration.

This processing is necessary to show available plans, verify purchases, restore Premium access, and manage subscription status. RevenueCat and the relevant app store process purchase data under their own terms and privacy policies. The RevenueCat anonymous identifier becomes visible in Settings → Premium → Purchase support ID after RevenueCat has been initialized. Include that identifier in access or deletion requests so the record can be located.

See RevenueCat Privacy and Google Privacy.

Sharing and service providers

We do not sell personal data or use it for advertising. Data is shared only as required to provide the features described above:

These providers may process data outside Sweden or the European Economic Area using the safeguards described in their applicable terms, including adequacy mechanisms or Standard Contractual Clauses where required.

Retention

We retain correspondence about privacy or support requests only as long as necessary to respond and meet legal obligations.

Your rights

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, objection, or portability of personal data and to complain to a supervisory authority. In Sweden, the supervisory authority is Integritetsskyddsmyndigheten (IMY).

To make a request, email alfom.dev80@gmail.com. For RevenueCat requests, include the Purchase support ID shown in the app. We may request information necessary to verify the request and locate relevant records.

Children

MiniGolf Helper is not directed to children under 13 and we do not knowingly collect personal data from children through an account or server operated by us. Adults organizing a game should avoid entering a child's full name without an appropriate reason and permission; a nickname may be used instead.

Security

Network communication with Firebase, RevenueCat, and app stores uses encrypted HTTPS connections provided by their SDKs. Local game data is protected by the device's operating-system security. No method of storage or transmission can be guaranteed to be completely secure.

Changes

We may update this policy when the app or legal requirements change. The current version and effective date will remain available at this URL. Material changes will be communicated in the app where required.

Contact

Al_Fom Dev
Email: alfom.dev80@gmail.com