Aqube Outdoor Privacy Policy

Last updated: September 28, 2026Effective date: September 28, 2026

1. Introduction and scope

Suzhou HyECO Smart Co.Ltd (“we,” “us,” or “our”) values the security of your personal information and privacy. This Policy explains how we collect, use, store, share, transfer, publicly disclose, and protect your personal information, and how you may exercise your rights, when you use the Aqube Outdoor mobile application, consumer Web application, installer Web application, related device connectivity, cloud services, and customer support.

This Policy applies to the account, garden collaboration, smart-device control, installation services, diagnostic support, and other functions currently provided by Aqube Outdoor. Products or services independently provided by third parties are governed by their own privacy rules, which we will identify where appropriate.

Please read this Policy carefully before using the Services. We will highlight sensitive personal information, device permissions, and matters that may materially affect your rights by bold text, a separate notice, or another prominent method, and will obtain separate consent where required by law.

2. Principles for processing personal information

We follow the principles of lawfulness, legitimacy, necessity, and good faith. We process only the minimum information directly relevant to clear and reasonable service purposes and apply security measures appropriate to the relevant risks.

If information or a permission is not necessary for a core function, you may refuse to provide it or withdraw your authorization. Refusal or withdrawal will affect only the relevant function and will generally not affect unrelated functions.

3. How we collect and use personal information

3.1 Account registration, sign-in, and security verification

To create and manage accounts, sign you in, send verification codes, recover passwords, and protect account security, we may process:

Email address;
Security-verification information relating to your password;
Email verification codes, verification status, and password-reset status;
Sign-in time, session identifiers, account status, and necessary security logs;
Account identifiers and verification information for other sign-in methods when those methods are actually made available.

The current product primarily uses email for registration and sign-in. We will not collect your phone number merely because an interface placeholder exists, unless that function is actually launched and clearly disclosed.

3.2 Account profile

To display your profile and help members identify one another, we may process the display name and avatar you choose, together with the email address or telephone number associated with your account.

3.3 Gardens, areas, and member collaboration

To create garden spaces, organize devices, and enable member collaboration, we may process:

Garden name, garden code, time zone, and an address you voluntarily provide;
Area names, ordering, and associations with devices;
Member account identifiers, display names, avatars, roles, and permissions;
Records of invitations, joining, member removal, and permission changes;
The initiator, recipient, status, and protection-period information for ownership transfers.

Garden owners and other authorized members may view garden, member, and device information within the scope of their permissions. Invite only people you trust and promptly revoke permissions that are no longer needed.

3.4 Installation services and organization information

If you use installation-service functions, we may process:

The account type, organization name, and contact person of an installer or installation organization;
Service email, service telephone number, service area, and organization logo;
Customer display name, installation or service records, and handover status;
Garden and device information needed to complete installation, commissioning, after-sales service, and ownership handover.

Installers should access relevant data only with the user’s authorization and to the extent necessary to provide the service.

3.5 Adding, connecting, controlling, and maintaining devices

To identify, connect, bind, control, and maintain lights, light strips, multi-channel controllers, irrigation controllers, and their child devices, we may process:

Device name, type, model, firmware information, and capabilities;
Serial number, MAC address, device identifier, Thing ID, binding relationship, and device metadata;
Online status, power state, brightness, color, color temperature, channel state, valve state, and other device state;
Control instructions, execution status, error information, creation and acknowledgement times, and lifecycle-operation records;
Cached basic device information, including device time zone and, only where the relevant function is enabled, longitude, latitude, altitude, and country or region code associated with the device or installation location.

Precise location may be sensitive personal information. If precise-location functionality is enabled in the future, we will explain its purpose, method, and impact before collection and obtain separate consent as required by law.

3.6 Scenes, groups, schedules, and irrigation

To provide automation and device-management functions, we may process:

Device groups, scene names, actions, ordering, and member devices;
Schedules, time zones, recurrence rules, enabled state, and execution records;
DIY lighting effects, color parameters, speed, and other effect settings;
Irrigation programs, zones, durations, schedules, run history, and device feedback.

Depending on the device type and implementation, these settings may be stored in the cloud, on the device, or locally on your terminal.

3.7 Wi-Fi provisioning information

When provisioning a device over Bluetooth or a local network, the application may read the current Wi-Fi network name (SSID) and ask you to enter the Wi-Fi password so that the network credentials can be delivered to the device being configured.

Under the current implementation:

The Wi-Fi password is used only for the current provisioning process;
The Wi-Fi password is not written to the Aqube Outdoor business database;
The Wi-Fi password is not written to diagnostic logs;
Password fields in logs are redacted or blocked.

Do not expose your provisioning password to others in public or untrusted environments.

3.8 Microphone and music-responsive lighting

When you actively enable music-responsive lighting or a similar feature, the application requests microphone permission, analyzes rhythm or audio features locally, and sends the necessary feature parameters to a connected device to create lighting effects.

Under the current implementation, raw audio is neither recorded nor uploaded to our servers. Analysis stops when you leave the feature, the application enters a state in which processing should not continue, or you withdraw permission.

3.9 Camera and photos

When you actively scan a code to add a device, the application requests camera permission to recognize the QR code. When you set a photo for an irrigation-valve zone, the application may request camera or photo-library access.

Under the current implementation, valve-zone photos are copied to the application’s local file directory and referenced in the local database. They are not automatically uploaded to the cloud. When a related zone or device is deleted, the application attempts to remove the corresponding local photo files.

3.10 Bluetooth, nearby devices, local network, and current network information

To discover, connect, configure, and control nearby smart devices, the application may request Bluetooth, nearby-device, local-network, or current-Wi-Fi-related system permissions.

In the current iOS permission descriptions, location-related permission is used only to obtain current Wi-Fi information. Under the current implementation, the phone’s real-time location is not stored or uploaded for this purpose. Different operating-system versions may classify scanning for nearby Wi-Fi or Bluetooth devices as location or nearby-device access; the system prompt controls the exact classification.

3.11 Local device PINs and security credentials

Some local devices may require a PIN or another connection credential. Under the current implementation, these credentials are stored on the current terminal using the operating system’s secure credential storage. The local database stores only an alias or reference, not the plaintext credential. The application attempts to remove the corresponding secure credential when a device is deleted.

3.12 Local cache and offline data

To support offline viewing, improve responsiveness, and perform local control, the application may store the following locally on your terminal:

Device and endpoint information and state snapshots;
Local scenes, groups, schedules, and DIY configurations;
Irrigation zones, programs, and history;
Offline workspace cache and synchronization state;
Language settings, account sessions, temporary verification state, pending installer-activation state, and demo data.

Signing out does not necessarily remove all local device data. You may use available product deletion or cleanup functions, operating-system cleanup, or uninstall the application. Contact us if you need assistance.

3.13 Diagnostic logs and customer support

To troubleshoot connection, synchronization, and device-control problems, the application may create redacted diagnostic logs locally, including time, module, event type, error code, the minimum necessary device or request identifier, and runtime state.

Under the current implementation:

Regular diagnostic logs are retained locally for up to approximately 7 days or are rotated when they reach approximately 10 MB;
Detailed diagnostic mode lasts for no more than approximately 15 minutes by default;
You may actively clear or export logs;
Exported logs may be saved to the Android Downloads directory or the Files application on iPhone;
We receive an exported file only after you actively send it to customer support.

Before sending a diagnostic file, check whether it contains information you do not want to share.

3.14 Notifications

The current product code does not implement real remote push notifications. If push services are enabled in the future, we will update this Policy or the relevant list to identify the push provider, device identifiers, purposes, and opt-out method, and will obtain consent where required.

4. Device permission list

Permission	Use	May you refuse?	Current processing
Bluetooth and nearby devices	Discover, connect, configure, and control nearby devices	Yes	Refusal may make local Bluetooth connections and provisioning unavailable
Local network	Discover or connect to devices on the same network	Yes	Refusal may make some local-network control or discovery unavailable
Location or current Wi-Fi information	Obtain the current Wi-Fi name to assist provisioning	Yes	The current implementation does not store or upload the phone’s real-time location
Microphone	Analyze music rhythm locally and drive lighting effects	Yes	Raw audio is not stored or uploaded
Camera	Scan device QR codes and photograph valve zones	Yes	Used only when you actively invoke the function
Photos	Select a valve-zone photo	Yes	Currently stored in the application’s local directory and not automatically uploaded
Files or storage	Export diagnostic files and support certain Android versions	Yes	Used only when you actively export a file

You may withdraw permissions through the operating-system settings. The corresponding function may stop working after withdrawal, but withdrawal does not affect processing already lawfully completed on the basis of your authorization.

5. Legal bases for processing personal information

To the extent permitted by applicable law, we process personal information on one or more of the following bases:

Your consent or separate consent;
Necessity for entering into or performing a contract to which you are a party;
Necessity for complying with a legal duty or statutory obligation;
Necessity for responding to a public-health emergency or, in an emergency, protecting a person’s life, health, or property;
Processing, within a reasonable scope, information that you have made public or that has otherwise been lawfully disclosed;
Other circumstances provided by laws or administrative regulations.

If the purpose or method of processing or the categories of personal information change and renewed consent is legally required, we will obtain your consent again.

6. How we share, entrust processing of, transfer, and publicly disclose information

6.1 Sharing

We do not sell your personal information. We may share necessary information only in the following circumstances:

At your active choice or with your separate consent, with garden owners, members, or invited installers or installation organizations to the extent needed for collaboration;
With a device cloud platform or connector, to the extent needed for device binding, state synchronization, and control;
As required by laws, legal proceedings, or lawful requests from administrative or judicial authorities;
To protect the life, property, or other substantial lawful rights of you, other users, or the public, subject to applicable law.

6.2 Entrusted processing and service providers

We may entrust cloud infrastructure, identity verification, email delivery, operations, and customer-support providers to process information necessary to provide the Services. Contracts, security assessments, access controls, and other measures will restrict such providers to processing information only on our instructions.

The main technical capabilities currently involved in the code and architecture include:

HyecoSmart Project Runtime / AppBase, which provides project runtime, account, business-data, and related cloud capabilities;
HyecoSmart Device Cloud and Connector, which provide device identity, binding, state synchronization, and command forwarding;
The Supabase client and compatible backend capabilities used to connect to the configured project backend;
React Native and open-source components for Bluetooth, camera, image selection, local databases, secure credential storage, and related terminal functions.

The use of an open-source component does not itself mean that its developer receives your personal information. We use the technical capabilities above only to the extent necessary to provide the applicable functions and use contracts, access controls, and security measures to govern service providers that actually participate in processing personal information.

6.3 Transfer

If personal information is transferred as part of a merger, separation, restructuring, asset transfer, insolvency liquidation, or similar transaction, we will inform you of the recipient’s name and contact details and require the recipient to remain bound by this Policy. If the recipient changes the original processing purpose or method, it must obtain consent again as required by law.

6.4 Public disclosure

As a rule, we do not publicly disclose your personal information. If public disclosure is necessary, we will explain the purpose, information categories, and possible impact and obtain separate consent as required by law, unless otherwise provided by law.

7. Storage location and retention periods

7.1 Storage location

Aqube Outdoor account data, business data, device-cloud data, backups, and logs are stored in data centers located in the People’s Republic of China.

No enabled cross-border transfer arrangement for personal information has currently been identified. If personal information must be provided overseas in the future, we will complete the applicable security assessment, personal-information protection certification, standard contract, or other legally required procedure; inform you about the overseas recipient; and obtain separate consent where required.

7.2 Retention periods

We retain personal information only for the shortest period necessary to achieve the processing purpose, unless otherwise required by law. The principal retention periods are:

Information category	Retention rule
Account and authentication information	While the account exists; after a verified account-deletion request is accepted, related information in active systems is generally deleted or anonymized within 15 business days, and backup copies are cleared within a rolling period of up to 90 days, unless retention is required by law
Garden, member, device, and automation data	While the garden or device relationship exists and as needed to provide the Services; after deletion, unbinding, or account deletion, the data is generally cleared within 30 days, and backup copies are cleared within a rolling period of up to 90 days, unless retention is required by law
Installation service and handover records	3 years after the service relationship ends, or longer where necessary to resolve disputes or comply with legal duties
Cloud security and operation logs	Generally 180 days; this period may be extended where necessary for a security investigation, dispute resolution, or legal compliance
Local diagnostic logs	Approximately 7 days by default, or rotated after reaching approximately 10 MB
Detailed diagnostic mode	Up to approximately 15 minutes by default, after which the regular diagnostic level resumes
Valve-zone photos	Stored on the current terminal until you delete the relevant data, uninstall the application, or the system clears it; the application attempts cleanup when a device is deleted
Local device PIN	Stored in the current terminal’s secure credential area until the device is deleted, application data is cleared, or the application is uninstalled

When a retention period expires, we delete or anonymize the information. If immediate deletion is temporarily impossible for technical reasons, we stop processing the information except for storage and necessary security protection.

8. How we protect personal information

We apply security measures appropriate to the sensitivity and risk of the information, including:

Access controls, authentication, least privilege, and session management;
Appropriate secure storage for passwords and security credentials;
Redaction or blocking of passwords, tokens, and other sensitive fields in diagnostic logs;
Permission, state, or protection-period checks for important operations;
Access restrictions and security management for service personnel and entrusted processors;
Processes for detecting, responding to, and notifying security incidents.

No internet environment is absolutely secure. If personal information is or may be leaked, tampered with, or lost, we will take remedial measures and notify you and the competent authorities as required by law.

9. Your personal-information rights

To the extent provided by law, you may:

Access and copy your personal information;
Correct or supplement inaccurate or incomplete information;
Request deletion where the legal conditions are met;
Withdraw an authorization based on consent;
Restrict or object to specified processing;
Request an explanation of personal-information processing rules;
Where the legal conditions are met, request transfer of personal information to a processor you designate;
Delete your account;
Submit a complaint or report about our processing.

You may exercise some rights through profile, member, device, permission, or cleanup functions in the product, or contact us at info@aqubeiot.com.

To protect account and data security, we may require identity verification. We will respond within 15 business days after receiving the request and completing identity verification. We may lawfully refuse a request that is unreasonably repetitive, requires disproportionate technical effort, may harm another person’s lawful rights, or may otherwise be refused by law, and will explain the reason.

Please note:

Signing out is not the same as deleting your account;
Removing a device from the application is not the same as factory-resetting it and does not necessarily delete the device entity from an upstream device cloud;
You must delete exported diagnostic files from the system Downloads directory or Files application yourself;
Offline data on your terminal may need to be deleted using application cleanup, system cleanup, or application uninstallation.

10. Children’s personal information

Aqube Outdoor is primarily intended for adults and is not principally directed to children under 14 years of age.

If you are the guardian of a child under 14, do not allow the child to register for or use the Services without your consent and guidance. If we discover that we collected a child’s personal information without guardian consent, we will delete it or take other necessary measures as soon as legally required.

11. Automated decision-making, advertising, and profiling

Under the current implementation, we have not identified functionality for personalized advertising, commercial marketing profiles, or automated decision-making that has a material impact on individual rights. We have also not identified advertising, payment, or general behavioral-analytics SDKs.

If such capabilities are introduced in the future, we will update this Policy, explain the processing logic, impact, opt-out method, and applicable third parties, and obtain consent as required by law.

12. Updates to this Policy

We may update this Policy in response to changes in laws, product functionality, data-processing activities, or service providers.

For material changes affecting processing purposes, information categories, methods of use, sharing recipients, or your rights, we will provide notice through the application, a website announcement, email, or another appropriate method and obtain renewed consent where required by law.

The updated Policy will state its last-updated and effective dates. We will not use an update to reduce your statutory rights without appropriate notice.

13. Contact us

If you have a question, comment, complaint, or request concerning this Policy, our personal-information processing, or your rights, contact us as follows:

Personal information controller: Suzhou HyECO Smart Co.Ltd
Address: #12, Beiqian Lane, SIP, Suzhou, Jiangsu, China
Telephone: 0512-65632906
Fax: 0512-65632016
Email: info@aqubeiot.com
Response period: within 15 business days after receiving the request and completing identity verification

If you are dissatisfied with our response, you may also complain or report to a competent cyberspace, market-regulation, consumer-protection, or other authority, or bring proceedings before a competent court in accordance with law.