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 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. Royal Dutch Gazelle does not store this data. To access or manage this information, please refer directly to their platforms:
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
- Bosch Drive train
- Bosch Drive train
- Bosch Drive train
- Name SupplierCategory
- Bosch Telemetry
- Bosch Battery
- Bosch System
- Bosch 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
- Bosch State of charge, bike light, charger connected
- Bosch Firmware versions, identification bike, OEM, system locked
- Bosch 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
- Bosch Json via Bosch SDK
- Bosch Json via Bosch SDK
- 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
- Bosch Data is realtime, amount of data depends amount of cycling
- Bosch Data is realtime, amount of data depends amount of cycling
- 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
- Bosch Yes
- Bosch Yes
- 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
- Bosch On device, shared via Bluetooth or cable
- Bosch On device, shared via Bluetooth or cable
- 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
- Bosch Unknown
- Bosch Unknown
- 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 Website: https://www.bosch-ebike.com/
- 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 Website: https://www.bosch-ebike.com/
- 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 Website: https://www.bosch-ebike.com/
- 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 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 Website: https://www.bosch-ebike.com/
Bosch
Drive train
Battery
State of charge, bike light, charger connected
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 Website: https://www.bosch-ebike.com/
Bosch
Drive train
System
Firmware versions, identification bike, OEM, system locked
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 Website: https://www.bosch-ebike.com/
Bosch
Drive train
Device meta data
service dates due, activity, walkassits
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 Website: https://www.bosch-ebike.com/
Fazua
- Name SupplierType of device
- Fazua Drive train and app
- Fazua Drive train and app
- Fazua Drive train and app
- Fazua Drive train and app
- Name SupplierCategory
- Fazua Telemetry
- Fazua Battery
- Fazua System
- Fazua 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
- Fazua State of charge, bike light, charger connected
- Fazua Firmware versions, technical data of the bike display, battery and drive train
- Fazua 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
- Fazua CSV or Excel
- Fazua CSV or Excel
- 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.
- 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.
- 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.
- 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
- Fazua Yes
- Fazua Yes
- Fazua Yes
Data storage
- Name Supplierproduct stores data on the device or a remote server (local / remote / both / not applicable)
- Fazua Both
- Fazua Both
- Fazua Both
- 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
- Fazua Server Log Files: 7 days Personal and Ride Data: Until end of subscription
- Fazua Server Log Files: 7 days Personal and Ride Data: Until end of 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/
- 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/
- 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/
- 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/
Fazua
Drive train and app
Battery
State of charge, bike light, charger connected
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/
Fazua
Drive train and app
System
Firmware versions, technical data of the bike display, battery and drive train
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/
Fazua
Drive train and app
Device meta data
User ID, app version, user type, bike serial number
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/
Enviolo
- Name SupplierType of device
- Enviolo Automatic Hub Interface
- Enviolo Automatic Hub Interface
- Enviolo Automatic Hub Interface
- Name SupplierCategory
- Enviolo Telemetry
- Enviolo System
- Enviolo 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
- Enviolo hub and motortype, CAN protocol, error flags, assistant behavior settings
- Enviolo 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)
- Enviolo *.csv export available on demand Direct access via enviolo App (Available via Apple or Google Play Store)
- 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
- 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
- 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
- Enviolo Data is collected, but data sharing is only enabled via enviolo App Bluetooth connection
- 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
- Enviolo Data gets stored on the device and gets synced with Backend upon connection with the enviolo App
- 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
- Enviolo Data is retained as long as the device has memory space
- 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
- 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
- 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
Enviolo
Automatic Hub Interface
System
hub and motortype, CAN protocol, error flags, assistant behavior settings
*.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
Enviolo
Automatic Hub Interface
Device meta data
Identifiers and versions of the hardware and firmware, bike details
*.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
Shimano
- Name SupplierType of device
- Shimano E-bike system, Hub, Di2 components
- Shimano E-bike system, Hub, Di2 components
- Shimano E-bike system, Hub, Di2 components
- Name SupplierCategory
- Shimano Telemetry
- Shimano System
- Shimano Device meta data
Data specifications of the connected product
- Name SupplierType example (all types of generated data, e.g. mileage, battery range)
- Shimano Riding related data
- Shimano Fault related data, usage history non personal data
- Shimano Device setting data
Data specifications of the connected product
- Name Supplierformat (format used to share data with User or Third Parties, e.g. CSV / Excel / Json)
- Shimano The product cannot provide data directly to users or third parties.
- Shimano The product cannot provide data directly to users or third parties.
- Shimano The product cannot provide data directly to users or third parties.
Data specifications of the connected product
- Name Supplierestimated volume of data generated (frequency of sampling and/or publishing)
- Shimano This product does not generate the relevant data at predetermined timing or intervals.
- Shimano This product does not generate the relevant data at predetermined timing or intervals.
- Shimano This product does not generate the relevant data at predetermined timing or intervals.
Data Generation Capacity
- Name SupplierConfirm that the product can generate data continuously and in real-time (y/n)
- Shimano n
- Shimano n
- Shimano n
Data storage
- Name Supplierproduct stores data on the device or a remote server (local / remote / both / not applicable)
- Shimano On the product (No data will be transferred to a remote server unless the user utilizes a separate app or equivalent software.)
- Shimano On the product (No data will be transferred to a remote server unless the user utilizes a separate app or equivalent software.)
- Shimano On the product (No data will be transferred to a remote server unless the user utilizes a separate app or equivalent software.)
Data storage
- Name Supplierretention period (how long is the data retained, i.e. days/week/month or untill termination of the subscription)
- Shimano The relevant data is stored on the product until it is updated.
- Shimano The relevant data is stored on the product until it is updated.
- Shimano The relevant data is stored on the product until it is updated.
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
- Shimano https://bike.shimano.com/
- Shimano https://bike.shimano.com/
- Shimano https://bike.shimano.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
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.
n
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.
https://bike.shimano.com/
Shimano
E-bike system, Hub, Di2 components
System
Fault related data, usage history non personal 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.
n
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.
https://bike.shimano.com/
Shimano
E-bike system, Hub, Di2 components
Device meta data
Device setting 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.
n
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.
https://bike.shimano.com/
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 ourPrivacy Statement.
- Name SupplierType of device
- ComoduleIoT module
- ComoduleIoT module
- ComoduleIoT module
- ComoduleIoT module
- ComoduleIoT module
- ComoduleIoT module
- Name SupplierCategory
- ComoduleTelemetry
- ComoduleLocation
- ComoduleBattery
- ComoduleNetwork
- ComoduleSystem
- ComoduleDevice meta data
Data specifications of the connected product
- Name SupplierType (all types of generated data, e.g. mileage, battery range)
- ComoduleSpeed, cadance, distance
- ComoduleGPS coordinates during rides, Latitude and longitude
- Comodulestate of charge, battery performance
- Comodulesignal strenght, signal quality, network connection
- Comodulemovement detection, range
- ComoduleTimestamp, GPS validation
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
- 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
- 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
- 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)
- 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
- 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 Website: https://consumer-account.pon.bike/
- ComoduleUsers 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/
- ComoduleUsers 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/
- ComoduleUsers 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/
- ComoduleUsers 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/
- ComoduleUsers 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/
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 (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/
Comodule
IoT module
Location
GPS coordinates during rides, Latitude and longitude
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/
Comodule
IoT module
Battery
state of charge, battery performance
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/
Comodule
IoT module
Network
signal strenght, signal quality, network connection
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/
Comodule
IoT module
System
movement detection, range
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/
Comodule
IoT module
Device meta data
Timestamp, GPS validation
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/
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?
Check our FAQ or contact our support team. We’re happy to help!