Legal
Privacy policy
Effective 21 August 2026
1. What this policy covers
This policy explains how Trip Reaper handles information when you browse the public website, create a personal or enterprise account, use road-journal features, connect an installed GPS device, or contact the team.
2. Account information
Trip Reaper stores your name, email, securely hashed local password, preferences, sessions, and revocable mobile access tokens. Enterprise accounts also retain the minimum encrypted Platform and Gateway connection information needed to verify eligibility and reach the assigned environment. One-time enterprise codes are fingerprinted and cannot be recovered from the database.
3. Vehicle and journey information
Vehicle, maintenance, reminder, refueling, expense, planned-route, GPS journey, and installed-device assignment records are sent server-to-server through Gateway to the Transport service assigned to your account. The browser and mobile client do not receive Gateway credentials. Journey records may include timestamps, start and end coordinates, speed, distance, accuracy, and—when you enable detailed map capture—ordered route points.
4. Your location choices
Location is used only after device or browser permission and an explicit tracking action. You can disable detailed journey-map capture for future journeys in your profile. Doing so keeps summary information and endpoints but omits the complete recorded trail. Installed vehicle trackers may provide location independently of phone GPS when that integration is active.
5. Contact messages and public pages
Contact submissions store the name, email, subject, message, status, and timestamps needed for the Trip Reaper administrator to review and respond. Trip ideas are public editorial content and do not contain rider records.
6. Maps, analytics, and service providers
If enabled by the administrator, Google Maps may process route-planning requests and browser location supplied to the planner. Google Analytics may process page-view information on public, authentication, and rider pages, but not administration pages. Their handling is governed by their own terms and privacy policies.
7. Retention and security
Passwords are hashed; sensitive connection and mail credentials are encrypted at rest. Access is scoped by authenticated account and owner identity. Closing a rider account blocks access. Contact messages remain until an administrator deletes them.
8. Your choices
You can update your profile, password, distance units, reminder syncing, and detailed-map preference. You can close your account from your profile and contact the Trip Reaper team about access, correction, or deletion requests. Some records may need to be retained when required for security or legal obligations.
9. Contact
For privacy questions, use the contact form and avoid including passwords, tokens, registration codes, or precise live location.