1. About this policy
FuelSum is an Android app provided by Protus App Development (“Protus”, “we”, or “us”) for fuel records, journey estimates and trip recording. This policy explains how information is handled when you use FuelSum and contact us about it.
You do not need a FuelSum account. FuelSum does not provide a developer-hosted account or cloud database of your fuel and trip records. Google services described below process usage, diagnostic or payment information separately.
2. Your records and location
Information you enter is stored in the app’s private storage on your device. This can include vehicle details and nicknames, fuel purchases and prices, odometer readings, receipt photos, budgets, saved estimates, trip dates and distances, and optional notes, journey names, business labels or client/project details. FuelSum uses these records to provide its calculations, history, reports and backups.
Live trip recording
With Android location permission, FuelSum uses precise or approximate location to calculate distance during a trip. An active recording can continue when you leave the app or turn off the screen using an Android foreground service and an ongoing notification. You can pause or finish the recording, or revoke location permission in Android settings.
Automatic car trips are a one-time purchase through Google Play. Manual live trips stay free and do not require that purchase. Settings → Live recording → Start trips automatically stays off until the purchase is completed and you turn the setting on. When it is on, FuelSum uses Android physical-activity detection on your device to notice travel in a vehicle, then starts the same recording. It cannot tell whether you are driving or riding as a passenger. A finished trip is saved on the device. If you were a passenger, you can remove that trip from the save screen or later from trip history so it is not counted. Turning the setting off stops new automatic trips. You can also revoke physical-activity permission in Android settings. Payment handling for this purchase is described in section 6.
Location samples and activity detection are processed on the device to measure distance and to decide when an automatic trip starts or ends. FuelSum does not upload a route, GPS coordinates or activity-detection results to Protus, Analytics or Crashlytics. Android and Google Play services provide location and activity detection under your device’s settings and Google’s policies. Manual fuel entry and calculations can be used without location or physical-activity permission.
Photos and files
You choose a receipt photo through Android’s file/photo interface or take one with your camera app. FuelSum accesses the image you select or capture, rather than your whole photo library. A saved receipt is kept with its fuel purchase and can be included in a backup. The camera app or photo provider may keep its own copy under its own settings.
3. Usage statistics
Google Analytics for Firebase is on by default. It sends information to Google so we can understand which features are used and improve the app. This includes app interactions and screen names, app/version and device information, session information, an app-instance identifier, and approximate location derived from network information. Automatic events can include app launches, sessions and in-app purchase activity. See Google’s Analytics data collection description.
FuelSum’s own events use a limited set of categories, such as saving a purchase or completing a backup. These custom events do not include your vehicle nicknames, receipt contents, fuel amounts or prices, trip names, notes, client/project details, or GPS coordinates. We do not assign a name, email address or account user ID to your Analytics activity.
Turn off Settings → Privacy → Usage statistics to disable Analytics collection. FuelSum then resets locally stored Analytics data and its app-instance identifier. This does not delete information already received by Google. Previously saved OFF choices are respected when you reopen the app.
FuelSum does not display ads. Its configuration disables advertising-ID collection and denies advertising storage, advertising user-data and personalized-advertising consent.
4. Crash reports
Firebase Crashlytics is on by default. Google receives crash reports, app-not-responding reports and selected nonfatal diagnostics so we can find and fix faults. Reports can contain stack traces, technical error information, app and device state, device/OS and app versions, session information, and installation identifiers. If usage statistics are also enabled, recent app-interaction events can help explain what happened before an error. See Firebase’s Crashlytics disclosure.
We do not attach your fuel database, receipts, GPS coordinates or a personal account identity to crash reports. FuelSum removes original messages and nested causes from the nonfatal errors it deliberately records; automatic crash reports can still contain technical exception details.
Turn off Settings → Privacy → Crash reports to disable automatic Crashlytics report uploads. FuelSum also asks Crashlytics to delete unsent reports. The switch does not remove reports already uploaded, and it is independent of the Usage statistics switch.
5. Receipt text recognition
FuelSum uses Google ML Kit to read receipt text on your device and suggest fuel-entry values. The receipt image and recognized text are not sent to Google for this recognition. You decide whether to apply the suggestions. See ML Kit’s privacy terms.
ML Kit separately sends technical metrics to Google, such as app and device details, a per-installation identifier, processing times, image dimensions/formats, feature usage and error codes. These help Google maintain and improve the recognition service. ML Kit can also contact Google for service updates and compatibility information. Its metrics are separate from Firebase Analytics and Crashlytics and are not controlled by FuelSum’s two Firebase privacy switches. See ML Kit’s data disclosure.
6. Payments, backups and sharing
Automatic tracking purchase
Buying automatic car-trip recording is optional and is a one-time purchase processed through Google Play Billing. You do not create a FuelSum account to pay. Google handles your Google account, payment method and transaction under its own policies. FuelSum receives the product identifier, purchase token and purchase status so it can confirm and acknowledge the purchase. FuelSum does not receive your full payment-card or bank-account details.
FuelSum stores only whether automatic tracking is unlocked, in private app storage on your device. That yes-or-no flag is not included in fuel-record backups and is not sent to Analytics or Crashlytics. Google Play keeps the purchase record. If you reinstall FuelSum or clear the app’s storage, the app asks Play whether that Google account still owns the purchase. If Play reports that the purchase was refunded or revoked, FuelSum removes the unlock. See Google’s Privacy Policy.
Optional developer tips
One-time tips are processed through Google Play Billing. Google handles your Google account, payment method and transaction under its own policies. FuelSum receives product identifiers, purchase tokens and purchase status to complete and acknowledge the transaction; we can access the transaction information Google Play makes available to developers. FuelSum does not receive your full payment-card or bank-account details. A completed tip is consumed so another tip can be purchased later. Google may retain payment records for its transaction, fraud-prevention and legal obligations. See Google’s Privacy Policy.
Recovery copies and exports
Automatic recovery copies are enabled by default in the app’s private storage. If you select an additional backup folder, FuelSum writes copies there too. A folder offered by a cloud-storage provider may sync according to that provider’s settings and privacy policy. Backups may contain your records, notes and receipt photos.
When you share a backup, report or estimate, you choose the destination app or recipient using Android’s sharing tools. That destination handles the shared data under its own terms. FuelSum’s backup files are not password-protected or encrypted by FuelSum; choose storage and recipients you trust.
The Review app action opens Google Play, where reviews and account information are handled by Google.
7. Retention and deletion
- Active local records: kept until you remove them, clear the app’s storage or uninstall it. Use Settings → Delete all local records to clear the active records and their receipt photos.
- Recovery copies: automatic backup retention normally keeps the ten most recent recovery points. Deleting active records does not erase existing recovery copies, exported files, shared copies or copies in a selected backup folder. Clearing Android app storage or uninstalling removes app-private recovery copies; delete external copies separately through their storage provider or recipient.
- Analytics: retained according to the Google Analytics property’s retention settings and Google’s applicable retention/deletion rules. Aggregate reports can remain after individual event data expires. Turning collection off stops future collection rather than erasing previously received data.
- Crash reports: Google states that Crashlytics keeps crash data and associated identifiers for 90 days before beginning removal from its live and backup systems. See Firebase’s retention information.
- Automatic-tracking unlock: the on-device yes-or-no flag is removed when you clear the app’s storage or uninstall it. Google Play may keep the payment record under its own retention rules. The app can restore the unlock from Play on the same Google account.
- ML Kit and Google Play: technical metrics and payment records are handled under the Google policies linked above.
- Messages you send us: we use your email address and message contents to respond and handle your request, and keep them as needed for that purpose and applicable record-keeping obligations.
After deleting all local records: the app returns its privacy settings to their defaults, including Usage statistics and Crash reports being ON. You can turn them off again in Settings → Privacy.
8. Security and service providers
FuelSum uses Android’s private app storage and permission controls. Firebase and ML Kit encrypt their network transfers using HTTPS. Your device’s security, any exported copies and any folder or app you select also affect the protection of your information; no storage or transmission method is completely secure.
Google provides Analytics, Crashlytics, receipt-recognition technology, Play Billing and underlying Android services. Google and its service providers may process information in countries outside your own. Their applicable policies and safeguards include Google’s Privacy Policy and Firebase’s privacy and security information.
We use the service information described here to operate, understand and improve FuelSum. We do not sell your personal information. Information you choose to send us may also be disclosed where required by law or necessary to address fraud, security incidents or legal claims.
9. Your choices and requests
You can independently turn off the two Firebase services in Settings → Privacy, choose not to buy automatic tracking, turn automatic trip recording off in Settings → Live recording, manage location, physical-activity and notification permissions in Android settings, change automatic-backup settings, and edit, export or delete your local records. You can remove a saved trip if you were a passenger. Manual live trips remain available without the automatic-tracking purchase.
Depending on applicable law, you may have rights to request access, correction or deletion of personal information, or to object to or restrict its processing. Contact us using the details below. We may need enough information to verify and locate the relevant information. We cannot directly access records that exist only on your device, and telemetry is not linked to a FuelSum account. A request may therefore require additional information and is subject to applicable retention obligations and technical limits.
You do not need to send us your fuel database or receipts to ask a privacy question. Include only what is necessary for your request.
10. Children and policy updates
FuelSum is designed for managing vehicle travel and fuel costs and is not directed at children. If you believe a child has provided personal information to us, contact us so we can investigate and address it.
We may update this policy as FuelSum or its services change. The updated policy will show a new date on this page. Where required, we will provide additional notice or seek consent before a change takes effect.
11. Contact us
For questions about this policy or a privacy request, contact Protus App Development, the developer of FuelSum.
protusappdev@gmail.com
protusappdev.co.za
Please include “FuelSum privacy” in your subject line so we can identify your request.