Royal Dutch Gazelle

Your data, your ride, your control

At Royal Dutch Gazelle, 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

Royal Dutch Gazelle uses a range of smart components. Your Royal Dutch Gazelle 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, Royal Dutch Gazelle collects and stores data, which you can access through our developer portal and API:

  • 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. Royal Dutch Gazelle does not store this data. To access or manage this information, please refer directly to their platforms:

Drivetrain

Smart shifter

For privacy, legal, and technical reasons, Royal Dutch Gazelle does not have access to the data from these systems.

Bosch

  • Name SupplierType of device
  • Bosch Drive train
  • -
  • -
  • -

  • Name SupplierCategory
  • Bosch Telemetry
  • Battery
  • System
  • Device meta data

Data specifications of the connected product

  • Name SupplierType example (all types of generated data, e.g. mileage, battery range)
  • Bosch assistamce mode, power, torque, cadance, speed, range
  • State of charge, bike light, charger connected
  • Firmware versions, identification bike, OEM, system locked
  • service dates due, activity, walkassits

Data specifications of the connected product

  • Name Supplierformat (format used to share data with User or Third Parties, e.g. CSV / Excel / Json)
  • Bosch Json via Bosch SDK
  • -
  • -

Data specifications of the connected product

  • Name Supplierestimated volume of data generated (frequency of sampling and/or publishing)
  • Bosch Data is realtime, amount of data depends amount of cycling
  • -
  • -
  • -

Data Generation Capacity

  • Name SupplierConfirm that the product can generate data continuously and in real-time (y/n)
  • Bosch Yes
  • -
  • -
  • -

Data storage

  • Name Supplierproduct stores data on the device or a remote server (local / remote / both / not applicable)
  • Bosch On device, shared via Bluetooth or cable
  • -
  • -
  • -

Data storage

  • Name Supplierretention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription)
  • Bosch Unknown
  • -
  • -
  • -

Access and Management of Data

  • Name SupplierRequest 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 "Users can access data: yes (Via Bosh app or Gazelle app) Users can retrieve data: yes Users can delete data: no Technical means Users: via Bosch or Gazelle app Terms of Use: https://www.bosch-ebike.com/en/privacy-full Website: https://www.bosch-ebike.com/
  • -
  • -
  • -
Data specifications of the connected product
Data specifications of the connected product
Data specifications of the connected product
Data Generation Capacity
Data storage
Data storage
Access and Management of Data
Name Supplier
Type of device
Category
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 Gazelle app) Users can retrieve data: yes Users can delete data: no Technical means Users: via Bosch or Gazelle app Terms of Use: https://www.bosch-ebike.com/en/privacy-full 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 SupplierType of device
  • Fazua Drive train and app
  • -
  • -
  • -

  • Name SupplierCategory
  • Fazua Telemetry
  • Battery
  • System
  • Device meta data

Data specifications of the connected product

  • Name SupplierType example (all types of generated data, e.g. mileage, battery range)
  • Fazua assistamce mode, power, torque, cadance, speed, range, trip information
  • State of charge, bike light, charger connected
  • Firmware versions, technical data of the bike display, battery and drive train
  • User ID, app version, user type, bike serial number

Data specifications of the connected product

  • Name Supplierformat (format used to share data with User or Third Parties, e.g. CSV / Excel / Json)
  • Fazua CSV or Excel
  • -
  • -

Data specifications of the connected product

  • Name Supplierestimated volume of data generated (frequency of sampling and/or publishing)
  • Fazua 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.
  • -
  • -
  • -

Data Generation Capacity

  • Name SupplierConfirm that the product can generate data continuously and in real-time (y/n)
  • Fazua Yes
  • -
  • -
  • -

Data storage

  • Name Supplierproduct stores data on the device or a remote server (local / remote / both / not applicable)
  • Fazua Both
  • -
  • -
  • -

Data storage

  • Name Supplierretention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription)
  • Fazua Server Log Files: 7 days Personal and Ride Data: Until end of subscription
  • -
  • -
  • -

Access and Management of Data

  • Name SupplierRequest 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 "*Users can access data: yes *Users can retrieve data: yes *Users can delete data: yes *Technical means Users: via Email *Terms of Use: https://fazua.com/en/company/privacy-policy-fazua-app/ *Website: https://fazua.com/de/support/contact/"
  • -
  • -
  • -
Data specifications of the connected product
Data specifications of the connected product
Data specifications of the connected product
Data Generation Capacity
Data storage
Data storage
Access and Management of Data
Name Supplier
Type of device
Category
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 *Terms of Use: https://fazua.com/en/company/privacy-policy-fazua-app/ *Website: https://fazua.com/de/support/contact/"
-
-
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 SupplierType of device
  • Enviolo Automatic Hub Interface
  • -
  • -

  • Name SupplierCategory
  • Enviolo Telemetry
  • System
  • Device meta data

Data specifications of the connected product

  • Name SupplierType example (all types of generated data, e.g. mileage, battery range)
  • Enviolo Total distance, speed, cadance
  • hub and motortype, CAN protocol, error flags, assistant behavior settings
  • Identifiers and versions of the hardware and firmware, bike details

Data specifications of the connected product

  • Name Supplierformat (format used to share data with User or Third Parties, e.g. CSV / Excel / Json)
  • Enviolo "*.csv export available on demand Direct access via enviolo App (Available via Apple or Google Play Store)"
  • -

Data specifications of the connected product

  • Name Supplierestimated volume of data generated (frequency of sampling and/or publishing)
  • Enviolo 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 Generation Capacity

  • Name SupplierConfirm that the product can generate data continuously and in real-time (y/n)
  • Enviolo Data is collected, but data sharing is only enabled via enviolo App Bluetooth connection
  • -
  • -

Data storage

  • Name Supplierproduct stores data on the device or a remote server (local / remote / both / not applicable)
  • Enviolo Data gets stored on the device and gets synced with Backend upon connection with the enviolo App
  • -
  • -

Data storage

  • Name Supplierretention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription)
  • Enviolo Data is retained as long as the device has memory space
  • -
  • -

Access and Management of Data

  • Name SupplierRequest 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 "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: https://enviolo.com/privacy/ Website: www.enviolo.com"
  • -
  • -
Data specifications of the connected product
Data specifications of the connected product
Data specifications of the connected product
Data Generation Capacity
Data storage
Data storage
Access and Management of Data
Name Supplier
Type of device
Category
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: https://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
-
-
-
-
-

3. What data is collected by Royal Dutch Gazelle

Depending on your bike model and setup, we may collect the data as provided in the table below by activating the Royal Dutch Gazelle 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 Royal Dutch Gazelle 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.

  • Name SupplierComponents
  • ComoduleV10
  • ComoduleBnC CAN-less
  • ComoduleOld HW9
  • ComoduleB&C
  • ComoduleB&C Bafang

Data specifications of the connected product

  • Name SupplierType (all types of generated data, e.g. mileage, battery range)
  • Comoduletimestamp iot_charging_status iot_battery_soc iot_battery_voltage iot_battery_temperature iot_input_voltage iot_movement_status gnss_latitude gnss_longitude gnss_pdop_avg gnss_pdop gnss_known_satellites gnss_used_satellites gnss_cno_median gnss_cno_4th gnss_cno_max gnss_valid (gnss_fix_status) gnss_fix_since_reset cellular_signal_strength cellular_signal_rsrq cellular_signal_rsrp cellular_connection_status cellular_network_type charging_state battery_soc battery_soh battery_cycles battery_capacity_total battery_capacity_remining battery_temperature_max battery_temperature_min motor_temperature speed pedal_cadence pedal_torque motor_power pedal_power assist_level movement_status light_status total_distance battery_voltage gnss_odometer
  • Comoduletimestamp charger_status como_vin speed total_distance small_bat_soc small_bat_voltage small_bat_temp avg_gps_hdop gps_hdop gps_fix_status gps_sats gps_used_stats gps_med_cno gps_4th_cno gps_max_cno gps_valid gps_fix_received gsm_asu* gsm_status* gsm_op_code gsm_state gsm_reg_e_code gps_lat gps_lon
  • Comoduletimestamp light_status assist_level charging_status voltage state_of_charge encoded_signal_strength speed distance range small_bat_soc small_bat_voltage small_bat_temp avg_gps_hdop gps_hdop gps_lat gps_lon
  • Comoduletimestamp light_status assist_level charging_status 1st bike battery voltage 1st bike battery SoC speed total_distance range backup_battery_state_of_charge backup_battery_voltage backup_battery_temperature avg_gps_hdop gps_hdop reserved 2nd bike battery SoC 2nd bike battery voltage gps_sats gps_used_stats gps_med_cno gps_4th_cno gps_max_cno gps_valid gps_fix_received gsm_asu* gsm_status* gsm_op_code gsm_state gsm_reg_e_code gps_lat gps_lon
  • Comoduletimestamp 1st bike battery SoC speed 1st bike battery voltage assist_level light_status backup_battery_state_of_charge backup_battery_voltage backup_battery_temperature gsm_asu* gps_valid gsm_status* - gps_hdop gps_lat gps_lon

Data specifications of the connected product

  • Name Supplierformat (format used to share data with User or Third Parties, e.g. CSV / Excel / Json)
  • ComoduleJson
  • ComoduleJson
  • ComoduleJson
  • ComoduleJson
  • ComoduleJson

Data specifications of the connected product

  • Name Supplierestimated volume of data generated (frequency of sampling and/or publishing)
  • ComoduleData points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes
  • ComoduleData points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes
  • ComoduleData points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes
  • ComoduleData points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes
  • ComoduleData points sampled on device every 10 seconds, sending sampled data to cloud every 4 minutes

Data Generation Capacity

  • Name SupplierConfirm that the product can generate data continuously and in real-time (y/n)
  • ComoduleThe module samples the data on the device and sends it if it has connection to the cloud every 4 minutes
  • ComoduleThe module samples the data on the device and sends it if it has connection to the cloud every 4 minutes
  • ComoduleThe module samples the data on the device and sends it if it has connection to the cloud every 4 minutes
  • ComoduleThe module samples the data on the device and sends it if it has connection to the cloud every 4 minutes
  • ComoduleThe module samples the data on the device and sends it if it has connection to the cloud every 4 minutes

Data storage

  • Name Supplierproduct stores data on the device or a remote server (local / remote / both / not applicable)
  • ComoduleBoth (local only temporary until offloaded to the cloud)
  • ComoduleBoth (local only temporary until offloaded to the cloud)
  • ComoduleBoth (local only temporary until offloaded to the cloud)
  • ComoduleBoth (local only temporary until offloaded to the cloud)
  • ComoduleBoth (local only temporary until offloaded to the cloud)

Data storage

  • Name Supplierretention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription)
  • Comoduleuntil end of the subscription via the app
  • Comoduleuntil end of the subscription via the app
  • Comoduleuntil end of the subscription via the app
  • Comoduleuntil end of the subscription via the app
  • Comoduleuntil end of the subscription via the app

Access and Management of Data

  • Name SupplierRequest 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
  • ComoduleUsers can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via API or platform Terms of Use: [insert link] Website: [insert website]
  • ComoduleUsers can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via API or platform Terms of Use: [insert link] Website: [insert website]
  • ComoduleUsers can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via API or platform Terms of Use: [insert link] Website: [insert website]
  • ComoduleUsers can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via API or platform Terms of Use: [insert link] Website: [insert website]
  • ComoduleUsers can access data: yes Users can retrieve data: yes Users can delete data: yes Technical means Users: via API or platform Terms of Use: [insert link] Website: [insert website]
Data specifications of the connected product
Data specifications of the connected product
Data specifications of the connected product
Data Generation Capacity
Data storage
Data storage
Access and Management of Data
Name Supplier
Components
Type (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
V10
timestamp iot_charging_status iot_battery_soc iot_battery_voltage iot_battery_temperature iot_input_voltage iot_movement_status gnss_latitude gnss_longitude gnss_pdop_avg gnss_pdop gnss_known_satellites gnss_used_satellites gnss_cno_median gnss_cno_4th gnss_cno_max gnss_valid (gnss_fix_status) gnss_fix_since_reset cellular_signal_strength cellular_signal_rsrq cellular_signal_rsrp cellular_connection_status cellular_network_type charging_state battery_soc battery_soh battery_cycles battery_capacity_total battery_capacity_remining battery_temperature_max battery_temperature_min motor_temperature speed pedal_cadence pedal_torque motor_power pedal_power assist_level movement_status light_status total_distance battery_voltage gnss_odometer
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 Terms of Use: [insert link] Website: [insert website]
Comodule
BnC CAN-less
timestamp charger_status como_vin speed total_distance small_bat_soc small_bat_voltage small_bat_temp avg_gps_hdop gps_hdop gps_fix_status gps_sats gps_used_stats gps_med_cno gps_4th_cno gps_max_cno gps_valid gps_fix_received gsm_asu* gsm_status* gsm_op_code gsm_state gsm_reg_e_code gps_lat gps_lon
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 Terms of Use: [insert link] Website: [insert website]
Comodule
Old HW9
timestamp light_status assist_level charging_status voltage state_of_charge encoded_signal_strength speed distance range small_bat_soc small_bat_voltage small_bat_temp avg_gps_hdop gps_hdop gps_lat gps_lon
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 Terms of Use: [insert link] Website: [insert website]
Comodule
B&C
timestamp light_status assist_level charging_status 1st bike battery voltage 1st bike battery SoC speed total_distance range backup_battery_state_of_charge backup_battery_voltage backup_battery_temperature avg_gps_hdop gps_hdop reserved 2nd bike battery SoC 2nd bike battery voltage gps_sats gps_used_stats gps_med_cno gps_4th_cno gps_max_cno gps_valid gps_fix_received gsm_asu* gsm_status* gsm_op_code gsm_state gsm_reg_e_code gps_lat gps_lon
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 Terms of Use: [insert link] Website: [insert website]
Comodule
B&C Bafang
timestamp 1st bike battery SoC speed 1st bike battery voltage assist_level light_status backup_battery_state_of_charge backup_battery_voltage backup_battery_temperature gsm_asu* gps_valid gsm_status* - gps_hdop gps_lat gps_lon
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 Terms of Use: [insert link] Website: [insert website]

4. How to access your data

You can access your data via our [Developer Portal]. Log in with your account to view the bikes linked to you. For each bike you own, you can 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:

Contact us directly at klantenservice@gazelle.nl

We'll process your request as quickly as possible.

7. More questions?

Check our FAQ or contact our support team. We’re happy to help!