Data Management
Manage your location database from the Data Management screen.
Actions
| Action | Description |
|---|---|
| Sync Now | Manually flush the queue and upload pending locations |
| Clear Sent History | Remove locations that have already been synced |
| Clear Queue | Remove unsent locations from the upload queue |
| Delete Older Than X Days | Clean up old data past a specified age |
| Vacuum Database | Reclaim disk space after deletions |
| Export Locations | Export location history - see Data Export |
| Import Locations | Merge external files into your history - see Data Import |
In offline mode, sync-related actions (Sync Now, Clear Sent History, Clear Queue) are hidden since no queue is used. A Delete All Locations action is available instead. Data export remains fully available - see Data Export.
For a full archive of locations, settings and credentials in a single password-encrypted file, use Settings → Backup & Restore - see Backup & Restore.
Deleting from Location History
The actions above work on the whole database. To remove specific recordings, use the Location History screen.
Trips
From the Trips tab, long-press a trip card to enter selection mode, add any other trips you want to remove, then tap the trash icon in the selection header. You'll be asked to confirm before the underlying location points are permanently deleted from the device.
Single-trip delete is also available from the Trip Detail screen via the trash icon in the header.
To correct how points are grouped into trips rather than remove them, see Editing Trips.
Single points
A stray fix can land far from where you actually were, which drags the track and the day's distance with it. On the Map tab, tap the point to open its popup, check the time and accuracy to make sure it is the one you mean, then tap the trash icon next to the close button. You'll be asked to confirm.
Only that one point is removed, so the rest of the trip stays intact. If the point had not synced yet, its pending upload is dropped with it.
The same popup carries a split icon, which starts a new trip at that point instead of removing it - see Editing Trips.
Deleting locally does not remove anything already uploaded to your server.
Imported locations and the queue
Locations brought in via Data Import are marked as already synced by default, so they do not show up in the queue counter and don't get re-uploaded to your backend. If you used the Import + Queue for Sync button on the import dialog instead (the "migration" path), the imported rows do land in the queue and the next sync drains them - the counters here will reflect that until they finish uploading.
Storage Reference
- ~200 bytes per location
- ~2 MB per 10,000 locations