Last updated: 18/08/2026
This policy covers the ridelog.it website. The RideLog app has its own, on the
app privacy policy page.
1. Who processes your data
Dimitri Giani
Largo Riviera 7, 56128 Pisa, Italy
VAT number: IT02381200506
Email: hello@ridelog.it
2. In short
The site does not profile you. There are no analytics tools, no advertising, no social
buttons following you from site to site, no remarketing.
You won’t find a cookie banner: none is needed, because the only cookies the site sets are
technical ones that make it work.
3. Data collected while you browse
Like any website, the server records in its technical logs your IP address, the date and
time of the request, the page requested, your browser and operating system, and the site
you came from, if any.
This is data the internet protocol involves by itself: it keeps the site running, helps
diagnose faults and spot abuse. We don’t use it to build profiles and we don’t cross-
reference it with anything. ❓ It is kept for [DURATION — ask the host].
4. Cookies
The site uses technical cookies only:
| Cookie | What it does | Duration |
|---|---|---|
pll_language | remembers the language you picked | 1 year |
wordpress_logged_in_*, wp-settings-* | keep the session alive, only if you sign in to the admin area | session or 1 year |
No profiling cookies, no third-party cookies, no advertising cookies. Technical cookies
need no consent under the law, which is why there is no banner to dismiss.
You can delete or block them in your browser settings: the site carries on working, it will
simply forget the language you chose.
5. Contact form
When you write through the contact form we collect your name, email address and the
message you write. They reach us by email and we use them only to reply to you.
❓ The form relies on Akismet, by Automattic, to recognise automated submissions: in that
case the form’s content and your IP address are transmitted to Automattic for the check.
[CONFIRM whether Akismet is active, otherwise remove this paragraph.]
6. Sending email
❓ The emails the site sends — the copy of contact form submissions and service messages —
are delivered through [SMTP SERVICE — see the WP Mail SMTP configuration], which handles
the recipient’s address and the message content only for as long as delivery takes.
7. Resources loaded from third parties
Some of the site’s presentation is served by third parties:
| Service | What it provides | What it receives |
|---|---|---|
| Google Fonts (fonts.googleapis.com, fonts.gstatic.com) | the site’s typefaces | your IP address and the technical data of the request |
| jsDelivr (cdn.jsdelivr.net) | a library for image galleries | your IP address and the technical data of the request |
They set no cookies, but to deliver the file they do receive your IP address. These are
requests your browser makes on its own while loading the page.
8. Legal basis for processing
| Processing | Legal basis |
|---|---|
| Server technical logs and technical cookies | legitimate interest in running and protecting the site (Art. 6.1.f) |
| Contact form | responding to your request (Art. 6.1.b) and legitimate interest in replying (Art. 6.1.f) |
| Spam filtering | legitimate interest in protecting the site from automated submissions (Art. 6.1.f) |
9. How long we keep data
| Data | Retention |
|---|---|
| Server technical logs | ❓ [DURATION] |
| Messages received through the contact form | for as long as needed to handle the request and the related dispute period |
| Cookies | the durations listed in section 4 |
10. Where data is processed
The site is hosted with Hostinger, on servers in Europe. The services listed in section
7 are based in the United States: those transfers rely on the Standard Contractual Clauses approved by the European Commission and/or membership of the EU-U.S. Data Privacy Framework.
11. Your rights
At any time you can request access, rectification, erasure, restriction and
portability of your data, and object to processing based on legitimate interest.
Write to hello@ridelog.it: we answer within 30 days.
You also have the right to lodge a complaint with the Italian Data Protection Authority,
the Garante per la protezione dei dati personali (www.garanteprivacy.it), or with the
supervisory authority in your own country.
12. No advertising, no analytics
- No analytics or statistics tool, from any provider
- No conversion pixels, no remarketing
- No social widgets, no buttons that follow you from site to site
- No profiling, no selling of data
13. Changes to this policy
We may update this policy. Changes are published on this page, with the date of the last
update shown at the top.
Application Privacy Policy
This policy covers the RideLog app on iPhone and iPad and on Android. Where the two
platforms behave differently, the difference is stated.
1. Who processes your data
Dimitri Giani
Largo Riviera 7, 56128 Pisa, Italy
VAT number: IT02381200506
Email: hello@ridelog.it — Support: support@ridelog.it
2. In short
RideLog records your motorbike trips, refuelling, servicing and vehicle expenses.
Almost everything stays on your phone. Vehicles, trips, GPS tracks, refuelling, expenses, documents and photos are saved in your device’s storage: we don’t upload them anywhere and we can’t read them.
There are two exceptions, and you choose both:
- your account, which exists only so you can publish and find your shared trips;
- the trips you choose to publish, which become visible to other RideLog users.
On Android there is a third thing to know: some features rely on Google’s services and send them location data even when you publish nothing. This covers the trip thumbnails in the list and the route calculation at the start of a trip. They are explained in sections 6.9 and 6.10.
Beyond that we collect usage statistics, which you can turn off whenever you like, and some features (weather, fuel stations, events, charge points) need to know roughly where you are in order to answer you.
There is no advertising, no profiling, and we don’t sell data to anyone.
3. Data that stays on your device
This information is saved on your phone only. No copy reaches our servers, except in the cases described in section 6.
| Category | Contents |
|---|---|
| Vehicles | make, model, registration plate, year, engine capacity, power, emissions, fuel type, tank capacity, consumption, odometer, vehicle photo, name of the on-board Bluetooth device |
| Trips | date and time, GPS track, speed, distance, duration, altitude, start and end addresses, trip weather, tags, notes, driving score |
| Telemetry | acceleration, braking, lateral force and estimated lean angles during the trip |
| Refuelling and charging | date, quantity, price, fuel type, mileage, place, notes |
| Servicing and reminders | type of work, date, amount, garage, due dates, notes |
| Documents and photos | images and PDFs you attach to trips, vehicles or servicing records |
| Statistics | values calculated from the data above |
| Settings | app preferences, units, currency, notifications, paired Bluetooth devices |
At any time you can export this data, transfer it to another device, or delete it. Uninstalling the app removes it from your phone.
The export formats differ by platform: on iOS, PDF, CSV, GPX and a full backup; on Android, CSV, JSON and a full per-vehicle backup in JSON.
4. Permissions the app asks for
On iPhone and iPad
| Permission | What it is for |
|---|---|
| Location (including in the background) | recording your trip track, remembering where you parked, showing you nearby fuel stations, charge points and events |
| Motion & Fitness | automatically recognising when you are moving on a vehicle, and starting or ending the trip |
| Bluetooth | recognising your bike’s Bluetooth device and starting the trip automatically |
| Local Network | finding your other devices for direct data transfer |
| Camera | photographing the vehicle, documents and the odometer |
| Photos | choosing and saving vehicle images and attachments |
| Notifications | reminders for due dates, riding alerts, app announcements |
| Siri & Shortcuts | running RideLog actions by voice or from iOS Shortcuts |
RideLog for iOS supports CarPlay, widgets and Live Activities: they display data already on the device and involve no additional transmission.
On Android
| Permission | What it is for |
|---|---|
| Precise and approximate location | recording your trip track |
| Background location | carrying on recording with the screen off, and recognising the start of a trip |
| Activity recognition | working out when you are moving on a vehicle, and starting or ending the trip |
| Notifications | reminders for due dates, riding alerts, the notification for the trip in progress |
| Camera | photographing the vehicle, documents and the odometer |
| Bluetooth (connect and scan) | recognising your bike’s Bluetooth device and starting the trip automatically |
| Nearby Wi-Fi devices | finding your other devices for direct data transfer |
| Battery optimisation exemption | stopping the system from suspending the app while it is recording a trip |
The Bluetooth and Wi-Fi permissions are declared so that they cannot be used to derive your location. Photos are chosen through the system picker, which requires no gallery permission at all.
While a trip is in progress, Android shows a persistent notification: it is how the system tells you the app is recording in the background, and it is mandatory. You can stop the recording from it.
There are no widgets on Android, no Android Auto, and no Wear OS version.
You can deny or revoke any permission in the system settings. The features that depend on it will stop working; the rest of the app carries on as normal.
5. Backup and other devices
- The backup you generate in the app is a file you share yourself, to whatever destination you pick. We don’t receive it.
- On iOS, if you have iCloud Backup switched on, the app’s data is included in the system backup: it stays in your iCloud space, is governed by Apple’s privacy policy, and we have no access to it. The app also stores in iCloud the installation identifier described in section 6.1.
- On Android, the app’s data is included in Google’s system backup: vehicles, trips, GPS tracks, refuelling, servicing, notes and preferences, including the installation identifier. It stays in your Google space and we have no access to it. Excluded from the cloud backup are your session token and your trip photos. A direct transfer to a new phone carries the photos across as well, while the token stays excluded either way: you will need to sign in again.
- Transferring data between two devices happens directly between the devices over the local network, after confirmation. It does not pass through our servers, on either platform.
- Data shown on Apple Watch travels directly between iPhone and watch through Apple’s services.
- Maps, turning coordinates into addresses, and route calculation rely on Apple’s services on iOS and Google’s on Android. The detail is in section 6.10.
6. Data that leaves your device
6.1 Usage statistics
To understand which features get used and to spot problems, the app sends the following to a statistics service run directly by the controller:
What is sent:
- an installation identifier: a random code generated on first launch. It contains neither your name nor your email, and it is not linked to your account if you have one. It is included in the system backup, so it stays the same if you restore the app onto another device; on iOS, where it is stored in iCloud, it is the same across all your Apple devices
- usage events (app launch, opening a section, starting and ending a trip, exporting a report, making a purchase)
- the screens you visit
- subscription status and purchase details (product, price, currency, transaction identifier)
- device model, system version, app version, language
What is NOT sent: your vehicle data, your trips, your tracks, your locations, your expense amounts, and nothing you write yourself.
You can turn this off in Settings → Share usage statistics. It takes effect immediately and you lose no functionality.
6.2 RideLog account
An account is not required to use RideLog: it exists only so you can publish trips and find the ones you have already published.
On iOS you register with Sign in with Apple. We receive from Apple and keep your Apple identifier, your name and your email address. If you choose Hide My Email, we receive the anonymous address generated by Apple, not your real one.
On Android you register with Sign in with Google. We receive and keep your identifier, your name and your email address. Google offers no anonymous-email service like Apple’s: the address we receive is your account’s real one. Your Google profile picture is shown on the device but is not sent to us.
A session token is kept on your device, in the iOS keychain or in the equivalent encrypted store on Android.
You can sign out at any time. You can delete your account in Account → Delete account: this removes your profile, the trips you published, their photos and your access tokens.
6.3 Shared trips
When you choose to publish a trip, and only then, the following is sent to our servers:
- the trip’s GPS track (latitude, longitude and altitude of the points)
- the coordinates where the published track begins and ends, and the names of the places you started from and arrived at
- distance, altitude, date
- on iOS, the photos you attach to the trip, with their location, the time they were taken, and the caption you write. On Android, trip photos are not published
A published trip is public: other RideLog users can find it and see its route and photos, in particular by searching for trips near an area.
So that a ride starting from home doesn’t make your address public, the first and last 500 metres are not published: the shared route starts and ends away from the real departure and arrival points. The map you see on the publishing screen shows exactly what will be shared. The trip saved on your phone stays complete. A trip too short to leave a route after this trim cannot be published.
You can remove a published trip at any time from your shared trips section.
To show you nearby trips, the app sends your approximate location and a search radius. The request exists only to answer you: it is not retained, and it is not used to reconstruct your movements.
6.4 Weather, fuel stations, charge points and events
Some features need to know where you are in order to give you a useful answer:
- trip weather
- nearby charging points
- nearby events and rallies
- nearby fuel stations and prices (iOS only: this feature does not exist on Android)
In every one of these cases your location is rounded to about one kilometre before it leaves the device, along with the search radius and your language. These are area searches, so the approximation doesn’t change the result, but it does stop a precise position from being written into a server’s logs, ours or anyone else’s. The location is not retained, and it is not associated with your identifier or your account.
6.5 AI vehicle search
If you use the assisted search to fill in your vehicle’s details, the text you write and your language are sent to our servers, which forward them to Anthropic PBC to identify the make, model and technical data. Nothing else is transmitted: not your trips, not your location, not data that identifies you, not your account.
The text of your request is kept in a search cache on our servers, so the same question doesn’t have to be asked twice: it is not linked to any user, any device or any identifier. If something goes wrong the request also appears in technical logs, which are kept for 14 days.
6.6 Notifications
Reminders for due dates and servicing, riding alerts and the notification for the trip in progress are local notifications: your phone schedules them, without going through any server.
On iOS only, so that we can also deliver announcements sent by us, the system assigns your installation a notification token, registered with Google Firebase Cloud Messaging. The token identifies the app installation, not you, and is deleted when you uninstall the app or turn notifications off. On Android there is no remote notification service at all: every notification is generated by the device.
6.7 Error reports
If the app crashes, a technical report is sent to Google Firebase Crashlytics: device model, system version, app version and the state of the program when the error occurred. It exists only to find and fix the problem, and contains none of your trips, vehicles or expenses.
6.8 Application content
The app downloads content from our servers that has nothing to do with you: lists of makes and models, events and rallies, news, service announcements and configuration parameters. Only your language travels with the request. As with any request over the internet, the server records the IP address in its technical logs.
6.9 Trip thumbnails (Android only)
In the trip list, the thumbnail showing the route is an image generated by Google Maps. To generate it, the trip’s route is sent to Google as a simplified track, reduced to at most 80 points, together with the image’s size and styling. No other data of yours is sent.
Two things to know:
- it happens for every trip in the list, not only the ones you choose to publish;
- it does not happen for trips you have attached at least one photo to: in that case the thumbnail is your photo and Google is not involved.
The resulting image is stored on the device, so the request is made once per trip. The map you see when you open a trip’s detail draws the route on the device instead.
This feature does not exist on iOS, where thumbnails are drawn locally.
6.10 Addresses, place search and route calculation
To turn coordinates into readable addresses — the start and end of your trips, and the results when you search for a place by name — the app uses the operating system’s geocoding service, which sends the exact coordinates to Apple on iOS and to Google on Android.
Route calculation likewise relies on Apple on iOS and on Google on Android. On Android it happens in two cases:
- at the start of a trip, automatically. While the track still has at most one point, the app asks Google for the road route between where the vehicle was parked and your current position, in order to reconstruct the opening stretch lost while tracking was starting up. Only those two coordinates are sent. The request is only made when the two points are between 150 metres and 5 kilometres apart;
- when you add or edit a trip by hand, picking the start and end from the place picker, to obtain the distance and the route to draw on the map.
Two things to know. First: in these cases the coordinates are not rounded as they are in section 6.4, because a route calculated from an approximate position would not match the real roads. The spot where you parked — often your home — therefore arrives exact. Second: the reconstructed points become part of your trip like any other, so if you publish it they are subject to the same 500-metre trim described in section 6.3.
7. Third-party services
| Service | Platform | Data transmitted | Purpose | Location | Privacy policy |
|---|---|---|---|---|---|
| Apple Inc. | iOS | Sign in with Apple; maps, geocoding and route calculation; in-app purchases; iCloud backup | account, maps, purchases, backup | USA / EU | apple.com/legal/privacy |
| Google LLC | Android | Sign in with Google; maps, geocoding and route calculation (section 6.10); trip thumbnails (section 6.9); purchases; system backup | account, maps, purchases, backup | USA / EU | policies.google.com/privacy |
| Anthropic PBC | both | text of the vehicle search | interpreting the request | USA | anthropic.com/privacy |
| Google Firebase Crashlytics | both | error reports | diagnosing malfunctions | USA / EU | firebase.google.com/support/privacy |
| Google Firebase Cloud Messaging | iOS | notification token, installation identifier, device technical data, IP | delivering notifications | USA / EU | firebase.google.com/support/privacy |
| WeatherAPI.com | both | approximate location (~1 km), language | weather forecasts | USA | weatherapi.com/privacy.aspx |
| Open Charge Map | both | approximate location (~1 km) | charging points | EU / USA | openchargemap.org/site/about/privacy |
Usage statistics, the shared trips archive, the fuel station list and the events list run on servers operated directly by the controller, hosted with Hostinger in Europe, and are not entrusted to third parties.
8. Legal basis for processing (Art. 6 GDPR)
| Processing | Legal basis |
|---|---|
| Vehicle, trip, expense and attachment data on the device | performance of the service (Art. 6.1.b) — it stays on the device |
| Account and trip publishing | performance of the service you requested (Art. 6.1.b), triggered by your choice |
| Weather, fuel stations, charge points, events | performance of the service (Art. 6.1.b): the feature cannot work without your location |
| Trip thumbnails on Android | performance of the service (Art. 6.1.b): it is how the app draws the route preview |
| Addresses, place search and route calculation | performance of the service (Art. 6.1.b): the app cannot record or display the trip without them |
| AI vehicle search | consent (Art. 6.1.a), given by using the feature and withdrawn by not using it |
| Notifications | performance of the service (Art. 6.1.b) and your consent to the notification permission |
| Usage statistics | legitimate interest in improving and securing the app (Art. 6.1.f); you can object using the switch in Settings |
| Error reports | legitimate interest in keeping the app working (Art. 6.1.f) |
| Email support | performance of the service and legitimate interest in answering your requests |
| Purchases and subscriptions | performance of the contract and legal obligations |
9. How long we keep data
| Data | Retention |
|---|---|
| Data in the app | on your device, until you delete it or uninstall the app — we hold no copy |
| System backup | in your iCloud or Google space, until you delete it |
| Account | until you delete it; on deletion we remove your profile, published trips, photos and access tokens |
| Published trips | until you remove them or delete your account |
| Usage statistics | individual events for 14 months, then deleted; only aggregate data remains, traceable to no installation |
| Text of the AI vehicle search | in the search cache for as long as it stays useful, linked to no user; 14 days in technical logs |
| Error reports | according to Google Firebase Crashlytics policies (typically 90 days) |
| Server technical logs | 14 days |
| Support emails | for as long as needed to handle the request and the related dispute period |
10. Transfers outside the European Union
The controller’s servers are in Europe. Some providers are based in the United States: those transfers rely on the Standard Contractual Clauses approved by the European Commission and/or membership of the EU-U.S. Data Privacy Framework. Write to hello@ridelog.it for the details.
11. Your rights
At any time you can request access, rectification, erasure, restriction, portability of your data, and object to processing based on legitimate interest. Where processing is based on consent, you can withdraw it at any time, without affecting the lawfulness of what was done beforehand.
How to exercise them: write to hello@ridelog.it. We answer within 30 days.
Some things you can do yourself, straight away, without contacting us:
- turn off usage statistics in Settings → Share usage statistics
- remove a published trip from your shared trips section
- delete your account in Account → Delete account
- export all your data in the formats listed in section 3
- delete the app’s data by uninstalling it
For requests about usage statistics we will use the installation identifier: without it we are unable to link that data to you, and that is by design.
You also have the right to lodge a complaint with the Italian Data Protection Authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it), or with the supervisory authority in your own country.
12. Children
RideLog is not aimed at children under 16 and we do not knowingly collect their data. If you believe a child has given us personal data, write to hello@ridelog.it and we will delete it.
13. No advertising, no tracking
- No advertising inside the app
- No use of Apple’s advertising identifier (IDFA) or Google’s
- No request for permission to track across apps and websites
- No third-party analytics service: the usage statistics described in section 6.1 stay on our own servers
- No profiling for marketing purposes
- No sharing with advertising intermediaries
14. Changes to this policy
We may update this policy. Changes are published on this page and, where they matter, flagged inside the app. The date of the last update is shown at the top of this document.