> you can be sure your data stays secure and private.
By using the Google Maps API you grant Google the rights to your data to use as they see fit. You cannot have private or secure data if you use the Google Maps API.
(edits: however, I think if you pay Google for the premium or business access to the Google Maps API, then Google does not claim their rights to your data)
creator of the Owntracks Android app here. I'm absolutely with you that you cannot have private and secure location data when using any Google services.
Indeed, Owntracks does use Google Maps and the Google Play Services location APIs and your location data is likely sent to Google when using the app and we're very clear that this is the case.
However, when using Android, it's almost impossible to not send any personal data to Google when using an Android phone (or to Apple if you're using an iPhone). Hence, we decided to not use any third party location or APIs and for several reasons:
1) Google likely has your location data anyway because you're using their operating system
2) I personally would trust my data to Google than any third party that's not that closely monitored by others. We tried to integrate Mapbox as Mapping provider for the 0.5.x release until they likewise started gathering user data. Thus the next version switches back to Google Maps.
3) The offered location APIs are much easier on the battery life than any third party solution
4) We develop Owntracks in our spare time and receive no funding whatsoever. Hence, the time that we can invest into the integration of other Maps or location providers is very limited.
Besides that, Owntracks does allow you to store your location data on your own infrastructure. You are free to choose whatever you want with that data and you're not trusting a third party (besides Google) with your data.
Personally I think that this isn't a perfect solution, but it is as good as it gets for the majority of smartphones.
If that isn't good enough with you that's fine and I totally understand that. In that case, simply don't use the app and build something that you can trust entirely. E.g. some people from our development team are happily tracking their cars with a hardware appliance that is Owntracks compatible [1]
Would prefer it if it used OSM anyway, which I can also run my own version of if I am little twisted.
Basically, with a bit of work, you could produce a completely-self-hosted solution where there are no calls going out anywhere to anything you don't host yourself.
That's progress to my mind. Just needs a little more work to get there. If I didn't have family over this weekend...
That's an excellent documentation, in my opinion. Extensive and complete.
As an example: It doesn't just say: 'Can use MQTT.'. Instead it details the usage of MQTT by the appplication and even how to set up an MQTT service on a Rasperry Pi.
I've used it a bit on Android. It's important to note that OwnTracks only takes care of publishing your location to an MQTT server (and also subscribing to and displaying other published locations). If you want to save historical location data, and display it on a map, you'll need to hook up some more software, likely this: https://github.com/owntracks/recorder
As far as the Android app goes, I had no complaints. I didn't notice any significant battery drain issues or anything like that.
Fellow traveller here - going to try it in my solo bike tour from Lisbon to Istanbul that starts in a few days, let me know if there is any aspect of the software that you want reviewed
Have been using Where have I been for the past year and it works flawlessly. Most important is that I can export all locations as CSV which I convert to KML and all is good.
Will give OwnTracks a try but privacy wise Where Have I Been also is phone only.
The Google Maps timeline doesn't have an API, so while you can see what data Google have there's no way to get it out and make use of it in other ways.
It's trivial (~2 lines) to write a script that will get your location every minute and HTTP POST it to the OwnTracks recorder, if I'm understanding the docs correctly.
[+] [-] mnutt|10 years ago|reply
https://apps.sandstorm.io/app/cjv3p2a970vrm729x9x0v54k0nff6x...
[+] [-] jsilence|10 years ago|reply
"Step 2: Configure the app
Tap the i icon in the top left and tap "Settings". In the URL field, enter:"
But there is no "i" icon and no Settings tap. There is a menu button and in the preferences I can choose a mode between public, hosted and private.
I tried to use the supplied URL in the Host setting, but the Owntracks app complains that the settings are incomplete.
Any help appreciated.
[+] [-] ocdtrekkie|10 years ago|reply
[+] [-] chippy|10 years ago|reply
> you can be sure your data stays secure and private.
By using the Google Maps API you grant Google the rights to your data to use as they see fit. You cannot have private or secure data if you use the Google Maps API.
(edits: however, I think if you pay Google for the premium or business access to the Google Maps API, then Google does not claim their rights to your data)
[+] [-] binarybucks|10 years ago|reply
creator of the Owntracks Android app here. I'm absolutely with you that you cannot have private and secure location data when using any Google services.
Indeed, Owntracks does use Google Maps and the Google Play Services location APIs and your location data is likely sent to Google when using the app and we're very clear that this is the case.
However, when using Android, it's almost impossible to not send any personal data to Google when using an Android phone (or to Apple if you're using an iPhone). Hence, we decided to not use any third party location or APIs and for several reasons:
1) Google likely has your location data anyway because you're using their operating system 2) I personally would trust my data to Google than any third party that's not that closely monitored by others. We tried to integrate Mapbox as Mapping provider for the 0.5.x release until they likewise started gathering user data. Thus the next version switches back to Google Maps. 3) The offered location APIs are much easier on the battery life than any third party solution 4) We develop Owntracks in our spare time and receive no funding whatsoever. Hence, the time that we can invest into the integration of other Maps or location providers is very limited.
Besides that, Owntracks does allow you to store your location data on your own infrastructure. You are free to choose whatever you want with that data and you're not trusting a third party (besides Google) with your data.
Personally I think that this isn't a perfect solution, but it is as good as it gets for the majority of smartphones. If that isn't good enough with you that's fine and I totally understand that. In that case, simply don't use the app and build something that you can trust entirely. E.g. some people from our development team are happily tracking their cars with a hardware appliance that is Owntracks compatible [1]
[1] jpmens.net/2014/06/14/owntracks-in-a-vehicle-choral-greenwich
[+] [-] PaulRobinson|10 years ago|reply
Basically, with a bit of work, you could produce a completely-self-hosted solution where there are no calls going out anywhere to anything you don't host yourself.
That's progress to my mind. Just needs a little more work to get there. If I didn't have family over this weekend...
[+] [-] cstuder|10 years ago|reply
As an example: It doesn't just say: 'Can use MQTT.'. Instead it details the usage of MQTT by the appplication and even how to set up an MQTT service on a Rasperry Pi.
It details common usage scenarios.
[+] [-] vosper|10 years ago|reply
Does anyone have any experience using OwnTracks?
[+] [-] beardicus|10 years ago|reply
As far as the Android app goes, I had no complaints. I didn't notice any significant battery drain issues or anything like that.
[+] [-] tcooks|10 years ago|reply
[+] [-] vespakoen|10 years ago|reply
[+] [-] andrenotgiant|10 years ago|reply
I logged the process I used to get it all setup here: https://www.digitalocean.com/community/questions/how-to-setu...
[+] [-] moontear|10 years ago|reply
Will give OwnTracks a try but privacy wise Where Have I Been also is phone only.
[+] [-] StavrosK|10 years ago|reply
[+] [-] JetSpiegel|10 years ago|reply
[+] [-] 89vision|10 years ago|reply
[+] [-] brudgers|10 years ago|reply
[+] [-] h-h|10 years ago|reply
[+] [-] chipperyman573|10 years ago|reply
https://www.google.com/maps/timeline
[+] [-] conradev|10 years ago|reply
> OwnTracks is open-source and uses open protocols for communication so you can be sure your data stays secure and private.
I think OwnTracks was named because you "own" all of the data.
[+] [-] jon-wood|10 years ago|reply
[+] [-] alainchabat|10 years ago|reply
https://community.owntracks.org
[+] [-] nostalgiac|10 years ago|reply
[+] [-] binarybucks|10 years ago|reply
[+] [-] ekianjo|10 years ago|reply
[+] [-] StavrosK|10 years ago|reply
[+] [-] nagarjun|10 years ago|reply
[+] [-] nickysielicki|10 years ago|reply
[+] [-] vosper|10 years ago|reply
[+] [-] guruz|10 years ago|reply
[+] [-] Jack5500|10 years ago|reply