Privacy Policy

This policy is provided by Zhongman Zhisheng (Beijing) Technology Co., Ltd. ("LickMV", "we", "us", or "our"). It explains how we process personal data when you use the LickMV website, iOS app, or Google Play Android app (com.zmzs.lickmv).

1. Information We Collect

1.1 Account information

• Google sign-in: Google account identifier, email address, display name, and profile image supplied by Google after you authorize sign-in.
• WeChat sign-in: WeChat OpenID/UnionID, nickname, and profile image supplied by WeChat after authorization.
• Email sign-in: email address and one-time verification code that you enter.
• Session data: access tokens issued by us to keep you signed in and protect API access.

1.2 Content you choose to provide

• Lyrics, creative ideas, image descriptions, video scripts, titles, and subtitle text.
• Audio files, images, and videos you select or upload for a project.
• Generated songs, images, videos, subtitles, storyboards, and exported projects.
• Support messages and information you send when contacting us.

On Android we use the system photo picker, so the app receives only the media you select and does not request access to your full photo library.

1.3 Purchases and credits

• Google Play product ID, purchase token, order and transaction status, purchased credit package, and the resulting credit ledger.
• Google Play processes your payment credentials. We do not receive or store your full card number or Google account payment password.

1.4 Device, network, and security data

• Android ID, device model, operating-system version, app version/build, app distribution, language, IP address, access time, request metadata, error information, and core-operation security audit logs.
• We use this information for authentication security, fraud and abuse prevention, troubleshooting, service reliability, and legally required audit records.
• The Google Play build does not include Umeng analytics, Umeng U-Push or manufacturer push SDKs, advertising SDKs, Alipay, location collection, or advertising-ID collection.

Apple Ads download attribution. In the iOS version of the app, to record how our app downloads relate to advertising, the app obtains a short-lived attribution token through Apple AdServices at launch and sends it to our service with randomly generated collection and request identifiers and elapsed time since token acquisition, using existing app-account authentication. When attribution processing is enabled, we send the token to Apple and associate the returned campaign, ad-group, keyword and ad identifiers, placement, campaign country or region, download/redownload/pre-order type, available click or impression time, and attribution result with that app account for source analytics. Collection identifiers, attempt statuses and error codes support deduplication, bounded retries and troubleshooting. The raw token is used only during processing and is not persistently stored or logged; our server retains its digest and necessary processing records. This integration does not read IDFA, send app-account identifiers to Apple's attribution endpoint, or personalize advertising. Our existing retention and deletion rules apply.

1.5 Additional disclosure for China-distribution Android builds

This section applies only to China-distribution Android builds, including Huawei. It does not apply to the Google Play build. The Chinese privacy policy and SDK list describe the China build's services and providers.

The China-distribution Android build also integrates Umeng U-App analytics (common/asms), provided by Umeng Tongxin (Beijing) Technology Co., Ltd. (友盟同欣（北京）科技有限公司). After you agree to the privacy policy, the SDK processes Android ID and, when supported and available from system or device-manufacturer identifier interfaces, the Open Anonymous Device Identifier (OAID). The SDK may cache OAID and transmit it with analytics data to Umeng to identify statistical devices and analyze app use, including launches, page visits and feature events. This applies at app launch, including cold starts after consent, and during use. We do not use OAID for app sign-in, AI creation, payments or personalized advertising. This disclosure does not enable Umeng or OAID collection in the Google Play or iOS build. See the Umeng SDK privacy policy.

The China build integrates Umeng+ Message Push SDK (U-Push; com.umeng.message / com.umeng.umsdk:push), provided by Umeng Tongxin (Beijing) Technology Co., Ltd. (友盟同欣（北京）科技有限公司). After you read and agree to the privacy policy, the device SDK obtains ANDROID ID (Android ID), push Token, device model, operating-system version, network type and IP address through system APIs, generates or obtains the Token, and transmits these data to the push provider to identify the device and register a push channel. Notifications are triggered when your song generation, image generation or video composition tasks finish; task submission is not a prerequisite for SDK registration. See the Umeng SDK privacy policy.

After consent, the app also reads the push Token, Android ID (falling back to Build.FINGERPRINT if unavailable), package name, app version, distribution channel, language and time zone and uploads them to our servers when push registration succeeds, including cold starts after consent. The server associates the device with your account only for authenticated requests to deliver task-completion notifications. The China build includes Huawei HMS Push and Umeng channel adapters for vivo, OPPO, Honor and Xiaomi. A channel is enabled only if its native SDK is integrated and applicable to the device; adapters do not imply that every native SDK is included or every channel is active. Huawei HMS Push processes push Tokens, basic app information, app-scoped device identifiers, device hardware information, basic system information and system settings to register and deliver messages, as described in the SDK list.

If you decline the initial privacy policy, the app closes and the Umeng SDKs are not initialized and do not collect or report data. Turning off system notification permission stops notification display; it does not stop SDK registration or device-information collection.

To request access to, deletion of, or withdrawal of consent for device identifiers processed by Umeng, contact us through Settings — Contact us. Signing out or disabling system notifications does not stop Umeng SDK registration or device-information processing. Submitting a request through this contact channel does not immediately stop the SDK in the current app process.

2. How We Use Information

• Provide sign-in, account synchronization, AI creation, editing, storage, export, and customer support.
• Verify Google Play purchases, credit the correct account, prevent duplicate fulfillment, and maintain transaction records.
• Review uploaded and generated content for safety, prevent fraud or abuse, diagnose failures, and improve reliability.
• Comply with legal obligations and send essential notices such as security or policy updates.

3. Service Providers and Disclosure

• We do not sell your personal information to unrelated third parties.
• We use cloud hosting, object storage, content delivery, AI generation, content-safety, email, and support providers. They receive only the data needed to perform the requested service and are contractually limited to our instructions.
• If you choose Google sign-in or Google Play Billing, Google processes the relevant identity or transaction data under its own privacy terms. If you choose WeChat sign-in or sharing, Tencent processes the authorization or sharing data under its own privacy terms.
• We may disclose information when required by applicable law or legal process.

4. International Processing, Retention, and Security

• LickMV serves users internationally. Personal data may be processed in countries or regions where we or our service providers operate, which may have different data-protection laws.
• We use HTTPS, access control, least privilege, monitoring, and audit logging. No Internet transmission or storage system can be guaranteed completely secure.
• We retain account and project data while your account is active or as needed to provide the service. Purchase and security records may be retained longer where required for accounting, fraud prevention, dispute handling, or law. After account deletion becomes effective, we delete or de-identify personal data within the stated processing period unless retention is legally required.

5. Your Rights

• You may request access, correction, export, or deletion of your personal data where applicable.
• You can request account deletion in the app under Settings → Account and security → Delete account. You may also contact us using the details below.
• You may withdraw optional permissions through Android settings. This does not affect processing already completed lawfully.
• You may complain to your local data-protection authority.

6. Minors

LickMV is not directed to children. If you are under the age required to consent to data processing in your country, use the service only with authorization from a parent or guardian. Contact us if you believe a child provided personal data without proper authorization.

7. Permissions and Choices

• Internet: required for sign-in, generation, purchases, synchronization, and media delivery.
• Storage write on Android 9 and earlier: requested only when saving generated media to the device. Newer Android versions use scoped storage.
• Package visibility for WeChat: used only to determine whether WeChat can handle sign-in or sharing.

8. Policy Updates

We may update this policy based on business changes or legal requirements. Material changes will be communicated through reasonable notice.

9. Contact

For privacy questions or requests, email support@dubmic.com or use our Contact page.

Controller: Zhongman Zhisheng (Beijing) Technology Co., Ltd.
Address: Room 395, Floor 1, Building 1, No. 4, Zone B, Yongledian Development Zone, Tongzhou District, Beijing, China.