Dina data, din cykeltur, din kontroll
Hos Royal Dutch Gazelle kan smarta komponenter på din cykel samla in data för att göra dina turer bättre, säkrare och roligare. På den här sidan kan du läsa om vilka data vi samlar in, hur vi använder dem och hur du behåller kontrollen. Det är trots allt din cykel - och dina data.
1. Varför vi samlar in data
Vi använder turdata för att förbättra cykelns prestanda, analysera användningen och erbjuda praktiska funktioner som turhistorik, stöldskydd och att återfinna stulna cyklar.
2. Vilka komponenter samlar in data
Royal Dutch Gazelle använder en rad smarta komponenter. Beroende på modell kan din Gazelle-cykel innehålla några av dessa. För att se exakt vilka komponenter som finns på din cykel kan du titta i produktöversikten för din specifika modell.
Vi skiljer mellan:
A. Komponenter anslutna till Pon.Bike-plattformen
För dessa komponenter samlar och lagrar Royal Dutch Gazelle data, som du kan se via vår utvecklarportal och API:
GPS-moduler
Comodule BnC
Comodule Guardian
Comodule Master Module
Data från dessa komponenter hanteras i enlighet med denna datapolicy och, i tillämpliga fall, sekretesspolicy.
B. Komponenter anslutna till en tredjepartsplattform
För följande komponenter kan data samlas in av respektive tillverkare. Royal Dutch Gazelle lagrar inte dessa data. För att se eller hantera denna information hänvisar vi dig direkt till deras plattformar:
Drivetrain
Smart shifter
Av sekretess-, juridiska och tekniska skäl har Royal Dutch Gazelle inte tillgång till data från dessa system.
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/
- -
- -
- -
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/"
- -
- -
- -
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"
- -
- -
3. Vilka data samlas in av Royal Dutch Gazelle
Beroende på din cykelmodell och konfiguration kan vi samla in de data som anges i tabellen nedan genom att aktivera Gazelle-appen. En fullständig och mer detaljerad översikt över de insamlade data hittar du i [utvecklarportalen].
Översikt över genererade data
De data som behandlas av Royal Dutch Gazelle kan betraktas som personuppgifter, såsom platsdata (i händelse av förlust eller stöld). De genererade data behandlas i enlighet med denna EU Data Act-deklaration och, i den mån det rör personuppgifter, i enlighet med integritetspolicyn. För mer information hänvisar vi till vår integritetspolicy.
- 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]
4. Hur du får tillgång till dina data
Du kan få tillgång till dina data via vår [Utvecklarportal]. Logga in med ditt konto för att se de cyklar som är kopplade till dig. För varje cykel du äger kan du via ett API se dina data och ge eller återkalla åtkomst till tredje part. Du kan få tillgång till dina data (nästan) i realtid via MQTT-strömmen, som är tillgänglig via utvecklarportalen. Kodexempel finns tillgängliga på [utvecklarportalen].
5. Hur du kan få dina data raderade
För att permanent radera dina data:
Kontakta oss direkt via kontaktformuläret på vår webbplats. Vi behandlar din begäran så snart som möjligt.
6. Fler frågor?
Kolla in vår FAQ eller kontakta vår kundtjänst. Vi hjälper dig gärna!