Who we are
Clive is a UK train companion provided by Lloyd.dev Ltd. This policy covers the Clive app and clive.bot. Lloyd.dev Ltd is responsible for the personal information it processes in providing these services. Contact us at support@clive.bot with privacy questions or requests.
You do not need to create a Clive account to use the app.
Location and nearby stations
With your device’s permission, Clive uses your location to find nearby stations and order favourite stations by distance. The app compares your location with station coordinates on your device. Its widget can also use permitted location access to select a nearby favourite.
Clive’s rail requests use station codes and service identifiers, rather than sending your GPS coordinates. A station selected using your location can still reveal something about the area you are travelling in. You can search manually without location access, and change location permission in your device’s Settings.
Information saved on your device
Clive saves favourite stations, recent destination filters, settings, cached station and departure data, and the train you are following. The app shares favourites and cached departures with its widget through storage on your device.
Journey memory records explicit route choices and followed services to suggest familiar journeys. These records can include origin and destination station codes, dates and times, and a service identifier. Memory is enabled by default unless you previously paused it.
When history is read or updated, Clive removes entries more than 60 days old and keeps at most 2,000 events. In Settings → Journey history you can pause memory or clear this history. Clearing it does not remove favourite stations, recent destination filters or hidden-route preferences; those are managed separately.
The journey-memory file is not uploaded as a history database. This is separate from the rail requests and analytics described below. Device backups may include app data, depending on your Apple settings.
Live rail information
To load departures, calling points and train details, Clive sends requests to rail services available through the Rail Data Marketplace. Requests can contain origin and destination station codes, the requested time and a service identifier. The service also receives connection information, such as your IP address, needed to respond.
These requests are necessary to show the live information you ask for. They are separate from any location permission or journey-memory preference.
App analytics
Clive uses TelemetryDeck to understand app use and improve reliability. Its SDK sends session events and technical information such as app and operating-system versions, device type, language and region settings, and a hashed app-user identifier.
Clive also sends events when you start or stop following a train, change the followed destination, or receive a detected delay, cancellation or platform change. Depending on the event, this includes station codes, a service identifier, platform numbers, delay minutes, tracking duration, the reason tracking ended and whether the service was on time.
These events concern your use of Clive; they do not establish that you boarded or completed a journey. Clive does not supply a name or email address to the analytics SDK. TelemetryDeck says it does not store IP addresses for app analytics. Journey-related event data still leaves your device, so we do not describe all travel information as device-only.
Pausing or clearing journey memory does not turn off analytics or delete events already sent. The current app has no separate analytics switch. Contact us with questions about this processing. TelemetryDeck’s published retention policy currently has no fixed deletion schedule for cold-storage analytics events; see its privacy FAQ.
Apple features and purchases
Apple processes optional tip subscriptions and payment details through the App Store. Clive uses StoreKit purchase and entitlement information to recognise an active subscription and restore purchases. We do not receive your payment-card details through Clive.
If you enable notifications or follow a train, Clive uses Apple’s local notification and Live Activity features to show journey information. You can manage their permissions in your device’s Settings. Your Lock Screen settings determine what others can see there. Read Apple’s privacy policy for its processing.
This website and support
clive.bot does not load advertising, analytics scripts, remote fonts or tracking cookies. GitHub Pages hosts the site and may process IP addresses and other technical request information to deliver and protect it. See GitHub’s privacy statement.
If you email us, we receive your email address, message and any attachments. We use that information to answer the enquiry and investigate issues you report. Please only include the information needed for your request. Clicking an App Store or other external link takes you to a service with its own privacy practices.
Why information is used and shared
We use information to provide requested app features and support, maintain and improve the service, prevent misuse, and meet legal obligations. Where data-protection law requires a legal basis, processing may be necessary to provide the service you request, for our legitimate interests in operating and improving it, to comply with law, or based on consent where required. Permission for location and notifications can be withdrawn in device Settings.
Information is handled by the providers described above and service providers needed to deliver support. It may also be disclosed where required by law. Providers may process information outside the UK; their privacy notices explain the locations and safeguards that apply to their services. We do not use the app’s journey information to target advertising.
Retention and your choices
The journey-memory limits are described above. Other local settings and caches remain until changed, replaced or removed with app data. Removing Clive does not remove copies in device backups, cancel subscriptions or delete information already held by external providers.
We keep support correspondence for as long as needed to deal with the enquiry, follow-up issues and applicable legal obligations. Provider-held information is subject to the provider’s retention practices; local history controls do not erase that information.
Depending on your circumstances and applicable law, you may request access, correction or deletion of personal information, restrict or object to processing, or request a portable copy. Where processing depends on consent, you can withdraw it. Email support@clive.bot. We may need enough information to verify a request, and may be unable to associate analytics records with you.
You can also raise a concern with the UK Information Commissioner’s Office, or your local data-protection authority.
Changes to this policy
We will update this page when Clive’s data practices change and revise the date above. Contact us if you need help understanding a change.