Your data is absolutely private
Trilobite Solutions understands that the privacy of your data is paramount. Australian Geology Travel Maps and Ontario prospector writes trails and locations data to your phone/tablet only. None of your data is copied behind the scenes to the internet. None of your data is visible to Trilobite Solutions. The only way for anyone (including Trilobite Solutions) to access your marked locations and trails is to have your device in their hands, or for you to share your data (as KML, CSV or GeoJSON) and send it to them.
Back up your data
As mentioned above, your locations and trails are only stored in one place – on your phone/tablet. This is not a safe long-term storage area. You may lose or damage your phone, it might malfunction, or you may unwittingly uninstall your Trilobite app, and consequently lose all of your marked locations and trails. Regularly share your locations and trails as CSV and put them into an email sent to yourself. If you do not trust your email provider, then you can instead share the CSV with DropBox or some other internet-based storage system, and save the .csv file there.
To share (ie. export) trails in a particular area, zoom into that area tap on one of the trails then on the popup. When the details are shown for that trail, scroll down to the option to share all the trails in the current map view to CSV, choose to share using your email app and save into an email sent to yourself. Now you have a CSV file permanently stored on the internet. Likewise for locations.
Restore your data
At any time in the future that you lose your phone or lose your data for some other reason, you can install Australian Geology Travel Maps or Ontario prospector on a new phone or tablet, and import your .csv files by opening up your saved emails and tapping on the attached CSV file. See the latter part of the ‘Import trails & locations from Google Earth‘ video for details – https://trilobite.solutions/maps/videos/
Larger amounts of trails data
If you have a large amount of trails data (eg. 1,000’s of kms) you can eventually slow down the app because it holds all of the trails in memory. In this case, back up your trails as geojson. If/when the .geojson file is later imported, the trails will be saved to a data layer – this is more efficient with memory.