Your data, your ride, your control
At Kalkhoff, your bike may be equipped with smart components that collect data to make your rides better, safer, and more fun. On this page, you'll find what data we collect, how we use it, and how you stay in control. It’s your bike — and your data.
1. Why we collect data
We use ride data to improve performance, track usage, and offer helpful features like ride history, and theft protection and recovery of stolen bikes.
2. Which components collect data
Kalkhoff uses a range of smart components. Your Kalkhoff bike may include some of these, depending on the model. To see exactly which components are on your bike, check the product overview for your specific model.
We distinguish between:
A. Components connected to Pon.Bike platform
For these components, Kalkhoff collects and stores data, which you can access through our developer portal and consumer portal
GPS modules
Comodule BnC
Comodule Guardian
Comodule Master Module
Data from these components is handled in accordance with this Data Statement and, where applicable, Privacy Statement.
B. Components connect to third-party platform
For the following components, data may be collected by the respective manufacturers. Kalkhoff does not store this data. To access or manage this information, please refer directly to their platforms:
Bosch
| Name Supplier | Type of device | Category | Data specifications of the connected product | Data Generation Capacity | Data storage | Access and Management of Data | |||
|---|---|---|---|---|---|---|---|---|---|
| Type example (all types of generated data, e.g. mileage, battery range) | format (format used to share data with User or Third Parties, e.g. CSV / Excel / Json) | estimated volume of data generated (frequency of sampling and/or publishing) | Confirm that the product can generate data continuously and in real-time (y/n) | product stores data on the device or a remote server (local / remote / both / not applicable) | retention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription) | Request a detailed explanation of how users can access, retrieve, or delete data, including technical means and terms of use. Including the URL of the Suppliers website to which Pon.Bike can refer the User | |||
| Bosch | Drive train | Telemetry | assistamce mode, power, torque, cadance, speed, range | JSON via Bosch SDK | Data is realtime, amount of data depends amount of cycling | Yes | On device, shared via Bluetooth or cable | Unknown |
Users can access data: yes (Via Bosh app or Kalkhoff app) Users can retrieve data: yes Users can delete data: no Technical means Users: via Bosch Website: https://www.bosch-ebike.com/ |
| Battery | State of charge, bike light, charger connected | ||||||||
| System | Firmware versions, identification bike, OEM, system locked | ||||||||
| Device meta data | service dates due, activity, walkassits | ||||||||
Fazua
| Name Supplier | Type of device | Category | Data specifications of the connected product | Data Generation Capacity | Data storage | Access and Management of Data | |||
|---|---|---|---|---|---|---|---|---|---|
| Type example (all types of generated data, e.g. mileage, battery range) | format (format used to share data with User or Third Parties, e.g. CSV / Excel / Json) | estimated volume of data generated (frequency of sampling and/or publishing) | Confirm that the product can generate data continuously and in real-time (y/n) | product stores data on the device or a remote server (local / remote / both / not applicable) | retention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription) | Request a detailed explanation of how users can access, retrieve, or delete data, including technical means and terms of use. Including the URL of the Suppliers website to which Pon.Bike can refer the User | |||
| Fazua | Drive train and app | Telemetry | assistamce mode, power, torque, cadance, speed, range, trip information | CSV or Excel | Server log file data is collected with each call of the app and transferred to the server. Personal and ride data is generally saved after each recorded and saved ride and then send to the server afterwards. | Yes | Both | Server Log Files: 7 days Personal and Ride Data: Until end of subscription |
Users can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via Email Website: https://fazua.com |
| Battery | State of charge, bike light, charger connected | ||||||||
| System | Firmware versions, technical data of the bike display, battery and drive train | ||||||||
| Device meta data | User ID, app version, user type, bike serial number | ||||||||
Enviolo
| Name Supplier | Type of device | Category | Data specifications of the connected product | Data Generation Capacity | Data storage | Access and Management of Data | |||
|---|---|---|---|---|---|---|---|---|---|
| Type example (all types of generated data, e.g. mileage, battery range) | format (format used to share data with User or Third Parties, e.g. CSV / Excel / Json) | estimated volume of data generated (frequency of sampling and/or publishing) | Confirm that the product can generate data continuously and in real-time (y/n) | product stores data on the device or a remote server (local / remote / both / not applicable) | retention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription) | Request a detailed explanation of how users can access, retrieve, or delete data, including technical means and terms of use. Including the URL of the Suppliers website to which Pon.Bike can refer the User | |||
| Enviolo | Automatic Hub Interface | Telemetry | Total distance, speed, cadance | *.csv export available on demand Direct access via enviolo App (Available via Apple or Google Play Store) |
Except Odometer and active wheel and cadence, data is static data and will only be transferred on connection of the Automatic Hub Interface to the enviolo App | Data is collected, but data sharing is only enabled via enviolo App Bluetooth connection | Data gets stored on the device and gets synced with Backend upon connection with the enviolo App | Data is retained as long as the device has memory space |
Users can access data: yes via app Users can retrieve data: Theoretical via request and transmission of *.csv file Users can delete data: no Technical means Users: via enviolo App Terms of Use: www.enviolo.com/privacy/ Website: www.enviolo.com |
| System | hub and motortype, CAN protocol, error flags, assistant behavior settings | ||||||||
| Device meta data | Identifiers and versions of the hardware and firmware, bike details | ||||||||
Shimano
| Name Supplier | Type of device | Category | Data specifications of the connected product | Data Generation Capacity | Data storage | Access and Management of Data | |||
|---|---|---|---|---|---|---|---|---|---|
| Type example (all types of generated data, e.g. mileage, battery range) | format (format used to share data with User or Third Parties, e.g. CSV / Excel / Json) | estimated volume of data generated (frequency of sampling and/or publishing) | Confirm that the product can generate data continuously and in real-time (y/n) | product stores data on the device or a remote server (local / remote / both / not applicable) | retention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription) | Request a detailed explanation of how users can access, retrieve, or delete data, including technical means and terms of use. Including the URL of the Suppliers website to which Pon.Bike can refer the User | |||
| Shimano | E-bike system, Hub, Di2 components | Telemetry | Riding related data | The product cannot provide data directly to users or third parties. | This product does not generate the relevant data at predetermined timing or intervals. | no | On the product (No data will be transferred to a remote server unless the user utilizes a separate app or equivalent software.) | The relevant data is stored on the product until it is updated. | Website: https://bike.shimano.com/ |
| System | Fault related data, usage history non personal data | ||||||||
| Device meta data | Device setting data | ||||||||
For privacy, legal, and technical reasons, Kalkhoff does not have access to the data from these systems.
3. What data is collected by Kalkhoff
Depending on your bike model and setup, we may collect the data as provided in the table below by activating the Kalkhoff app. A complete and more detailed overview of the data collected can be found in the developer portal.
Overview of Generated Data
The data processed by Kalkhoff may be considered personal data, such as location data (in case of loss or theft). The generated data is processed in accordance with this EU Data Act statement and, insofar as it concerns personal data, in accordance with the Privacy Statement. For more information, please refer to our Privacy Statement.
Comodule
Name Supplier
Type of device
Category
Data specifications of the connected product
Data Generation Capacity
Data storage
Access and Management of Data
Type example
(all types of generated data, e.g. mileage, battery range)
format
(format used to share data with User or Third Parties, e.g. CSV / Excel / Json)
estimated volume of data generated
(frequency of sampling and/or publishing)
Confirm that the product can generate data continuously and in real-time
(y/n)
product stores data on the device or a remote server
(local / remote / both / not applicable)
retention period
(how long is the data retained, i.e. days/week/month or untill termination of the subscription)
Request a detailed explanation of how users can access, retrieve, or delete data, including technical means and terms of use. Including the URL of the Suppliers website to which Pon.Bike can refer the User
Comodule
IoT module
Telemetry
Speed, cadance, distance
JSON
Data points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes
The module samples the data on the device and sends it if it has connection to the cloud every 4 minutes
Both (local only temporary until offloaded to the cloud)
Until end of the subscription via the app
Users can access data: yes
Users can retrieve data: yes
Users can delete data: yes
Technical means Users: via API or platform
Website: https://consumer-account.pon.bike/
Location
GPS coordinates during rides, Latitude and longitude
Battery
state of charge, battery performance
Network
signal strenght, signal quality, network connection
System
movement detection, range
Device meta data
Timestamp, GPS validation
| Name Supplier | Type of device | Category | Data specifications of the connected product | Data Generation Capacity | Data storage | Access and Management of Data | |||
|---|---|---|---|---|---|---|---|---|---|
| Type example (all types of generated data, e.g. mileage, battery range) | format (format used to share data with User or Third Parties, e.g. CSV / Excel / Json) | estimated volume of data generated (frequency of sampling and/or publishing) | Confirm that the product can generate data continuously and in real-time (y/n) | product stores data on the device or a remote server (local / remote / both / not applicable) | retention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription) | Request a detailed explanation of how users can access, retrieve, or delete data, including technical means and terms of use. Including the URL of the Suppliers website to which Pon.Bike can refer the User | |||
| Comodule | IoT module | Telemetry | Speed, cadance, distance | JSON | Data points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes | The module samples the data on the device and sends it if it has connection to the cloud every 4 minutes | Both (local only temporary until offloaded to the cloud) | Until end of the subscription via the app |
Users can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via API or platform Website: https://consumer-account.pon.bike/ |
| Location | GPS coordinates during rides, Latitude and longitude | ||||||||
| Battery | state of charge, battery performance | ||||||||
| Network | signal strenght, signal quality, network connection | ||||||||
| System | movement detection, range | ||||||||
| Device meta data | Timestamp, GPS validation | ||||||||
4. How to access your data
You can access your data via our Customer portal. Log in with your account to view the bikes linked to you. For each bike you own, you can view access your data via an API, and give or revoke access to third parties. You can access your data in (near) real-time via MQTT stream accessible via the developer portal. Code examples are available on the developer portal.
5. How to delete your data
To permanently delete your data go to customer portal and log in to your account. Here you will find the option to delete your account.
7. More questions?
Contact our support team. We’re happy to help!