Trips — Privacy Policy
Last updated: 17 November 2026
This policy explains how Trips (com.oguzhanyucel.trips) handles personal data. Trips is a single app with two parts:
- Car app — runs in cars with Google built-in (Android Automotive OS); records trips and shows live values and a trip summary on the car display.
- Phone/tablet app — reads the trips recorded by the car app from your Google Drive and shows them with charts, maps and analysis.
Summary: Trips records your trips (including a GPS track) in your car. If you connect your own Google account in the car, these records are uploaded only to your own Google Drive, and Trips on your phone reads them from there. The developer runs no server; nobody, including the developer, can see your data. There is no advertising, analytics or crash reporting.
Data collected by the car app
- Location: precise location (latitude, longitude), altitude, GPS speed and accuracy. Distance, route and elevation can only be calculated from location, so the
ACCESS_FINE_LOCATIONpermission is requested. - Background location: if you allow it (
ACCESS_BACKGROUND_LOCATION), Trips records trips when the car starts, without you opening the app; location is collected even when the app is closed or not in use. This is explained in the app before the permission is requested. The permission is optional; without it, trips are recorded only while the app is open. - Vehicle data: speed, instantaneous power and energy use, battery level and capacity, remaining range, gear, ignition and parking brake state, outside temperature, wheel tick counter — read from the vehicle's own systems.
- Vehicle details and vehicle ID: make, model, model year, battery capacity and the infotainment unit's model; plus, to keep trips apart when you use the same Google account in more than one car, a Trips-specific vehicle ID derived one-way from the device's Android ID. The raw device ID never leaves your car. This information goes, together with your trips, only to your own Drive.
- Google account (optional): if you connect one, your email address (to show which account is connected) and the access tokens issued by Google.
- Diagnostic log: a small file recording the app's own state (for example when a trip started or ended, whether an upload succeeded). It contains no location, stays in the car and is never sent anywhere.
While a trip is being recorded, a "Recording the trip" notification is shown (if you allowed notifications).
Data used by the phone/tablet app
- Google account: the email address of the account you sign in with and the access granted by Google. The access token is kept by Google Play services; the app writes no token to disk.
- Trips: trip summaries and GPS tracks that the car app uploaded to your Drive are downloaded to the phone for display and kept in the app's private storage. Notes you add, such as place names and names you give your cars, are stored only on the phone.
- Maps: map tiles are downloaded from OpenStreetMap servers. These requests reveal your device's IP address and the map area being viewed to OpenStreetMap; no trip data is sent. See the OSMF privacy policy.
- The phone app never writes to Drive; it only reads. App data is excluded from Android backup.
How data is used
Data is used solely to give you information about your own trips: distance, duration, energy consumption, regenerative braking, elevation, range gauge accuracy, performance measurements, and their charts, maps and statistics.
Uploading to Google Drive
- Uploads happen only once you connect your own Google account in the car. If you do not, no data leaves the car.
- Once connected, each trip's summary and GPS track are uploaded automatically when the trip ends, to a "Trips" folder in your own Drive.
- Trips requests only the
drive.filescope: it can see only the files Trips created in your Drive, and has no access to your other files. - Data goes directly from your car to Google and from Google to your phone. There is no developer server in between; the developer cannot access your data.
Permissions
| Permission | Where | Why |
|---|---|---|
| Location (precise, approximate) | car | distance, route, elevation |
| Background location | car | recording when the car starts, without opening the app (optional) |
| Car energy, speed, powertrain, info, exterior environment, display units | car | consumption, battery, range, trip start/end detection |
| Foreground service (location) | car | keeping the recording alive while driving |
| Run at startup | car | being ready to record when the car starts |
| Notifications | car | "Recording the trip" notification (optional) |
| Internet, network state | car, phone | Google sign-in, uploading to and reading from your own Drive, map tiles |
Storage
- In the car: trip summaries and GPS tracks are kept in private storage, inaccessible to other apps (up to the last 300 trips; older ones are deleted automatically). The Google access token is stored encrypted with the car's hardware-backed key store (Android Keystore).
- On the phone: downloaded trips and tracks are in the app's private storage.
- In Drive: records stay in your account until you delete them.
- Uninstalling the app deletes all Trips data on that device.
Purchases
- Trips Pro (subscription or lifetime) is purchased through Google Play. Your payment details never reach the developer; Google Play's own privacy policy applies.
- To know whether Pro is active, the phone app asks Google Play for your purchases on the device. This information stays on the phone and is never sent to the developer or any other server.
- Purchase and subscription terms: Terms of Use.
Google API Services User Data Policy
Trips' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used for advertising, not sold, not transferred to third parties, and not used to train AI models.
Website and email
This website (TripsEVLog.app) uses no cookies, analytics or tracking tools and loads no fonts or scripts from other sites. It is hosted on the infrastructure of Cloudflare, Inc. (USA). To deliver pages and prevent abuse, Cloudflare processes technical connection data such as your IP address, browser information and the time of the request. The developer keeps no separate visitor log. The Cloudflare dashboard mostly shows the developer aggregate statistics such as request counts; security events and email forwarding logs may show the related IP address or sender address.
Emails you send to support@tripsevlog.app are forwarded by Cloudflare Email Routing to the developer's Gmail (Google) account. Your address and message are used only to answer your request, and the correspondence is kept in Gmail. Cloudflare's and Google's servers may be outside Türkiye; see the Cloudflare Privacy Policy and the Google Privacy Policy.
Sharing
Trips contains no advertising networks, analytics tools, crash reporting services, or similar third-party SDKs. Data is never sold, rented, or shared. The only external connections are the Google account you connect and, on the phone, Google Play for purchases and OpenStreetMap map tiles; see the KVKK section. For the website and email, see the section above.
Deleting your data and removing access
- In the car, inside the app: Trips → Settings → "Delete data".
- Delete from car: deletes that car's trips, GPS tracks, records, upload queue and diagnostic log. Records in Google Drive are not touched.
- Delete from car and Drive: first permanently deletes that car's trip files, GPS tracks and vehicle profile from your Google Drive, then the records in the car. Other cars on the same account keep their records.
- Disconnect in the car: Trips → Settings → Google account → "Disconnect". The token is deleted from the car and revoked at Google.
- Sign out on the phone: Trips → Settings → Google account → "Sign out". Access is revoked and all of that account's data on the phone is deleted.
- From Google: remove "Trips" at myaccount.google.com/permissions.
- Records in Drive: they are entirely in your Drive; besides "Delete data" in the car, you can delete the "Trips" folder to remove them all.
- Uninstalling: uninstalling the app or clearing its data in the device settings also deletes all Trips records on that device.
- Location: revoke the location permission (including background) in the car's settings at any time.
Because the developer holds none of your data, there is no server record to delete; you are still welcome to write with any questions.
Rights under Turkish data protection law (KVKK)
The data controller under Law No. 6698 on the Protection of Personal Data (KVKK) is Oğuzhan Yücel (individual developer), support@tripsevlog.app. Data is collected automatically and electronically when you use the app (the car's location receiver and vehicle systems, your connected Google account and Drive, Google Play for the Pro status, and Cloudflare when you visit the website or send an email). The legal basis is the performance of the contract for using the app (KVKK Art. 5(2)(c)); for the on-device diagnostic log, the developer's legitimate interest (Art. 5(2)(f)); for answering your requests, legal obligation (Art. 5(2)(ç)).
Data reaches Google (sign-in, your own Drive, Google Play, and the developer's Gmail for emails; servers may be outside Türkiye), the OpenStreetMap Foundation in the United Kingdom for map tiles (IP address and map area only) and Cloudflare, Inc. in the USA for the website and email forwarding (IP address and connection data). These connections are required for the app's and the website's core functions. The app's connections are made directly from your device; apart from your own emails, the developer transfers no data to anyone.
Under KVKK Art. 11 you may learn whether your data is processed and request information about it, learn the purpose and the third parties it is transferred to in Türkiye or abroad, request correction, deletion or destruction and notification of these to third parties, object to a result against you arising solely from automated analysis, and claim compensation for damage caused by unlawful processing. Most deletion can be done immediately in the app (see above). Other requests can be sent by email; they are answered free of charge within 30 days (Art. 13). If a request is refused, the answer is insufficient or no answer is given in time, you may complain to the Personal Data Protection Board (Art. 14).
Children's privacy
Trips is not directed at children and does not knowingly collect data from them.
Changes to this policy
If this policy is updated, this page will be revised with a new "last updated" date.
Contact
Oğuzhan Yücel · support@tripsevlog.app