1. About this policy
This Privacy Policy explains how FUEL / RUN, package name com.antonio.runningCalculator, handles information when you use the Android app. The app is provided by [DEVELOPER_NAME] (“we”, “us”).
Privacy contact: [CONTACT_EMAIL].
2. Information you enter
The app processes the information you provide to create and manage fueling plans: activity and workout type, expected duration, tested carbohydrate tolerance, calculated nutrition amounts, saved plan titles and dates, and fueling intervals. If you save food entries, these may include food names, carbohydrate amounts and portions.
Your athlete profile may contain a display name, optional weight and tested fueling preferences. These values can include fitness or health-related information.
Calculator drafts, profile information and food entries are stored on your device. The calculator performs its calculations on the device. Saved plans are also stored locally. Android device backup or transfer services may handle eligible local app settings according to your device settings and the app’s backup configuration.
3. Optional cloud synchronization
If you choose cloud synchronization, saved plan information, including its activity details, duration, carbohydrate tolerance and calculated results, is uploaded to Google Cloud Firestore so that the app can synchronize it.
Firebase Authentication associates the cloud records with a user identifier. Where no signed-in account is available, the app uses anonymous sign-in, which creates a pseudonymous identifier without requiring an email address or password. This identifier is not the same as completely anonymous data.
Once cloud synchronization has been enabled, later plan changes can synchronize automatically. Authentication and cloud requests also involve technical information, such as IP addresses and service or device identifiers, needed to operate and protect the services. The profile’s display name and weight are not included in the plan synchronization implemented in this version.
4. Usage and diagnostic information
Google Analytics for Firebase processes app usage events and technical information to help us understand how the app is used. This can include app-instance identifiers, app and device details, language, and approximate geographic information. Advertising identifiers may be processed when their collection is enabled and permitted by the device settings.
Firebase Crashlytics processes crash reports, stack traces, app and device details, and installation identifiers to help us diagnose faults.
Firebase Performance Monitoring processes performance measurements, device information, installation identifiers and IP-related information to help us understand app responsiveness and network performance. The data available depends on SDK configuration and the events instrumented in the app.
If you contact us, we receive the email address and information you include in your message so we can respond. Please include only the information needed for your request.
5. Why information is used and who receives it
We use information to calculate and save plans, remember preferences, provide requested synchronization, respond to support requests, protect the service, and understand or fix reliability and usability problems.
Google/Firebase processes information for the services described above. Our email service provider processes support correspondence. Information may also be disclosed when legally required or necessary to address fraud, abuse or security incidents.
We do not sell personal information. The nutrition and profile information described here is not used by us for personalized advertising.
Google and other service providers may process information outside your country under their applicable privacy and data-processing terms. For provider details, see Google’s Privacy Policy and Firebase’s Privacy and Security information, linked below.
6. Retention
Local profile information, drafts and food entries remain on the device until changed or removed, or until the app’s local storage is cleared. Copies made by Android backup services follow those services’ settings and retention rules.
Saved cloud plans remain until their content is deleted or a verified request to remove the associated cloud data is completed. Deleting a plan removes its content from the active plan record; a minimal deletion marker can remain while the cloud identity exists to prevent an older copy from being restored during synchronization.
Google Analytics user-level and event-level retention follows this configured setting: [ANALYTICS_RETENTION_SETTING]. Aggregate reports may follow different retention rules.
Under Firebase’s published retention terms, Crashlytics starts removing crash information and associated identifiers after 90 days. Performance Monitoring starts removal after 30 days for IP-associated events and 60 days for installation-associated and de-identified performance data. Authentication records are retained until deleted; some provider backups and security records are removed later under Firebase’s retention terms.
Support messages are retained while needed to resolve the request, address follow-up questions, and meet any applicable record-keeping requirements.
7. Your choices and deletion requests
You can edit your profile and remove individual plans using the controls provided in the app. For a cloud-synced plan, deletion must synchronize successfully before the active cloud copy reflects the change.
Clearing app storage or uninstalling the app removes local app data but does not itself delete records already stored in Firebase. Doing so can also remove the anonymous sign-in credentials needed to access the existing cloud records.
To request access, correction, or deletion of information we hold, contact [CONTACT_EMAIL] with the subject “FUEL / RUN privacy request”. Tell us whether you want to remove saved cloud plans, an associated sign-in identity, or support correspondence. We may request limited information needed to identify the relevant records and verify your authority. Do not send passwords or authentication tokens.
We handle verified requests under applicable requirements and the deletion capabilities of the relevant providers. We will explain if limited information must be retained for a legal or security reason, or if we cannot identify records associated with an anonymous installation.
Depending on your location, you may have additional rights, including restriction of processing, portability, objection, withdrawal of consent where consent applies, and a complaint to the appropriate data protection authority. Contact us to exercise applicable rights.
8. Security
The app uses Android app-private storage for local information. Firebase communications use encrypted HTTPS connections, and access to cloud records is restricted through authentication and database access controls. No storage or transmission method can guarantee absolute security.
9. Children
FUEL / RUN is not directed to children under 13. If you believe a child has provided personal information to us, contact us so we can investigate and take appropriate action.
10. This policy page and external services
This policy page does not include analytics scripts, advertising or a contact form. When hosted on GitHub Pages, GitHub processes visitors’ IP addresses for security under the GitHub Privacy Statement. If you follow an external link or contact us by email, the relevant provider’s terms and privacy practices also apply.
11. Changes and contact
We may update this policy to reflect changes in the app or how information is handled. The “Last updated” date identifies the latest version. Where required, material changes will be communicated separately.
For privacy questions, contact [DEVELOPER_NAME] at [CONTACT_EMAIL].