1. Core privacy position
Ball Python Morph Calculator is designed around a local-first product model. The app is intended to let users run genetics calculations, browse reference morph information, and keep collection records on the device without requiring a public profile or community account.
We do not describe the product as a social platform, and the core app experience does not require users to upload their local collection data to a central server in order to use the MVP feature set.
2. Information handled by the app
Information stored locally on the device
- Collection records entered by the user, including animal names, IDs, tags, sex, and weight values.
- Pairing inputs and saved calculation history created inside the app.
- On-device app preferences such as language and onboarding state.
Information transmitted off the device
The current Google Play build includes Google Mobile Ads, Firebase Analytics, and Firebase Crashlytics. These services may transmit limited technical and usage data off the device for advertising, analytics, fraud prevention, security, and app stability purposes.
- Device or other IDs, such as advertising ID, app instance ID, app set ID, installation identifiers, and similar SDK-generated identifiers.
- App activity data such as screen views, sessions, ad interactions, and high-level in-app usage events.
- Crash logs, diagnostics, and app performance information, which may include technical device, operating system, network, and app-state metadata.
- Custom diagnostic keys and event metadata used to understand crashes or product health, such as the active screen and aggregate calculation counts.
Based on the current implementation, the app is not intended to send user-entered morph names, collection notes, or full local genetics records as analytics event payloads. However, third-party SDKs may still process device identifiers, app interaction signals, and technical diagnostics under their own product behavior and privacy terms.
3. How information is used
- To provide local genetics calculations, collection functionality, and reference browsing inside the app.
- To measure app stability, diagnose crashes, understand product usage patterns, and improve technical performance.
- To display and measure advertising where ad placements are enabled in the distributed build.
- To maintain, improve, and secure the app and website.
5. Data retention
Local records remain on the user's device until the user edits them, clears app storage, or uninstalls the app. Diagnostic, analytics, and advertising-related data transmitted to Google services may be retained according to the configuration and retention rules of the relevant Google products in use.
6. User choices and controls
- Users can remove local app data by clearing app storage or uninstalling the app.
- Users can use the app's telemetry control, where available, to manage certain diagnostic reporting preferences.
- Users can manage advertising identifiers and ad privacy controls through Android and Google settings, subject to the controls available on their device and account.
- Users can contact us regarding privacy questions or deletion-related requests using the support contact published on this site or the app listing.
7. Children's privacy
The app and website are not directed to children under the age required by applicable law for consent. If you believe information has been provided by a child in violation of applicable law, contact us so that we can review the request.
8. Policy changes
We may update this Privacy Policy from time to time to reflect app changes, legal requirements, or operational updates. When we make material changes, we will update the effective date on this page.
9. Contact us
For privacy questions, deletion requests, or policy-related inquiries, contact [email protected].