🎉 Special Offer! Use code SAVE10 for 10% off your order. View All Coupons →
🎉 Special Offer! Use code SAVE10 for 10% off your order. View All Coupons →

WELLVOW App Privacy Policy

Effective date: September 19, 2026

This policy explains how 深圳市汉煻科技有限公司 (“WELLVOW”, “we”, “us”) handles information in the WELLVOW mobile app and its related app services. It covers compatible lighting control, app community features, feedback, and optional HUB technical submissions. The website’s separate privacy notice applies to website accounts, website shopping, and other website activities. Opening website or third-party content from the app can involve those services as explained below.

The app’s core lighting-control functions do not require a WELLVOW app account. This does not mean that all app activity is anonymous or stays on your phone. Device identifiers in optional diagnostics, online requests, community submissions, and the optional features described here can involve our cloud services.

1. Local lighting control and information on your phone

The app uses controller information, connection addresses or identifiers, model and firmware information, device state, and lighting settings to discover, authenticate, connect to, and control supported devices. Device lists, preferences, saved lighting settings or effects, community blocking preferences, and other local feature data may be stored on your phone.

Wi-Fi setup sends the network name and password you enter to the selected controller through the setup connection. This setup flow does not submit that password to our cloud feedback or HUB services. Do not place a Wi-Fi password or other secret in feedback, community posts, or HUB product-model fields. Local control and setup should not be confused with the online submissions and diagnostic services described below.

Photos chosen for the color-extraction feature are processed on your phone and are not uploaded to WELLVOW for that analysis. If you independently send an image or other material to support or another service, that is a separate disclosure.

For supported music-reactive controls, the app sends settings such as mode and sensitivity to the controller. Audio sensing depends on the controller hardware. The current music-control flow does not record audio through your phone’s microphone.

2. Device connections and online requests

For the WLED-STRIP and HUB controllers supported by this release, controller identifiers, authentication information, model, firmware version, and connection state are used on the phone and in communication with the controller. This release does not send automatic device-security reports or perform app-based firmware-update checks for these controllers. App-based firmware updates for these controllers are currently unavailable; contact support for model-specific assistance.

If you choose the optional feedback diagnostic described in section 4, a device-identity hash or transport identifier and related technical details are sent to WELLVOW. That optional diagnostic is separate from normal local device control. It can distinguish a device and should not be understood as anonymous.

Requests for online app content and cloud submissions involve cloud and delivery providers. They receive network information needed to serve the request and may produce connection, operational, and security logs, including IP addresses. This is separate from the contents of a community, feedback, or HUB submission.

3. Community content, reports, and feedback

When you submit a community post, we receive the author name or label, title, text, any shared lighting-effect parameters, and a randomly generated community identifier associated with that app’s community activity. We use these to receive and moderate submissions, show approved content, and support abuse reporting and blocking. Approved posts and shared content are visible to other users. A random identifier does not make the post unidentifiable, especially if its text identifies you.

When you report a post, we receive the post reference and the report reason. Your local blocked-user list is stored on your phone to filter the content you see. Do not include another person’s private information in a post or report unless needed to explain a problem to support.

When you send feedback or contact support, we receive the message and information you provide, such as an email address, attachments, device details, or a submission reference. App feedback may also include app-version and device-model fields where available. We use this information to handle your request, investigate problems, moderate content, and maintain the service.

4. Optional one-time feedback diagnostics

You may choose a one-time diagnostic when sending feedback. If enabled, the app opens a short capture window, normally 60 seconds, and captures one subsequent eligible device-control operation. The diagnostic can include a device-identity hash or transport identifier, control-function identifiers, the operation’s success or failure and error code, product type, hardware and firmware details, protocol and key version numbers, and connection type.

This diagnostic is intended to identify a failing operation. Control-function identifiers describe which controls were used; the diagnostic payload does not include their values, raw command packets, or a device secret key. Sending a normal feedback message does not require enabling this option. The capture stops after the one eligible operation or when the window expires. Network services can still create their normal connection or security logs.

5. Optional HUB technical submissions

For a compatible HUB, you can review and save a product-protocol snapshot on your phone. Saving it locally does not submit that snapshot to WELLVOW. If you separately confirm a cloud submission, we receive the entered brand and product model, bytes per frame, parsed LED count, high and low durations for 0 and 1 bits, reset timing, and channel format. Unknown technical values can remain unknown.

We use these submissions for testing, protocol comparison, and improvement of the recognition library. The service also keeps a submission reference, submission and expiry times, consent-notice version, and review status. This particular submission does not attach an account, device identifier, raw signal-frame contents, Wi-Fi name or password, or a photo. Other app features have their own data flows described in this policy.

Submission is optional and does not affect local analysis or lighting control. Consent is requested for each submission. Do not enter personal information in brand or product-model fields. Keep the returned reference if you want us to find or delete the record later.

HUB submission records are retained for 90 days and are scheduled for deletion after expiry. Reviewed technical features may continue to be retained in a protocol-recognition library without the original submission reference or an attached account or device identity. The 90-day rule applies to the business submission records; it does not mean every cloud-provider log or backup is erased at the same moment.

6. Permissions and your choices

Bluetooth or Nearby Devices and Local Network access support controller discovery and communication. Some older Android versions require a location-related permission for Bluetooth discovery. Camera or photo-library access supports image features you choose. The permissions available and prompts shown depend on the phone, operating system, and app version.

You can manage these permissions in your phone settings. Denying a permission may disable the related function. You can decline optional diagnostics, choose not to post community content, and keep a HUB snapshot local instead of submitting it. To withdraw a submission or request deletion of data already sent, contact us using the process below; turning off a permission alone does not delete previous cloud records.

7. Cloud providers, online videos, and external links

We use Supabase to host app backend services and data. The WELLVOW project used for HUB submissions is hosted in the US West region. Our operator and support function are based in China. Information may therefore be processed or accessed in countries outside your own, whose privacy laws and government-access rules can differ.

Cloud hosting, network delivery, and email providers process information needed to deliver and protect their services. Authorized support and administration personnel use the relevant records for support, moderation, security, and the purposes described here. We may disclose information when necessary to comply with a legal obligation, respond to a lawful request, or protect users and the service.

When you choose a tutorial, the app opens its HTTPS video page in your system browser or a video app. This release does not embed an online YouTube player, automatically play a video, or load YouTube thumbnails in the app. The external destination then processes connection and playback information under its own policy; it may use cookies, identifiers, account settings, or advertising. See Google’s Privacy Policy for YouTube.

Product and promotion links can open our website or a third-party seller. The destination site’s cookies, account, payment, and privacy practices apply to activity there. Loading online app content also involves requests to the host serving it. Local lighting control does not imply that external video pages, external websites, or all service providers operate without their own data collection.

8. Retention, deletion, and security

Local app data remains subject to the app’s relevant controls and your phone’s storage and backup settings. Clearing an effects list affects only the scope stated in that control. Removing a controller, clearing phone storage, or uninstalling the app does not automatically delete community posts, support records, optional diagnostics, HUB submissions, or a separate website account.

Apart from the HUB submission period stated above, we retain information for the period needed for the purpose for which it was collected. The relevant factors include whether a support issue or content report remains open, whether community content remains published, whether a diagnostic record is still needed to investigate an issue or protect the service, and any applicable legal obligations. Deletion requests are considered against these purposes and obligations. Cloud-provider logs, backup copies, and records needed for security, legal compliance, or request handling can follow separate retention cycles or requirements; deletion from an active service does not necessarily remove those copies immediately.

We use access controls and technical safeguards intended to protect information. No storage or transmission method eliminates every risk. Please keep device credentials private and avoid putting sensitive information into free-text fields.

9. Requests and privacy rights

You can contact support@wellvow.com to ask about, access, correct, or request deletion of information associated with your use of the app, or to withdraw consent for an optional submission. Rights and exceptions depend on applicable law. We may need limited information to locate a record and verify that you are entitled to request action; we will explain if we cannot locate information or cannot fulfill a request in full.

Use a post link or title, your app community identifier where available, a feedback reference or approximate date, or a HUB submission reference. A reference helps locate data and is not by itself proof of ownership. Do not send passwords, Wi-Fi passwords, device keys, or identity documents. Full instructions are on WELLVOW App Data and Account Deletion Requests.

10. Children and policy changes

WELLVOW is a general lighting-control service and is not directed at children under 13. If you believe a child has provided personal information through the app, contact us so that we can investigate and address it as appropriate.

We may update this policy when the app, services, or data practices change. The effective date identifies the current version. Where required, we will provide additional notice or request consent before applying a material change to the relevant data use.

11. Contact the operator

深圳市汉煻科技有限公司
深圳市宝安区石岩街道龙腾社区石环路135号212
Contact-address translation: Room 212, No. 135 Shihuan Road, Longteng Community, Shiyan Subdistrict, Bao’an District, Shenzhen, China.
Email: support@wellvow.com
Phone: +86 136 9217 9901

Related pages: App Support · Data and Account Deletion Requests.

New Report

Close