Last updated: July 2026
CIDER (“the app”) is developed by Kartikeya Mudliyar (“we,” “us,” “the developer”). This policy explains what data CIDER collects, how it is used, and how it is stored.
CIDER is a local-first driving companion app. Almost everything it does happens entirely on your device. This policy is written to be precise about the few places data does leave the device.
Location (GPS). While a trip is active, CIDER uses your device’s location to calculate speed, distance, and detect hard-braking events. This happens only while the app has detected you are connected to a saved vehicle’s Bluetooth or Android Auto. Location data is processed in memory during the trip; only the start and end coordinates of a completed trip are saved to your trip history, stored locally on your device.
Accelerometer data. CIDER briefly samples your device’s motion sensor to detect sudden hard-braking events. This raw sensor data is never stored — only a count of detected events is saved per trip.
Bluetooth device information. CIDER reads the name and MAC address of Bluetooth devices your phone connects to, so it can recognize your car and activate automatically. This information is stored locally and is used only to match against vehicles you’ve explicitly added in the app.
Microphone / voice. After certain reminders, CIDER may briefly listen for a short spoken response (for example, to defer or dismiss a reminder). This uses your device’s built-in speech recognition system. CIDER does not store or log what you say — only the length of your response is recorded internally for troubleshooting. Microphone access is optional; if you don’t grant it, this feature is simply unavailable and everything else in the app works normally.
Trip and driving data. CIDER calculates and stores trip duration, distance, average and maximum speed, warning counts, braking events, and a driving score. This is stored locally in a database on your device and is used to power your trip history and dashboard.
Settings and preferences. Your chosen thresholds, saved vehicles, voice preference, and feature toggles are stored locally on your device.
CIDER does not access your contacts, call history, messages, photos, files, or any other app’s data. CIDER does not collect device identifiers, advertising IDs, or any information that identifies you personally.
All data described above is stored in your device’s private app storage, inaccessible to other apps. Specifically:
Backups are disabled. CIDER explicitly disables Android’s automatic backup system. None of your trip history, settings, or logs are backed up to any cloud service, and none of this data survives if you uninstall the app.
CIDER sends data off your device in the following circumstances:
Weather lookups. If you enable weather alerts (on by default), CIDER sends your approximate location (rounded coordinates) to OpenWeatherMap, a third-party weather data provider, once at the start of a trip and periodically during long drives if conditions may have changed. This request does not include your name, any device identifier, or any other personal information. You can disable weather alerts at any time in Settings, which stops these requests entirely. OpenWeatherMap’s own privacy practices apply to this data once it leaves your device — see their policy at openweathermap.org.
Traffic lookups. If you enable traffic alerts (on by default), CIDER monitors your driving pattern on your device to detect signs of possible traffic congestion, using only your speed and movement — no network request is made for this step. Only if that on-device check suggests congestion does CIDER send your approximate location (rounded coordinates) to TomTom, a third-party traffic data provider, to confirm current road conditions before speaking an alert. This request does not include your name, any device identifier, or any other personal information. You can disable traffic alerts at any time in Settings, which stops these requests entirely. TomTom’s own privacy practices apply to this data once it leaves your device — see their policy at tomtom.com.
Voice recognition. When you respond to a spoken reminder, your voice is processed by your device’s speech recognition system (the recognition service configured on your Android device, commonly provided by Google). This is a system-level Android feature that CIDER relies on but does not control. CIDER itself never stores, logs, or transmits your voice audio or the words you say — it only receives a short recognized response (“yes,” “not now,” etc.) to act on. How your device’s speech recognizer itself handles that audio is governed by that service provider’s own privacy practices, not this policy.
CIDER also uses Google Play Services’ location functionality to determine your device’s position. This means location processing on your device involves Google’s location services, which are governed by Google’s own privacy policy in addition to this one.
CIDER does not use any analytics, advertising, or crash-reporting services. We do not know how many people use the app, how they use it, or anything else about app usage beyond what is described above.
CIDER’s codebase includes an optional diagnostic logging feature, used only in development and testing builds to help identify and fix bugs. This feature is not present in the version of CIDER available on the Google Play Store. In the Play Store version, no diagnostic log file is ever created, there is no logging toggle in Settings, and there is nothing to export. If this changes in a future release, this policy will be updated first, and the feature will remain off by default and require your explicit action to enable.
CIDER is not directed at children and is not intended for use by anyone under the age required to hold a driver’s license in their jurisdiction. We do not knowingly collect data from children.
If this policy changes, the “Last updated” date at the top will be revised. Continued use of CIDER after a change constitutes acceptance of the updated policy.
If you have questions about this policy or how CIDER handles data, contact:
Kartikeya Mudliyar kartikeyamudliyar@gmail.com