Your location history, handled carefully.
A trip logbook knows where you drove. This policy explains what is stored, why, who can see it and how to have it removed. It is written to be read, not to hide behind.
Last updated: 16 November 2026
Account details, trips, points, vehicles, places, classifications, expenses and reminders.
No selling of movement data. Trips and locations are never shared with advertisers.
Account deletion is confirmed by email, then carried out 30 days later or when your paid subscription ends, whichever is later. Support can delete it straight away on request.
1. Who this policy covers
This policy covers the MyLogbook marketing website, the MyLogbook web application, the MyLogbook Android app and the API they use. In this policy, “we” and “us” mean the operator of MyLogbook, based in South Africa. “You” means the person using the service.
The Android app records trips on your device and uploads them to your account. This policy covers both what the app collects and what happens once those records reach the service. It does not replace any notice shown by your phone's operating system about location permissions.
2. What we collect
Account details
Your display name, email address, preferred units and currency, time zone, financial-year start month and stop-detection interval. Sign-in codes are stored with a short expiry so they can be emailed to you, and are marked used after sign-in. If you link a Google or Apple identity, we store the provider name, the provider's subject identifier and the email address the provider returns. We never receive or store a password.
Trip records
For each trip: start and end time, start and end coordinates, distance, duration, the vehicle, the trip type, the business flag, your reason or description, and the recorded points. A point can include latitude, longitude, altitude, speed, bearing, accuracy and a point-of-interest flag. Trips may also carry odometer values, battery percentages, an external identifier, the source that created them, and the phone model and app version that recorded them. The recorded points of each trip are kept as one file in our storage, linked to the trip.
Device details
When you open the mobile app, at most once a day, it sends a random identifier created by the app the first time it runs, and the phone's platform, operating system and version, manufacturer, model, app version, time zone and language setting. It also sends four country codes, such as “ZA”: the country of the mobile network the phone is connected to, the country that issued its SIM card, the country in its region setting and the country of its Google Play account. These show the country only, not where in it you are, and they do not use the location permission. We use these details to find recording problems that only affect certain phones and subscription problems that only affect certain countries. The random identifier is removed when you uninstall the app or clear its data. The app does not read your phone's IMEI, phone number, SIM serial number or subscriber identity, and the name you gave your phone is not collected. The advertising identifier is used only by app analytics, described below.
Supporting records
Vehicles, the name and address of the car Bluetooth device you link, odometer readings, saved places and their radii, auto-mark rules, mileage rates, expenses, reminders, GPX files you import, and the import batch history. Contact messages include the name, email address, subject, message and the IP address the message arrived from.
Subscription records
Cloud is bought through Google Play. Google processes the payment, and we never receive your card or bank details. To confirm a subscription, we receive and keep the purchase token, the product and plan, the purchase, renewal and expiry dates, whether the subscription renews automatically, and whether it was cancelled, refunded or paused. The purchase is linked to your account through an identifier derived from your account, not your name or email address. We also keep a history of subscription changes, including any time added by us or by a referral reward.
Referral records
Your referral code, the account that referred you, the accounts that signed up with your code, the dates they signed up and subscribed, and the rewards added to each account.
Technical records
The service keeps the technical information needed to run and secure it, such as request logs, error records and the time of access. The web application stores a session token in browser storage so that you stay signed in.
Error reports
When something fails in the Android app, the web application or the API, an error report is sent to Sentry, our error-monitoring provider. A report can include the error message and where in the code it happened, the screen or request involved, how long requests took, the app version, the phone or browser model and operating system, and your account identifier. If subscription options fail to load from Google Play, the report also includes Google Play's response, the subscription product, the four country codes described under Device details, and the phone's time zone and language setting. Before a report is sent, email addresses, sign-in codes, tokens, cookies and location coordinates are removed. Sentry's collection of IP addresses and personal details is switched off, and screens and sessions are not recorded. We use these reports only to find and fix faults.
Website analytics
If you allow it in the cookie banner, the marketing website uses Google Analytics to count visits and see which pages are read. Google Analytics then sets cookies and sends Google the pages you view, how you arrived, and your browser, device type and approximate location. It does not receive anything from your logbook, and advertising features are switched off. If you choose “No thanks”, Google Analytics is not loaded. You can change your choice at any time with “Cookie settings” in the website footer. Google processes this data under its own privacy policy. The web application does not use Google Analytics.
App analytics
The Android app uses Google Analytics for Firebase to measure which of our Google ads lead people to install and use the app. It records when the app is first opened, app sessions and updates, sign-up and sign-in and the method used, adding your first vehicle, recording your first trip, and starting a subscription. With these events Google receives the phone's advertising identifier, model, operating system, app version, language setting and an approximate location worked out from its IP address, such as the city. Google uses this to report and improve our ad campaigns. It does not receive your trips, coordinates, vehicles, email address or name. You can reset your advertising identifier or opt out of personalised ads in your phone's Google settings. Google processes this data under its own privacy policy.
3. Why we process it
- To create and secure your account and sign you in with an email code or a linked Google or Apple identity.
- To store trips and produce the logbook, summaries, maps and reports you ask for.
- To calculate mileage claims using the rates and vehicles you configure.
- To import GPX files and keep the original file with its import history.
- To confirm Cloud subscriptions with Google Play and keep your access in step with renewals, cancellations and refunds.
- To run the referral programme and add the rewards it earns.
- To answer support messages and account-deletion requests.
- With your permission, to measure how the marketing website is used so that we can improve it.
- To measure which of our Google ads lead people to install and use the Android app.
- To detect abuse, investigate errors and keep the service available, including through error reports.
- To meet legal obligations that apply to us.
We process account and trip records to provide the service you have asked for. Where a choice is optional — such as sending a contact message — we ask for your agreement at the point you provide the details. You can withdraw that agreement by asking us to delete the message or the account, subject to any record we must keep by law.
4. Who can see it
Trip records are scoped to your account. They are not public, and they are not shown to other users. Access inside the service is limited to the people who need it to operate, support and secure the platform.
The referral programme shows a shortened form of a name to the other person in the referral, such as “Ja•••• K.”: the person who referred you sees yours, and you see theirs. No email address, trip or other record is shown.
We use service providers for hosting, database operation, file storage, transactional email, error monitoring (Sentry), app analytics and ad measurement (Google Analytics for Firebase) and, if you allow it, website analytics. Google Play processes subscription payments and tells us the state of each subscription. If you choose Google or Apple sign-in, that provider verifies your identity and returns a token; we receive the identity details needed to link the account. These providers process data under their own privacy terms. Our service providers process data on our instructions. We do not sell personal information, and we do not share location history with advertisers or data brokers.
We may disclose information where the law requires it, where it is necessary to investigate fraud or abuse, or to protect the rights and safety of a person. Where a disclosure is permitted and we are able, we will tell you.
5. Location data
Location history is the most sensitive record in the logbook. It is collected to show the route, measure the trip and support the report. Location is only read while a trip records: when you start a trip yourself, or when the car Bluetooth device you chose connects. If you allow location all the time, that Bluetooth trigger can start a trip even if the app is closed or not in use, and the trip stops when it ends. The app explains this next to the permission before you grant it, a notification is shown while a trip records, and you can turn the trigger off or withdraw the permission at any time. Location is not used to build an advertising profile, and it is not sold. If you stop using the service, you can export the trips and ask for the account to be deleted.
6. How long it stays
Account and trip records are kept while the account is active. When you request deletion, we email a confirmation link. After you confirm, the account is scheduled for deletion, and on the deletion date the user-owned records — trips, points, vehicles, places, rules, expenses, reminders, readings, rates, import batches, uploaded files, linked devices, linked Google or Apple identities and sessions — are removed, and your name and email address are replaced on the account record. Until that date your data stays in the account. Contact messages may be kept for a limited period to resolve the query and keep a record of the request.
We may keep a minimal record of a deletion request where we need it to show that the request was carried out, or where another law requires a record to be kept. Subscription and payment records may be kept for as long as tax and accounting law requires. If you referred someone or were referred, the referral link and its rewards stay on the other person's account, and your name there is shown as “Deleted account”. Error reports are kept by Sentry for a limited period and then deleted automatically. When you ask to delete your account, it is deleted 30 days after you confirm, or after your paid Google Play subscription ends if that is later. Your subscription won't renew, you keep the time you've paid for, and you can cancel the deletion before that date. If you want the account deleted straight away instead, email support@mylogbook.co.za from the address on the account; any paid time left is then given up. Step-by-step instructions are on the delete your account page.
7. How it is protected
Sign-in codes expire after a short period, can be used once and allow only a few attempts. Access to the API requires a signed token, sessions can be revoked, and authentication endpoints are rate-limited. Sign-in with Google or Apple is verified against the provider's published signing keys. Production traffic is served over HTTPS. No system is perfectly secure; if you believe your account has been accessed without permission, contact us so the sessions can be revoked.
8. Your choices and rights
Subject to South African data-protection law, you can ask to see the personal information we hold about you, ask us to correct it, ask for it in a portable form, object to certain processing, or ask for it to be deleted. The service already provides export and deletion tools for the main records.
Send a request to support@mylogbook.co.za. We may need to verify that the request comes from the account holder before acting on it. You also have the right to complain to the Information Regulator (South Africa) at inforegulator.org.za.
9. Children
The service is intended for adults who drive and claim travel. It is not directed at children under 18, and we do not knowingly create accounts for them.
10. Changes to this policy
If the way we handle information changes, this policy will be updated and the date at the top will change. A material change will be communicated in the application or by email before it takes effect where that is practical.
11. Contact
Privacy questions and requests: support@mylogbook.co.za. For anything else, use the contact page.