Repository navigation
23. Device Identity and Sharing Privacy
The intent is to reduce the personal information a platform needs to hold. Without website registration, there is no required account profile containing a real name, phone number or email. Device-held keys provide proof of authorship without requiring that personal profile. Local contacts, conversations and unshared tracks do not need to become one provider's complete activity history.
This supports pseudonymous use: a key can identify an author without registering their civil identity. It does not make a persistent public identity unlinkable.
Trail Mate uses a personally held device identity for author operations. A connected device proves possession and signs authorized Geocaching or trail content. The browser is an editing tool; it does not issue a website account that owns your identity.
Reticulum gateways provide network access. Content directories index and serve shared publications. They may be operated independently and on different nodes. Reaching a directory does not require making its machine your account provider.
Author signatures let recipients check publication authorship independently of a directory's display text. Directory proofs describe a directory result; they are not a guarantee that every other directory stores the same content or that a route is physically safe.
| Information | Visibility in the ordinary workflow |
|---|---|
| Device private identity material | Held by the device; ordinary author operations use signatures. Explicit identity backups are sensitive. |
| Unpublished browser drafts | Stored in the current browser until exported or published. |
| Unshared device recordings | Stored on the device/media; connecting USB lets the authorized tool read supported records. |
| Published KML, coordinates, time and metadata | Available to the selected directory and recipients of the public content. |
| Public author key and publication history | Can link publications made under the same author identity. |
| Gateway connection metadata | Observable to the gateway or network parties that provide that connection. |
| External map requests | Observable to the selected map provider. |
Independent operators and portable files reduce the need to give one platform your entire private history. They do not prevent someone from saving or analysing data you intentionally publish. A public route may reveal a home, regular starting point or timing pattern if you include that information.
Check the route, waypoints, recording times, images, descriptions and embedded KML metadata. Publish only what you intend to disclose. Keep a private original if you create a public edited copy. Changing website language or RF protocol does not create a new author identity or make the old public history anonymous.
Archiving records a new publication state and can remove the item from ordinary active results. It cannot remotely erase copies or past versions already held by another directory or recipient.
Keep backups protected and retain recovery information you need. Someone who obtains usable private identity material can act as that author. A lost device without a usable backup may mean losing the ability to maintain its published content. These facts apply even though there is no central account login.
Trail Mate's privacy benefit is control over identity, local records and the choice of sharing relationships. Its documentation does not promise that no platform can ever learn a public route or infer behaviour from public data.
English
- Home
- 0. Why This Exists
- 1. Quick Start
- 2. Supported Hardware
- 3. Installation & Flashing
- 3.5 Configuration Guide
- 3.6 Settings Backup and Restore
- 3.7 SD-Editable Working Configuration (TMS)
- 4. Protocols & Data
- 4.1 Reticulum, LXMF and RNode Bridge
- 4.1.1 Reticulum Settings
- 5. Offline Maps
- 6. Trail Mate Center
- 6.1 Creating a Map Pack with Center
- 6.2 TMAP Maps and Terrain
- 6.3 Outdoor Navigation and Elevation Profiles
- 6.4 TMAP SDK and Resource Budgets
- 6.5 Persistent Routes and Viewport Reads
- 7. Team Features
- 8. UI Overview
- 9. Build from Source
- 10. Codebase Overview
- 11. Architecture
- 12. Design Decisions
- 13. FAQ
- 14. Troubleshooting
- 15. Logging and Debugging
- 16. Roadmap
- 17. Contributing
- 18. License and Third-Party
- 19.-GPS-Setting-Guide
- 20. Geocaching Developer Guide
- 20.1 Geocaching Wire Format and Signed Records
- 20.2 Geocaching Discovery and Directory Operations
- 20.3 Geocaching Integration Examples and Conformance
- 20.4 Geocaching GPX and Offline Storage
- 20.5 Geocaching Directory Deployment and Verification
- 21. Trails and Decentralized Sharing
- 22. Web Device Management
- 23. Device Identity and Sharing Privacy
- 24. Offline Navigation and Map Controls
- 25. Music, Widgets and Daily Controls