EU Data Act Notice

Version: v1.0 · Effective Date: 2026-07-14

This Notice is provided in accordance with the EU Data Act (Regulation (EU) 2023/2854) (the "EU Data Act").

1. Data Holder Information

Data Holder:Shenzhen Hohem Technology Co., Ltd. (hereinafter referred to as "We" or "Us").
Registered Address:B106, Building 2, Jiuxianglin Industrial Park, 4227 Xili Lake Road, Xili Street, Nanshan, Shenzhen City, Guangdong, China

We act as the data holder under the EU Data Act for the connected products described below.

2. Connected Products Overview

Connected Product means an item that obtains, generates or collects data concerning its use or environment and that is able to communicate product data via an electronic communications service, physical connection or on-device access, and whose primary function is not the storing, processing or transmission of data on behalf of any party other than the user.

We offer the following connected products:

  • phone stabilizer
  • camera stabilizer
  • Microphone
  • pocket camera

The functions of these connected products, as well as details regarding the data they generate and how it is handled, are described in the following sections of this notice.

3. Data Generated/Collected by Connected Products

Data NameData DescriptionData SourceData FormatEstimated VolumeContinuous Real-time GenerationStorage LocationStorage Duration
Bluetooth Device Name Advertised BLE name of the connected gimbal Gimbal Device String ~20 bytes No Device-side; Cloud Until actively cleared by user
Activation Status Whether the gimbal has been activated for warranty Gimbal Device Boolean ~4 bytes No Not stored Not stored
Boot Name / Boot Type Bootloader identity information Gimbal Device String ~10 bytes No Not stored Not stored
Battery Level Gimbal battery percentage derived from voltage Gimbal Device Int/Float 4 bytes Yes Not stored Not stored
Battery Charge State Cell count and charging status Gimbal Device Int/Boolean ~4 bytes Yes Not stored Not stored
Motor Angles (Tilt/Roll/Pan) Gimbal axis rotation angles from IMU/encoders Gimbal Device Float x3 12 bytes/packet Yes Not stored Not stored
Encoder Angles Per-axis encoder readings Gimbal Device Float x3 12 bytes/packet Yes Not stored Not stored
Motor Torque Per-axis motor torque/moment values Gimbal Device Int x3 6 bytes/packet Yes Not stored Not stored
Work Mode Current stabilization mode Gimbal Device Byte enum 2 bytes Yes Device-side (on gimbal) Until changed on gimbal
Motor Response Stabilization tuning parameters per axis Gimbal Device Byte/Int ~10 bytes No Device-side (on gimbal) Until changed on gimbal
Joystick Settings LR/UD reverse, speed, axis mapping preferences Gimbal Device Bytes ~10 bytes No Device-side (on gimbal) Until changed on gimbal
Smart Roll / Scene Mode Gimbal behavior and scene mode flags Gimbal Device Bytes ~4 bytes Yes Not stored Not stored
AI Module Online Status Whether AI tracker module is active Gimbal Device Boolean 1 bit Yes Not stored Not stored
Remote Connection Status Wireless remote controller connection state Gimbal Device Boolean 1 bit Yes Not stored Not stored
Axis Fine Adjustments Tilt/pan/roll trim calibration values Gimbal Device Bytes ~6 bytes No Device-side (on gimbal) Until recalibration
Motion-lapse Settings A/B duration and Inception spin parameters Gimbal Device Int/Byte ~4 bytes No Not stored Not stored
Firmware Binary (OTA) Firmware image streamed during over-the-air upgrade Gimbal Device Binary 160KB/upgrade No Not stored Deleted after upgrade
GPS Latitude/Longitude Smartphone GPS coordinates for activation and SN reporting Mobile App Double pair 16 bytes Yes Cloud Cloud: persistent
Reverse-geocoded Address Country, city, street derived from GPS coordinates Mobile App String ~200 bytes No Cloud Cloud: persistent
Network IP Address Local/Wi-Fi IP address at time of SN report Mobile App String ~15 bytes No Cloud Cloud: persistent
Game Rotation Vector Phone orientation quaternion for motion control Mobile App Float[4] 16 B @ ~20 Hz Yes Not stored Not stored
Accelerometer / Gyroscope / Magnetometer Sensor data for spirit level UI in camera mode Mobile App Float arrays 64 bytes Yes Not stored Not stored
GPS EXIF in Media Latitude/longitude embedded in photo/video metadata Mobile App EXIF GPS tags ~50 bytes/file No Device-side Until user deletes
App Logs Diagnostic log files Mobile App Text (.txt) 1-70 MB total Yes Device-side 30 days
User Account ID Hohem account identifier Mobile App String ~10 bytes No Device-side; Cloud Until account deletion
User Profile Account nickname, avatar, and bio Mobile App String/URL ~1 KB No Device-side; Cloud Until account deletion
Phone / Email Login identifiers and contact information Mobile App String ~50 bytes No Device-side; Cloud Until account deletion
Bound Gimbal List SN, BLE name, and product type per bound gimbal Gimbal + Mobile App JSON ~200 B/device No Cloud Until unbind or account deletion
SN Report Payload Data sent on connect Gimbal + Mobile App JSON ~200 bytes No Cloud Persistent
Activation Report Data for warranty activation Gimbal + Mobile App Form POST ~300 bytes No Cloud Persistent
Feedback Attachments User-submitted issue files Mobile App Multipart/ZIP Up to user selection No Device-side; Cloud Device-side: until cleared; Cloud: persistent
Crash Reports App crash stack traces Mobile App Crash bundle 10-100 KB/crash No Cloud 7 days
Network Connection Status Wi-Fi/cellular connectivity state for log upload Mobile App Boolean 1 byte Yes Not stored Not stored
Language Preference App display language setting Mobile App String ~10 bytes No Not stored Not stored
Face Bounding Boxes Face detection rectangles Mobile App Coordinate array ~100 bytes/frame Yes Not stored Not stored
Face Landmarks Face keypoint coordinates Mobile App Float array ~1 KB/frame Yes Not stored Not stored
Person/Object Tracking Rectangles Person and object tracking Mobile App Coordinate array ~100 bytes/frame Yes Not stored Not stored
Gesture Recognition Data Hand gesture classification IDs Mobile App Int enum ~4 bytes/event Yes Not stored Not stored
Track Coordinates to Gimbal AI tracking coordinates sent to gimbal Mobile App → Gimbal Device Int pair ~8 bytes/packet Yes Not stored Not stored
AI Camera Preview Stream Camera preview frames Mobile App YUV/RGB video frames ~300 KB/frame Yes Not stored Not stored
Community Auth Tokens Access/refresh tokens for community Mobile App String ~200 bytes No Device-side; Cloud Until logout or account deletion
WeChat OAuth Identifier WeChat openid and access token Mobile App String ~100 bytes No Cloud Until account unbinding
User Profile Gender / Country User gender and country/region Mobile App String ~50 bytes No Device-side; Cloud Until account deletion
Tutorial Search History Locally stored community tutorial search keywords Mobile App String list ~1 KB No Device-side Until user clears or app data cleared

Data means any digital representation of acts, facts or information and any compilation of such acts, facts or information, including in the form of sound, visual or audio-visual recording.

4. User Data Access, Erasure and Portability

Individuals or legal entities using our Connected Products (hereinafter referred to as "Users") have the right, in accordance with the EU Data Act, to request access to, erasure of, or portability of data generated/collected by Connected Products.

These requests can be submitted via [9. Contact and Data Request Channel].

5. Data Sharing and Compliance with Requests for Data

Data generated by our Connected Products may be shared with third parties under Articles 4 to 7 of the EU Data Act, applicable to the following requesters:

5.1 Business-to-Business (B2B) Access Requests

  • Exclusively based on the User's explicit consent;
  • Contracts shall specify: Purpose limitation, Confidentiality obligations, Data security measures, Prohibition of misuse.

5.2 Business-to-Government (B2G) Access Requests

Based on Article 14-18 of EU Data Act, data may be shared with public authorities:

  • Permitted under Article 15 for emergencies or legitimate public tasks (e.g., natural disasters, public safety, pandemics);
  • Data transmitted via encrypted secure channels with strict purpose binding;
  • Government entities must submit formal written requests with access logging;
  • Data minimisation principle applies to all shared datasets.

5.3 Third Parties Requests Submission

Third parties may submit formal requests through [9. Contact and Data Request Channel].

6. Data Security and Protection Mechanism

To ensure security of data generated by Connected Products manufactured by Shenzhen Hohem Technology Co., Ltd., we implement the following technical and organizational safeguards throughout the processes of data transmission, storage, and access:

  • Implement full security encryption during storage and transmission to prevent data from unauthorised access, use or disclosure (such as by using SSL to encrypt many Services).
  • Regularly review practices regarding data collection, storage and processing (including physical security measures) to prevent unauthorised access to or tampering with our various systems and data.
  • Establish access rights management mechanism to authorize only necessary personnel to access data.
  • Conduct security and privacy protection training, testing and other activities to enhance employee awareness of and proficiency in data protection.
  • Use international and industry-recognised standards to protect your data and actively pursue relevant security and privacy protection accreditation.

7. Interoperability Notes

We ensure that the recipient can process the data in a structured, commonly used and machine-readable format in order to comply with the interoperability requirements of Articles 33 of the EU Data Act.

8. Data Use Restrictions and Prohibited Purposes

Without hohem's express written authorization or, unless legally required, data shall not be used for the following purposes:

  • Development of competing products;
  • Reverse engineering of algorithms;
  • Targeted advertising or profiling of users.

Any breach of these restrictions may result in legal consequences and revocation of access.

9. Contact and Data Request Channel

Service channel Email
European Union region jolly.tan@hohem-tech.com

10. Policy Updates

This policy will be updated regularly based on legal requirements and business needs. All updates will be announced through our official website and related channels.