Gaugely, the vehicle-dashboard app by Daniel Velez · Last updated 24 August 2026
This page explains how to delete data from Gaugely — either your whole account and everything in it, or parts of your data while keeping your account. It also says exactly what is destroyed, what is kept, and for how long.
Gaugely is developed and operated by Daniel Velez. Contact: daniel.f.velez@gmail.com.
Gaugely works without an account. If you never created one, there is nothing on our server to delete — everything the app made is on your phone, and uninstalling removes it.
This is the fastest route. It runs immediately and you do not have to wait for us.
Deletion runs at once, in a single database transaction: either all of it happens or none of it does. It cannot be undone. On success the app says “Account deleted. Your data on this phone is untouched.” If it fails, nothing was deleted and you are still signed in — the app tells you so rather than pretending it worked.
If you cannot use the app — you no longer have the phone, or you cannot sign in — email daniel.f.velez@gmail.com from the email address your account uses and ask us to delete your account. Sending it from the account's own address is how we confirm the request is yours.
We will action it within 30 days. It performs the same deletion described in section 4.
If you also want your community contributions removed rather than just de-attributed (see section 5), say so in the same email.
You do not have to delete your account to remove data. Each of these works on its own.
Delete a trip, a fuel fill-up or a vehicle in the app, the way you normally would. If you are signed in, the next sync pushes that deletion: the record's stored contents on the server are overwritten with an empty object and the record is marked deleted. That marker is what makes the record disappear from your other devices, and it is itself deleted when your account is deleted.
Your settings, themes, metric overrides, PID lists and CAN lists sync as whole collections rather than as individually deletable records: clearing or changing them in the app overwrites the stored copy on the next sync.
Being straight about a limitation: the app currently has no way to delete a private vehicle photo from the server on its own. There is no delete endpoint for them, and if you remove the local file, the next sync downloads the server's copy back to your phone. Your photos are removed when your account is deleted (section 4), or you can email daniel.f.velez@gmail.com and ask us to remove a specific vehicle's photos from your account. The same applies to the photos of a vehicle you deleted — deleting the vehicle does not remove its uploaded photos from our storage.
Switch analytics off in the app's Settings. It calls the analytics SDK's own disable function, and no further events are sent from that moment. The app stays fully usable.
Events already collected cannot be deleted for you individually, and we will not pretend otherwise. They are never linked to your identity — we never attach an account, email or profile to an analytics event — which is exactly why there is no way to find “your” events and remove them. They are deleted when they reach the 12-month retention limit. See section 3 of the privacy policy.
You can have your community contributions or a photo you contributed to the public pool withdrawn without deleting your account. Email daniel.f.velez@gmail.com from your account's address, saying which contributions or which photo, and we will remove them.
Uninstall the app. That removes all of the on-device data in section 6, including cached photos, recordings and exports. It does not touch your account or anything synced to the server — use section 1 or 2 for that.
Signing out is not deletion: it removes the session token from the device and leaves your account and its data on the server.
All of the following is destroyed on our server, in one transaction:
Photos you uploaded for yourself are not database rows — they are files in our object storage, in a folder named after your account identifier and readable only by your account. Once the account is deleted, the server deletes those files.
One honest detail: that file deletion happens after the account is gone, and it is best-effort. If the storage system errors at that moment, your account and every record above are still permanently deleted, but the image bytes can survive as orphans under an account identifier that no longer exists — unreachable through the app and attached to nothing. If you want that confirmed, email daniel.f.velez@gmail.com and we will check and remove them by hand.
If you turned on community contributions, the vehicle data you contributed stays in the shared database. What is removed is the link between that data and you:
Why: those records are what makes other people's vehicles work in the app. Deleting them would silently break the shared vehicle definitions everyone else depends on, and the public photos were contributed under a licence you granted. So the vehicle data remains and the person does not. A contribution carries no full VIN, no wall-clock time and no location, so what is left describes a model of vehicle, not you.
If you want those records gone as well, you can ask. Email daniel.f.velez@gmail.com — either in your deletion request or on its own — saying you want the records attributed to your account removed, and we will remove them rather than only de-attribute them.
Most of what Gaugely produces never leaves your device, so it is not ours to delete. That includes your live vehicle readings, your vehicle profiles, gauge layouts, presets, themes and app settings, your trip history and fuel log, your PID and CAN definitions, your recordings, probe logs and exports, and the photos you attached to a vehicle.
Deleting your account leaves all of it exactly where it is on the phone. Uninstalling the app removes it. The full statement is in section 2 of the privacy policy.
Questions about any of this: daniel.f.velez@gmail.com. Full details of what Gaugely collects are in the privacy policy.
Gaugely · Daniel Velez · Home · Privacy policy