Installed trackers and mobile connectivity

Tracking and connectivity notice updated: 18 September 2026.

Tracking data and its purpose

When a compatible tracker is connected, we process its assigned device identifier (such as IMEI), model and vehicle/account association, together with received locations, timestamps and available journey readings such as speed and distance. We use these data to receive and associate device reports, show vehicle location and journey history, calculate statistics and support the tracking functions you use. Vehicle sharing and organization permissions determine which authorized users can view the records.

Mobile operators and equipment providers

Your SIM or connectivity provider may process subscriber and SIM details, network and connection metadata, network-derived location and usage or billing records to supply its own services. A device manufacturer or external tracking provider may also process data if you use its connected services. Their processing follows their own privacy notices and applicable obligations. Review those notices as well as ours when selecting equipment or connectivity. Trip Reaper remains responsible for the data processing described in this policy.

Independent trackers and your controls

Installed trackers operate independently of phone location permissions. Closing or uninstalling the app, disabling phone GPS or stopping a phone-recorded journey does not necessarily stop a vehicle tracker. Use the vehicle's device controls to pause or remove its Trip Reaper integration, and turn off or reconfigure the device to stop its own transmissions. This does not cancel its mobile contract or erase previously stored records. The access, correction, retention and deletion provisions of this policy also apply to account-linked tracking data.

Trip Reaper provides data collection, statistics and tracking software; devices, SIM cards and operator services are separately obtained and paid for. Trip Reaper does not provide GPS tracker installation services; you arrange installation directly with a separate company. Review its privacy notice when providing contact or vehicle details. Mobile data and roaming charges may apply even during background use. See the equipment and connectivity terms for details.

Equipment and connectivity terms

Trip Reaper and Trip Nav mobile apps

Mobile privacy policy updated: 16 September 2026.

This section applies to Trip Reaper and Trip Nav on Android and iOS, together with the website policy above. The Apple App Store and Google Play sections explain the additional processing for each store. Available features depend on the app, device and account.

Information we collect and why

We receive the information you enter, upload or record: your name, email and account identifiers; vehicle, maintenance, fuel and expense records; saved addresses and destinations; journey locations, routes, times, distance, speed and travel mode, including walking or cycling activity; selected photos and documents; friends, messages, checklists and support requests; and subscription purchase records. We associate these records with your account to provide sign-in, navigation, journey history, vehicle management, sharing, support and paid access. Account details are required for account features; you choose whether to add optional records, upload files, send messages or make purchases. Friends are connections within Trip Reaper; we do not import your device address book.

Location and device permissions

With your device permission, we use precise or approximate location for maps, nearby places, navigation and journey recording. During an active journey or navigation session, location can continue to be collected and sent to our services and the navigation provider while the app is in the background or the screen is locked. Stop the active session or revoke location permission in device settings to stop this access. You can turn off detailed journey-map capture for future journeys in Profile; summary information and endpoints still remain. This setting does not disable location processing needed for active guidance. Revoking a permission stops the relevant future device access; it does not erase data already saved. Installed vehicle trackers operate separately from phone permissions.

Maps, navigation and notifications

Google Maps, Places, Routes and Navigation receive the map and guidance requests needed for the features you use, including destination searches, coordinates and route information. Google's mobile map and navigation SDKs also collect technical data such as IP address, device and operating-system details, SDK identifiers, crash logs, performance measurements and diagnostics, and interactions such as map movements and navigation-screen use. Google uses this information to deliver its services, understand usage, diagnose problems and improve its services. Some technical collection is automatic when these SDKs run; it is separate from optional website analytics.

Firebase Cloud Messaging and, on Apple devices, Apple Push Notification service process installation identifiers, push tokens, app/device information and notification payloads to deliver messages and reminders. Firebase also processes technical metadata and diagnostics to operate and improve notification delivery. Our server associates registered push tokens with your account so notifications reach the right device. You can manage notification permission in device settings; disabling alerts does not erase existing installation or account records. Photos and documents are uploaded when you select them for a feature. Browser pages opened from the app follow the website policy, including website analytics when enabled.

Apple App Store — iOS

If you use Sign in with Apple where offered, Apple provides an app-specific identity and the name and email you authorize, which may be an Apple private-relay address. We use these details and Apple authorization tokens to create or authenticate your Trip Reaper account, verify access and revoke the Apple connection when you delete the account. We do not receive your Apple Account password.

When you buy an App Store subscription, Apple processes the payment. We send an account-linked identifier to associate the purchase with your Trip Reaper account and verify transaction identifiers, product, renewal, expiry and subscription status with Apple. We keep the verified purchase record to provide or restore paid access and prevent purchase misuse. We do not receive the payment card details you enter with Apple. Manage renewal and cancellation in your Apple subscriptions; deleting the app or your Trip Reaper account does not cancel the subscription.

Apple Privacy Policy · Manage Apple subscriptions

Google Play — Android

When you buy a Google Play subscription, Google processes the payment. Google Play supplies a purchase token and product information to the app, which sends them to our server for verification with Google. We also send an account-linked identifier to associate the purchase with your Trip Reaper account. We keep the purchase token, product, renewal, expiry and subscription status to provide or restore paid access and prevent purchase misuse. We do not receive your Google password or the payment card details you enter with Google Play.

Manage renewal and cancellation in Google Play subscriptions. Deleting the app or your Trip Reaper account does not cancel the subscription. Android location and notification permissions can be changed in device settings; the location and SDK processing described above also applies to the Android app.

Google Privacy Policy · Manage Google Play subscriptions

Sharing and community safety

Shared journeys and messages are visible to the audience you select; public journeys can be viewed without signing in and may reveal recorded locations. Vehicle sharing and enterprise access also depend on the vehicle owner's or organization's permissions. Our connected account and transport services process the records needed to provide these features. Authorized support and moderation staff may access relevant records to investigate requests, protect accounts and address abuse. Providers processing data on our behalf must protect it consistently with this policy and use it for the services they provide. The providers named above also describe their own processing in their privacy policies.

Use Friends or a conversation's menu to report abuse or block a user. Reports are reviewed by administrators; message evidence is retained for moderation. Blocking stops messages, invitations and authenticated shared-journey access between the accounts; public pages may still be viewed without signing in.

Security and retention

App connections to our services use HTTPS encryption in transit. Local passwords are hashed, sensitive server credentials and tokens are protected, and access to account records is restricted. Account and journey records are retained to provide your account history. Removing a record from view does not always erase every stored copy; you can request permanent deletion through the channels below. Support requests remain until an administrator deletes them. Purchase verification, security and moderation evidence may need to be retained for fraud prevention, resolving disputes or legal obligations. Retention exceptions are reviewed during deletion and explained with their reason and period. Apple and Google may retain their own store and service records under their respective policies; deleting a Trip Reaper account does not delete your Apple or Google account.

Account and data deletion

In the app, open Profile → Delete account. This requests deletion of your account and associated personal data, including records held by our connected services. Your access closes immediately and a deletion request is recorded; data disposal is handled separately from closing access. We review associated data within 30 days and confirm completion by email. Where records must be retained, the completion notice explains the reason and retention period. Organization-owned records are reviewed with the organization so the request does not remove other people's business records. Apple or Google subscriptions continue until cancelled in the store where you subscribed.

You can also sign in on the website and delete your account in Profile. For privacy questions, use the contact form.

To request account deletion without the app, or deletion of selected data while keeping your account, use the contact form or email the address below. State your account email, the app you use and what you want deleted. We may verify account ownership before acting. You can also request access or correction through these channels. Do not send passwords, purchase tokens or payment card details.

Trip Reaper privacy contact: [email protected]

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, optional country and phone, email-verification status, securely hashed local password, preferences, sessions, password-reset records, 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 and conversation replies store the name, email, subject, messages, delivery status, and timestamps needed for the Trip Reaper administrator to review and respond. A random private page address lets the sender view and continue the conversation; anyone with that address can read it. Trip ideas are public editorial content and do not contain rider records. Basic network and request metadata—including effective IP, selected Cloudflare location headers, referrer, language, and user agent—is also retained for abuse prevention and administrator review.

6. Maps, analytics, and service providers

If enabled by the administrator, Google Maps may process route-planning requests, browser location supplied to the planner, and journey-route coordinates displayed on authorized journey detail pages. 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 contact details, password, distance units, reminder syncing, and detailed-map preference. Changing a personal account email requires verification again and revokes connected mobile sessions. 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.