In short: Drivers Logbook stores the records you enter locally on your device. There is no required account, developer-run cloud sync, advertising SDK or analytics SDK in the current app. You choose whether to export a file or enable automatic backups to a folder you control.
Who is responsible for this policy
Drivers Logbook is operated by Donut Development LTD. In this policy, “we”, “us” and “our” refer to the operator of Drivers Logbook. For privacy questions or requests, email support@driverslogbook.co.uk.
Information kept only in the app
The app can store information you choose to enter, including companies and contacts, shifts, vehicles, trailers, mileage, fuel and fuel-card PIN references, defects, notes, absence and leave balances (including hours, day equivalents and approved carry-over), pay and tax settings, payslip checks and corrections, an optional driver profile, app preferences and purchase-entitlement state.
Optional tachograph tools can store card identity metadata and unique decoded work periods, including activity, card-in/out, vehicles, places and odometer information where the card provides it. Bluetooth connection is unavailable in the card-reader release. The app does not scan for or connect to nearby tachographs.
Core logbook data is stored locally in the app’s private on-device storage. We do not receive or host it during normal use and cannot view, recover or delete it for you remotely.
Pay calculations may be reused temporarily in device memory while their inputs are unchanged. This does not send records to us or create a cloud account. Clear All Data also clears these calculation results. Each device keeps separate records unless you transfer a backup yourself.
Document recognition and tachograph hardware
Document recognition for driver documents and optional payslip setup is designed to run on-device. Captured or imported images are temporary and deleted after recognition; fields you review and confirm may be saved. Drivers Logbook does not authenticate a document.
Supported driver-card reads use a fixed read-only catalogue. The app preserves useful unique derived work periods and provenance while discarding repeated raw reader snapshots after successful decoding. Imported card records are a personal reference, not complete signed statutory downloads.
Camera or photo, connected-reader, notification and file access are requested for the feature you choose.
Backups, recovery copies, PDFs and sharing
Automatic protection and folder backups apply only to app versions that show those controls in Settings → Backup & Restore. Earlier versions require manual exports. The descriptions below do not mean that an older installation already has automatic protection.
The app keeps automatic recovery copies and earlier shift and tachograph records in its private device storage. It retains up to seven daily copies, three copies made before app updates, three safety copies made before restores or removal of original card files, and 500 earlier record versions, within a combined 128 MB recovery-file budget. Large logbooks retain fewer copies; a verified replacement temporarily requires additional space (up to 128 MB). Clear All Data removes these local copies and history. This history starts when the protection is enabled by the app update and cannot recover previously lost information.
Optional folder backups use the system file picker to grant access to a folder you select. The app remembers that permission on this device and saves changed data while the app is open, at most once a day, or when you choose Back up now. Selecting a folder requests an initial backup, subject to your connection preference. On versions with backup preferences, starting folder backups defaults to unmetered Wi-Fi; you can explicitly allow mobile data with either no app-imposed mobile allowance or a monthly backup-file allowance, select manual-only backups, and choose a not-before time. Failed mobile attempts count towards the file allowance. This allowance does not cap billed network usage. Automatic folder files are compressed where supported; compression is not encryption, and manual exports remain plain JSON. The app checks connection type locally and keeps local totals of verified backup-file sizes, not measurements of your provider’s network traffic. These checks and totals are not sent to us. The provider controls any later upload connection. A cloud storage provider may then upload the file under its own privacy terms. Not every provider supports folder access; a local-only folder does not protect against device loss. We do not receive your cloud password or backup files.
Folder backup files are readable JSON, not password-encrypted by the app. They include records, settings and retained original tachograph-card files. Keep the folder private. The app verifies the saved file, but cannot confirm your provider has finished uploading it. For each installation, the app automatically retains at most seven managed folder backups within 256 MB, removing older managed copies after verifying a replacement. A replacement temporarily needs up to 128 MB extra space. Cleanup failures stop further backup creation until resolved. Manual exports and other installations’ backups are not automatically deleted. Stop folder backups revokes the app's remembered folder access; Clear All Data also disconnects the folder. Neither action deletes files already exported there. Delete unwanted external copies through your storage provider.
When you create a backup or export a PDF, the app prepares the file on your device and opens the device share sheet. You choose whether to save it to Files, send it by email, place it in cloud storage or share it with another app or person. The privacy practices of that destination then apply.
Backups can contain detailed work, pay, profile, equipment and derived tachograph information. PDFs and diagnostics can also contain private records or device identifiers. Keep those files somewhere you trust and check the recipient before sending them.
Calls and local notifications
If you tap a saved company contact, the app can ask the phone to open its dialler with that number. The call is handled by your phone and network provider; Drivers Logbook does not record the call.
If you start a break countdown, the app can schedule a local notification on your device. The notification is generated locally and is not sent through a Drivers Logbook server.
Purchases
Apple or Google processes the Pro purchase under its own terms and privacy policy. We do not receive your full payment-card details. The app receives the entitlement information needed to unlock Pro or restore a previous purchase. The relevant app store may provide us with transaction and diagnostic information through its developer tools.
Support and beta messages
If you email us, we receive the information you include, such as your email address, app and operating-system version, device model, screenshots and your description of the problem. If you voluntarily attach a backup or PDF, we will also receive the records in that file.
We use support information to respond, investigate faults, protect the service and improve the app. Our lawful basis is our legitimate interest in providing support and maintaining a reliable product. We use beta enquiries to administer testing and related communication; our lawful basis is the same legitimate interest and the action you requested by contacting us.
Do not send a backup unless it is necessary and you are comfortable sharing its contents. We will not use support material for advertising or sell it.
Website technical data
This website does not set advertising or analytics cookies in its current form. Our hosting and security provider may process ordinary technical request information such as IP address, browser details, requested page, time and security signals to deliver and protect the site. Our lawful basis is our legitimate interest in operating a secure, available website.
The App Store, Google Play, email and ICO links take you to external services. Those services receive the information normally sent when your browser opens a link and apply their own privacy policies.
Who information is shared with
Locally stored app records leave the app when you export or share them, or through automatic backups after you enable a chosen folder. Support messages are handled through our email provider. Website technical data is handled by our hosting and security provider. Purchase information is handled by Apple or Google. We may also disclose information where required by law or when necessary to establish, exercise or defend legal claims.
International processing
Some service providers used for email, website delivery or app-store services may process information outside the UK. Where we are responsible for such a transfer, we rely on an applicable adequacy regulation or contractual and organisational safeguards required by UK data-protection law. Contact us if you would like more information about the safeguards relevant to a particular support request.
How long information is kept
Current app records remain on your device until you edit them, delete them, restore over them, clear app data or remove the app. Earlier information can remain in local recovery copies and history until their retention limits are reached or you clear app data. Exported PDFs, diagnostics and manual backups remain wherever you chose to save them. Managed folder backups rotate under the limits above while that installation retains access. Files in old folders or from disconnected installations remain until removed through the provider. Provider-side trash and version history may keep additional copies beyond the app’s control.
Support and beta correspondence is kept only for as long as reasonably needed to handle the request, provide follow-up support, maintain security and deal with legal or accounting requirements, then removed through routine mailbox management. Website security logs are retained according to the hosting provider’s operational and security retention periods.
Your choices and rights
You can edit and delete local records in the app and create a backup before removing the app. Because we do not receive those records during normal use, requests to us cannot retrieve or alter the copy held only on your device.
For personal information we do hold, such as a support email, UK data-protection law may give you rights to ask for access, correction, erasure, restriction, portability or to object to processing. The rights that apply depend on the circumstances and lawful basis.
Your right to object: where we rely on legitimate interests, you can object to our use of your personal information. Email us with the details of your objection and we will consider it against the reasons for the processing.
Complaints
Please contact us first so we can try to resolve the issue. You also have the right to complain to the UK Information Commissioner’s Office. Visit ico.org.uk/make-a-complaint for current contact options.
Children
Drivers Logbook is intended for working drivers and is not designed for children. We do not knowingly use the website to collect information from children.
Changes to this policy
We will update this policy before introducing a materially different data use such as hosted accounts, developer-run cloud sync, analytics, employer monitoring or automated driver decisions. The date at the top shows the latest revision.
Contact
Email support@driverslogbook.co.uk.