Pre-Trip Check — Privacy Policy
Last updated: 2026-10-03
This privacy policy applies to the mobile app "Pre-Trip Check" on Android and iOS:
- Google Play: package com.simonj.vehiclecheck, developer "Global Utility App Maker"
- Apple App Store: bundle ID com.simonj.vehiclecheck, seller "Kyu-Hee Jang"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Pre-Trip Check does not require an account, and we do not sell personal information. You walk around a vehicle with a checklist, mark items, record defects with photos, sign the check, and can make a PDF report. Your vehicles, checks and photos are kept in the app's storage on your device. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
CAMERA, PHOTOS, AND NOTIFICATIONS
The app asks for camera permission only when you tap to take a photo of a checklist item, a defect, a damage mark or a fix. You can instead choose an existing photo; the system photo picker gives the app only the photo you pick and needs no library permission. Each photo is reduced (up to 1600 pixels on the long side, JPEG) and copied into the app's own folder; the app does not add it to your photo library and does not upload it. If you decline the camera, the app shows how to allow it in Settings, and you can still pick existing photos and use the rest of the app.
Notification permission is asked only while the optional daily check reminder in Reminders is on: when you switch it on or change its time, or when the app starts with the reminder on and permission has not been given yet. The reminder is a local notification scheduled on your device at the time you choose. If you decline, no reminder is set.
INFORMATION STORED ON YOUR DEVICE
- Vehicles: name (up to 40 characters), plate (up to 20), type, odometer unit and last odometer reading, and up to 50 maintenance entries per vehicle (title, due date or reading, done date).
- Checks (drafts are saved as you go): vehicle name and plate, the checklist used, each item's result, numbers, text and notes, up to 6 photos per item, the driver name and the location you type (the app does not read your device location), odometer, start and finish times, your drawn signature, items you confirmed in bulk, damage marks on the vehicle outline (up to 60, each with a note and photos), and open defects carried over from earlier checks.
- Defects: item, note, severity, photos, status, the checks that reported it, and fix details (date, action, note, photos).
- Your own checklists (up to 30 sections, 60 items per section, 300 items).
- Settings: the reminder switch and time, and a default driver name.
There is no fixed limit on the number of vehicles, checks or defects. The app also keeps a list of deleted record IDs with their deletion times, without a limit, so that an older backup cannot silently bring deleted records back.
The app may also store basic operating information such as the reminder schedule state, cached advertising settings, and a cached More Apps list.
The developer does not run a server that receives your checks. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not upload your vehicles, checks, signatures or photos. When you open More Apps, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, screen views, opening the menu and its Templates, Backup and Reminders pages, tapping the menu's rate, privacy policy and More Apps entries, review-prompt outcomes, ad revenue events (ad format, value, currency and precision), whether the iOS tracking prompt is shown (with the reason, the tracking status and the consent status), app version, device type, and app-instance identifiers. When a check is finished, an event records only that a check was finished; it does not include vehicle names, plates, driver names, locations, notes, signatures or photos.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob. AdMob may also request ads from the InMobi mediation network. Google and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission.
PERMISSIONS AND ADVERTISING CHOICES
The feature permissions the app requests are the camera and, if you turn on the reminder, notifications, as described above. It does not request location, microphone, contacts, Bluetooth, or health data.
When the app starts, Google's consent message (UMP) is checked first. Where it is required (for example in the EEA and UK), personalized advertising stays off unless your choice allows it. On iOS, Apple's App Tracking Transparency prompt is shown only after that step and only if you have not answered it before; it is normally skipped when you have declined personalized ads in Google's consent message where EU-style consent rules apply (such as the EEA and UK), but it may still appear if the app cannot read the result of that message. If tracking is not allowed, the IDFA is not available to the app or its ad partners. If the consent message cannot be loaded, the app still requests non-personalized ads, the iOS tracking prompt may still appear, and personalized advertising stays off. The app works whatever you choose.
You can change iOS tracking, camera and notification permissions in Settings. Where Google requires it, the app menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice.
STORAGE AND YOUR CONTROL
You can delete a finished check from its detail screen in History (with its signature and its photos, except photos that a defect record still uses, which stay with that defect), discard a draft check, remove single photos and damage marks, delete a vehicle on its Vehicle screen (with its maintenance entries and defects and the defects' repair photos; finished checks stay in History, and defect photos taken during a check stay with that check, or stay in the app's folder if that check was already deleted), and delete your own checklists in Templates. You can also clear the app's data on Android or delete the app. Local data may be included in an Apple, Google, or device backup depending on your backup settings; uninstalling normally removes the active copy but may not remove an older backup.
Files you create leave the app only when you choose: a PDF report (with the check details, signature and photos) is shared or printed through the system sheets, a CSV of your History is shared through the share sheet, and the Backup page saves backup files (all records, photos and deletion records) to a folder you pick on Android or through the share sheet. PDF and CSV files are written to the app's cache and may stay there until the system clears it; backup files the app writes to its cache are removed when you leave the Backup page. The app does not delete copies you saved or sent elsewhere. Restore reads backup files you pick; the system file picker places a copy of each picked file in the app's cache, which may stay there until the system clears it.
Because we do not receive your records, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your records and photos are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a passcode. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
A check in this app is the driver's own record. It is not a substitute for any legally required inspection, and it does not certify roadworthiness or legal compliance. Follow your local rules, your employer's procedures and the vehicle maker's instructions, and do not drive a vehicle with a defect that affects safety.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com