Hey, welcome to the docs
A quick intro to Drup Trails — what it is, why we built it differently, and how to get your first tracker running.
So… what is Drup Trails?
Drup Trails is a friendly home for your trackers — phones or other devices you trust — so you can see where they have been on a map, keep a private trail, or share it with people you actually invited (think family or a small team). It is meant to feel open and straightforward: you know where the data lives and who can see it.
Unlike big-tech timelines that silently absorb your location into an ad profile, Drup Trails keeps your trail in a smaller, clearer box: your data, visible only to teams you chose, for as long as you decided.
Why not just use Google for that?
Google's location history is handy — no shade on wanting maps that "just work." The trade-off is you are continuously feeding very rich location data into one company's ecosystem. That trail can power their products, personalisation, and whatever their terms and business priorities look like over time. You do not get much say in the big picture; you mostly get a toggle and a privacy policy.
With Drup Trails, the idea is different: your path is not automatically part of a global ad profile. It is yours (or your team's) to use on your terms — a smaller, clearer box around who sees what. We are not claiming we are "more secure than Google" in every abstract sense; we are saying the model is simpler — less "upload humanity to one dashboard," more "this is your diary, on your rails."
Where to start
The OwnTracks app
What OwnTracks does and why Drup Trails is built around it.
Configure OwnTracks
Create a tracker and import a ready-to-use config in one tap.
Trackers & teams
The two core concepts and how they work together.
Bottom line: if you want location memories without defaulting to "send it all upstream," you are in the right place. Poke around the rest of the docs as we grow them — and thanks for stopping by.