Where Does OwnTracks Store Data?
OwnTracks keeps location data in app-private storage with .otrc export files. Android and iOS flows.
Last updated
OwnTracks keeps everything in private app storage. Recorded locations, waypoints and settings never appear in a shared folder, on either phone OS. The package on Android is org.owntracks.android across Play and F-Droid builds.
The portable artifact is the export file. Configuration Management export writes a JSON .otrc file you can move, containing settings plus waypoints. Imports arrive by opening that file, by config URL, or by remote MQTT message. Location history itself flows to your own broker rather than a file.
Where OwnTracks stores this, by platform
App-private storage (exports as .otrc files)
Package org.owntracks.android. No user folder holds tracks. Export from Configuration Management to a .otrc JSON file. Waypoints travel inside it; live positions publish to your MQTT broker instead of files.
App sandbox (exports as .otrc files)
Same private model as Android. Import by opening the .otrc from Mail, Files or cloud storage, or via config URL. Recent builds need the URI config option enabled plus a confirm dialog.
Frequently asked questions
How do I move OwnTracks to a new phone?
Export configuration to an .otrc file on the old phone, then open that file on the new one to import settings and waypoints. Point it at the same MQTT broker afterwards. Location history already sits on the broker, not in the file.
Where are my recorded tracks stored?
On your MQTT broker and any recorder attached to it, not in phone folders. The app publishes positions; something else must subscribe and store them. Check the broker retention when old points vanish.
What is inside an .otrc file?
A JSON document with configuration plus waypoints, typed as configuration. It carries settings and places, never the full track history. Keep it private when regions inside reveal home or work.
Notice an outdated path? Let us know.