Privacy Policy
The Short Version
Your taco data lives on your device. We never sell it, share it, or use it for advertising. An account is optional — required only if you choose to enable the optional cloud backup feature.
What Data the App Stores Locally
All meal logs, taco ratings, ingredients, photos, favorites, and settings are stored in a local Room database on your device. Nothing is sent anywhere by default. You can export your entire history at any time as a CSV file. Uninstalling the app deletes this local database.
Photos you attach to meals are saved to your device's Pictures folder via Android's MediaStore (API 29+), so they survive an uninstall. On older Android versions, photos are stored in the app's private storage and are removed on uninstall.
Crash Reporting (Always On)
TacoLogger uses Firebase Crashlytics (provided by Google) to catch bugs automatically. Crash reports include device model, Android version, and a stack trace. No meal content or personal information is included. Crash reporting is disabled in debug builds.
Firebase also collects a small set of standard telemetry automatically — things like app version, device type, and session length. This is Google-controlled baseline data governed by Google's privacy policy.
Advanced Analytics (Opt-In, Off by Default)
TacoLogger includes an optional analytics feature to help improve the app's automatic ingredient classifier. It is turned off by default and can be enabled in Settings → Share usage data to improve TacoLogger.
When opted in, the following is sent on each meal save:
- Meal type (Breakfast / Lunch / Dinner / Snack)
- Up to 5 ingredient names as you typed them (e.g. "shrimp", "al pastor")
- The filling categories those ingredients classify into (Beef, Pork, Poultry, Seafood, Veggie, etc.)
- Feature usage signals with no meal content: stats viewed, CSV exported/imported, achievements unlocked, GPS tapped, bulk edit applied
This data is linked to an anonymous Firebase device ID — not to your name, email, or Google account. No location names, photos, notes, ratings, or restaurant names are ever sent.
You can opt out at any time from the Settings screen and previously collected events cannot be retroactively deleted from Firebase, but no new events will be sent after opting out.
Optional Cloud Backup (Pro Feature)
If you choose to enable cloud backup (a Pro-only feature), the app will ask you to sign in with your Google account via Firebase Authentication. Once signed in, your meal logs are synced to Firebase Firestore under your Google Account's UID — only you can read your data.
- Cloud backup is strictly opt-in. The app functions fully offline without it.
- Only the meal data you explicitly logged is synced — no location history, no browsing behavior, no identifiers beyond your Firebase UID.
- Photos are not synced to the cloud — only the local file path string is stored in Firestore.
- Deleting a meal marks it as deleted in Firestore; it is not immediately purged.
- You can sign out at any time from the Settings screen, which stops all future syncing.
Location Data
TacoLogger requests the ACCESS_FINE_LOCATION and
ACCESS_COARSE_LOCATION permissions to power the GPS restaurant
discovery feature (Pro). Location is only accessed when you tap the GPS
button in the meal entry form — the app does not track your location in the
background. The location is used to search for nearby restaurants via the
Google Places API and is not stored persistently beyond the restaurant name
you choose.
Google Places API usage is governed by Google's privacy policy linked above.
Camera & Storage
TacoLogger requests camera and storage permissions solely to let you attach photos to your meal entries. Photos are saved to your device only and are never uploaded unless you explicitly share them via Android's system share sheet.
Advertising
There are no ads in TacoLogger. There will never be ads in TacoLogger.
Children's Privacy
TacoLogger is not directed at children under 13. We do not knowingly collect personal information from children.
This Website
This website (the one you're reading right now) uses no cookies, no tracking scripts, no analytics, and no third-party services. It is a plain static HTML/CSS site hosted on GitHub Pages. No personal information is collected from visitors.
Changes to This Policy
If we make material changes to this policy, we'll update the "Last updated" date above. Significant changes will also be noted in the app's What's New dialog on the next update.
Contact
Questions, concerns, or data requests? Reach out:
Email: [privacy contact email — add before Play Store submission]