Updated: September 16, 2026
Effective: September 16, 2026
Yueche Nanxia Community (the “App”, “we”, “us”, or “our”) values your personal information and privacy. We process and protect your personal information in accordance with the principles of lawfulness, fairness, necessity, and good faith.
Please read and fully understand this Privacy Policy before using the App. After you tap to agree, or otherwise clearly indicate your consent, we will process your personal information in accordance with this Policy.
If you do not agree with this Policy, you may stop using the relevant services.
1. Who We Are
- App name: Yueche Nanxia Community
- Operator: Dongguan Yongzhi Technology Co., Ltd.
- Contact email: i@znnu.com
The App mainly provides information related to Yueche Nanxia, article reading, vehicle plate and lottery query tools, map and location marker browsing, current location and nearby place display, distance calculation, mall products and order services, in-app messages, account login, favorites, browsing history, and push notifications.
2. How We Collect and Use Your Personal Information
We only collect information that is necessary for the specific features you use.
If you refuse to provide certain information, you may be unable to use the corresponding feature, but other features that do not rely on that information will not be affected.
Account Registration, Login, and Identity Verification
When you use a phone number, email address, or WeChat to log in, register, or bind an account, we may process the following information:
- Phone number or email address;
- Verification code validation result;
- Account ID;
- Login credential and login status;
- Login time, login IP address, and necessary security logs.
When you use WeChat login or binding, after obtaining your authorization, we may receive the authorization code, OpenID, UnionID, nickname, avatar, and other public profile information returned by WeChat, for identity verification, account login, and account binding.
We do not store your password in plaintext, and we do not sell or illegally provide your phone number, email address, or WeChat account identifiers to unrelated third parties.
One-Tap Local Mobile Number Login
When you actively choose one-tap local mobile number login, we use Alibaba Cloud Phone Number Verification Service to authenticate the mobile number on the device through the carrier network.
After you agree to this Privacy Policy and actively authorize one-tap local mobile number login, the phone number verification service may process the following information:
- Network type;
- IP address;
- Device manufacturer;
- Device model;
- Mobile operating system;
- SIM card status (SIM State);
- Carrier type.
This information is used to pre-fetch the mobile number, obtain a one-time login credential, determine the terminal and network environment, and perform necessary security risk control and troubleshooting. It is not used for purposes unrelated to this feature.
After authentication succeeds, the client obtains a one-time authentication credential. Our server then exchanges that credential through Alibaba Cloud Phone Number Verification Service for the local mobile number you authorized. The mobile number is used only for account registration, login, identity verification, and account security management. If the mobile number has not been registered, the system may automatically create an account.
The phone number verification SDK is initialized or invoked only after you agree to this Privacy Policy and actively select one-tap local mobile number login. The carrier agreement displayed on the authorization page is dynamically provided by the SDK according to the current SIM card and carrier; we do not hard-code an agreement for a specific carrier.
You may refuse or cancel one-tap local mobile number login and use SMS verification code login or email login instead. Other features that do not rely on mobile number verification will not be affected.
User Profile Features
When you actively edit your profile, we may process the nickname, avatar, and other profile information you submit, for displaying and managing your user profile.
To maintain a healthy community environment, we may conduct format validation, sensitive word checks, or necessary content safety review on the nickname, avatar, and other content you submit.
Article Reading, Favorites, and Browsing History
When you use article-related features, we may process the following information:
- Article identifier;
- Reading time;
- Favorite status;
- Browsing record;
- Account ID.
This information is used to display content and synchronize favorites and browsing history.
If you are not logged in, we will not generate account-level favorites or browsing history for you, but necessary page state and cache may be stored on your device.
Vehicle Plate Query and Lottery Query
When you use vehicle plate query, lottery query, or similar tools, we may process the following information:
- Query conditions you actively enter;
- Query time;
- Query results;
- Necessary API request logs and troubleshooting logs.
This information is used to complete your query request and perform necessary troubleshooting.
Please do not enter sensitive personal information unrelated to the query purpose, such as ID card numbers, financial accounts, or medical and health information.
On-Device Image Text and Vehicle Plate Recognition
When you actively use image text recognition or vehicle plate recognition, the App may, based on your action, use the device camera to capture an image or allow you to select an image from the photo library or files for recognition.
The App uses a vehicle plate detection model trained or converted using the YOLO architecture, the open-source PaddleOCR component, and the Apple Vision system framework to perform vehicle plate region detection, text recognition, or vehicle plate number extraction locally on your device. This on-device processing may involve:
- Images you actively capture or select;
- Text that can be recognized in those images;
- Recognized vehicle plate numbers or other text results;
- Necessary temporary data generated on the device to complete recognition.
The above detection and recognition are performed locally on your device. The YOLO-based vehicle plate detection model is used only to locate vehicle plate regions in images and has no independent network or upload capability. We do not send images, detection results, or recognition results to maintainers of the model training framework or components, the PaddlePaddle open-source community, or Apple as a result of using the model, PaddleOCR, or Apple Vision. This feature itself does not upload original images to our servers or retain original images and temporary detection or recognition data for an extended period, unless otherwise required by law, actively saved or uploaded by you, or clearly stated for a specific feature.
If you actively initiate an online vehicle plate query after recognition, the App submits the vehicle plate number you confirm to our server as the query condition in order to return the corresponding result. The original image is not included in this step. The query condition, query time, query result, and necessary logs are processed in accordance with the “Vehicle Plate Query and Lottery Query” section of this Policy.
Camera, photo library, and file permissions are not required to use the App as a whole. You may refuse or withdraw these permissions in system settings. If you refuse, you cannot capture or select an image for recognition, but you may still manually enter a vehicle plate number or use features that do not depend on images. The App does not scan your photo library unless you actively select content.
In-App Messages and Notifications
When you use in-app message features, we may process the following information:
- Account ID;
- Message content;
- Message type;
- Sending and receiving time;
- Message read status.
This information is used to send, display, and manage in-app messages.
Push Notifications
After you agree to this Privacy Policy, we use the JPush SDK (v6.2.2, without IDFA) and Apple Push Notification Service (APNs) to provide basic message notifications, including article notifications, in-app messages, order notifications, and other service notifications. Displaying system notifications also depends on whether you allow notification permission for the App.
To register devices, select push channels, send notifications, and check delivery, we and the relevant service providers may process the JPush Registration ID, APNs device push token, app identifier, necessary device and network information, and push content, status, and logs. The types of information, purposes, and timing of processing are described in the JPush entry under “Third-Party SDKs and System Services” in this Policy.
We do not use push tokens for advertising tracking.
You can disable notification permission for the App at any time in iOS Settings. The system will then stop displaying the App’s notifications, while you can continue viewing messages in the App and using features that do not depend on notification permission. Disabling notification permission does not itself withdraw your consent to this Privacy Policy. To request deletion or withdraw authorization, you may contact us as described under “Your Rights” in this Policy.
Security, Risk Control, and Service Stability
To protect account, API, and service security, we may process the following information:
- IP address;
- Network type;
- Device model;
- Operating system version;
- App version;
- Request time;
- Account ID;
- Error information and crash information;
- Necessary operation logs.
This information is used only for identity verification, security risk control, statistical analysis, operation and maintenance, and troubleshooting. It will not be used for purposes unrelated to the App services.
When you use SMS verification code login, registration, phone number binding, or trigger security verification, we may process necessary information related to bot detection and security risk control through the GeeTest CAPTCHA v4 SDK and backend secondary verification service, such as device brand, device model, operating system and version, system language, device name, memory size, carrier information, screen size, whether the device is a tablet, IP address, network status, whether Wi-Fi is used, network type, verification interaction result, verification serial number, verification result, and necessary logs.
This information is used only to identify security risks such as automated scripts, malicious requests, bulk registration, and abuse of SMS verification codes. It is not used for personalized advertising or cross-app tracking. We initialize or call the relevant security verification SDK only after you agree to this Privacy Policy; the verification capability is called only when you actively trigger a feature that requires security verification.
Maps and Location Services
When you actively enter the map page, view your current location, view nearby markers, or calculate distance to a place, after obtaining your location authorization, we will use iOS system location service CoreLocation to obtain your precise or approximate location, including latitude and longitude.
Location information is used to:
- Display your current location on the map;
- Display or filter nearby places and markers;
- Calculate the distance between you and marker locations;
- Improve map browsing and place viewing experience.
Location information is sensitive personal information. We process it only within the scope necessary to provide the above features.
The App does not continuously obtain your location in the background, and does not use location information for user profiling, personalized advertising, or cross-app tracking.
Unless otherwise required by laws and regulations, or unless you actively submit it, we do not store your real-time location for a long time on our business servers.
Location permission is not required for using the App as a whole. You may refuse authorization or withdraw authorization in system settings. After withdrawal, only current location, nearby places, distance calculation, and related features will be affected.
When you use the map place contribution feature and actively enter place keywords, we will use the keywords you enter, the selected search region, and the place search results generated by our backend for place search, contribution submission, and backend review. To prevent forged place information, the place name, address, latitude and longitude, administrative region, and place identifier used for submission are based on the results confirmed and saved by our backend. The above information is used only for place search, contribution review, map marker creation, risk control, and necessary troubleshooting.
Mall Orders and Payments
When you use mall ordering, payment, refund, or after-sales features, we may process the following necessary information:
- Product or service name, specifications, quantity, item amount, order amount, and order number;
- Recipient name, contact phone number, and delivery address, only when you actively submit delivery information;
- Payment method, payment status, payment time, Alipay transaction number, and refund-related information;
- Necessary operation logs related to order processing, payment confirmation, refunds, after-sales service, and financial reconciliation.
When you actively choose Alipay payment, we provide Alipay with the order information and payment parameters necessary to complete the payment, and use the Alipay client payment SDK to open Alipay for payment. Alipay account information, payment password, bank card information, and other payment operations are handled by Alipay under its own privacy rules. The App does not collect or store your Alipay payment password or bank card password.
You may refuse to use Alipay payment, but you may then be unable to complete payment for the relevant order. This does not affect other features that do not depend on mall payment.
3. System Permissions and Device Capabilities We Use
Notification permission: used to receive article notifications, in-app messages, and service notifications. This permission is optional and is usually requested when push notifications are first enabled. If you refuse it, you will not receive system push notifications, but other in-app features will not be affected.
Location permission while using the App: used to display your current location, nearby places, and calculate distance. This permission is optional and is usually requested when you actively use location-related features. If you refuse it, current location, nearby places, and distance calculation will not be available.
Precise location: used to improve map positioning and distance calculation accuracy. This permission is optional and is provided by the system after location permission is enabled. If you disable precise location, only approximate location may be available.
Camera permission: used to capture an image for recognition when you actively use image text recognition or vehicle plate recognition. This permission is optional and is requested only when you actively use the capture feature. If you refuse it, you cannot directly capture an image for recognition, but you may still manually enter the relevant content or use other features that do not depend on the camera.
Photo library or file permission: used to select or upload avatars and files, and to select an image for recognition when you actively use image text recognition or vehicle plate recognition. This permission is optional and is requested only when you actively choose relevant content. If you refuse it, you cannot select or upload the corresponding content, but you may still manually enter the relevant content.
Network access: used to access backend APIs and load articles, maps, and query data. Network access is required for online features; without network access, network content and online features cannot be used.
You can view, enable, or disable relevant permissions in iOS “Settings - Privacy & Security” or the App’s system settings page.
Withdrawing authorization will not affect lawful processing already conducted based on your authorization before withdrawal.
4. Third-Party SDKs and System Services
WeChat Open Platform Login SDK (WeChat OpenSDK)
SDK name: WeChat OpenSDK for iOS
Service provider: Tencent / WeChat Open Platform
Purpose: To provide WeChat login, account binding, and identity verification.
Information processed: WeChat authorization code, OpenID, UnionID, nickname, avatar, and other public profile information authorized by you; necessary app, device, and network information required for SDK operation.
Processing method: Automatic SDK processing, app redirection, and API transmission.
Privacy reference: WeChat privacy protection guidelines.
Apple Push Notification Service (APNs)
Service name: Apple Push Notification Service (APNs)
Service provider: Apple
Purpose: To send article notifications, in-app message notifications, and service notifications to user devices.
Information processed: Device push token, app identifier, push content, and push status.
Processing method: Network transmission through Apple system push service.
Privacy policy: Apple Privacy Policy.
JPush SDK
SDK name: JPush SDK
SDK version: v6.2.2 (without IDFA)
Advertising identifiers: The App integrates the JPush SDK version without IDFA. We do not collect, access, or use IDFA or other user advertising identifiers through this SDK, or use it for personalized advertising or cross-app tracking.
Service provider: Shenzhen Hexun Huagu Information Technology Co., Ltd. (深圳市和讯华谷信息技术有限公司)
Purpose and usage scenarios: To provide basic message notifications to App users, including article notifications, in-app messages, order notifications, and other service notifications, and to maintain compatibility, connection stability, and accurate delivery.
Information processed and purposes:
- Push registration information: The JPush Registration ID, APNs device push token, and app identifier, used to identify the receiving device, associate push channels, and deliver messages accurately. These identifiers are used only for basic message notifications and are not used as user advertising identifiers;
- Device hardware information: Device model, screen resolution, hardware manufacturer, product name, and storage space, used to maintain compatibility across devices;
- Operating system information: Operating system version, system name, and system language, used to adapt to the device environment and deliver messages accurately;
- Network information: Network type, carrier information, IP address, DHCP, and Wi-Fi status, used to determine connectivity with the server and maintain stable, continuous push services;
- Push information: Message content, sending and delivery status, and necessary push logs, used to send notifications, query push service records, and investigate delivery issues.
Collection and processing method: When the App invokes push functionality, the SDK automatically collects information necessary for basic push services and processes it using de-identification, encrypted transmission, and other security measures. Our server submits the target device’s Registration ID and necessary message content to JPush. iOS notifications are delivered through the corresponding push channel, including APNs.
Timing of invocation: JPush business functionality is initialized or invoked only after you agree to this Privacy Policy. The SDK processes the necessary information during basic push operations such as device registration, connection maintenance, message receipt, and reporting push status.
Permissions and scope: Basic push services use network access, while system notification permission controls notification display. We use only the SDK’s basic message notification functionality. We do not use its user segmentation, geofencing, or user insights extensions, or use it for profiling based on location, Bluetooth information, or software lists. The information accessible to the SDK is restricted by the operating system, SDK configuration, and permissions you grant.
User controls: You can disable notification permission for the App in system settings. To request access to, correction of, or deletion of personal information, or to withdraw authorization, contact us using the details published in this Policy.
Jiguang Privacy Policy: https://www.jiguang.cn/license/privacy
JPush Compliance Guide: https://docs.jiguang.cn/jpush/client/jghgzy_a_i_h
Official website: https://www.jiguang.cn/
GeeTest CAPTCHA v4 SDK
SDK name: GeeTest CAPTCHA v4 SDK (GT4 iOS SDK)
Service provider: Wuhan GeeTest Network Technology Co., Ltd.
Purpose: To provide bot detection, security risk control, anti-abuse protection for API requests, protection against automated scripts, and abnormal request identification before sending SMS verification codes.
Information processed: Device brand, device model, operating system and version, system language, device name, memory size, carrier information, screen size, whether the device is a tablet, IP address, network status, whether Wi-Fi is used, network type, verification interaction result, verification serial number, verification result, and necessary logs.
Processing method: When you trigger security verification, the SDK automatically collects and transmits necessary verification information through the network. Our backend conducts secondary verification based on the verification parameters returned by GeeTest, and only stores verification results, tickets, and security logs necessary for verification, anti-abuse protection, and troubleshooting.
Timing of invocation: The SDK is invoked after you agree to this Privacy Policy and when you actively perform SMS verification code sending, login, registration, account binding, or other operations that require security verification.
Permission description: This SDK mainly uses network access capability. It does not actively request contacts, photo library, location, microphone, or camera permissions. We do not obtain IDFA through this SDK, and do not use it for personalized advertising or cross-app tracking.
Privacy policy: https://www.geetest.com/Private/gt4
Compliance guide: https://docs.geetest.com/gt4/compliance
Alibaba Cloud Phone Number Verification Service SDK
SDK name: Phone Number Verification Service SDK
Service provider: Alibaba Cloud Computing (Beijing) Co., Ltd.
Purpose: To provide one-tap local mobile number login, registration, and identity verification.
Usage scenario: Invoked after you agree to this Privacy Policy, actively select one-tap local mobile number login, and accept the relevant authorization agreements.
Information processed: Network type, IP address, device manufacturer, device model, mobile operating system, SIM card status (SIM State), carrier type, and the one-time authentication credential necessary to complete verification.
Processing method: SDK collection, encrypted transmission, and server-side authentication. After the client obtains a one-time authentication credential, our server calls Alibaba Cloud Phone Number Verification Service to exchange it for the local mobile number you authorized.
Timing of invocation: Initialized or invoked only after you agree to this Privacy Policy and actively select one-tap local mobile number login. The authorization page dynamically displays the applicable carrier agreement based on the current SIM card.
Permission description: The SDK mainly uses network access capability and does not request contacts, SMS, location, photo library, microphone, or camera permissions for this feature.
Compliance guide: https://help.aliyun.com/zh/pnvs/security-and-compliance/number-certification-service-compliance-guidelines
Privacy policy: https://terms.aliyun.com/legal-agreement/terms/suit_bu1_ali_cloud/suit_bu1_ali_cloud202112211045_86198.html
iOS integration guide: https://help.aliyun.com/zh/pnvs/developer-reference/the-ios-client-access
App Alipay Client Payment SDK
SDK name: App Alipay Client SDK
Service provider: Alipay Payment Technology Co., Ltd.
Purpose: To provide Alipay App payment for mall orders, protect user account and fund security, maintain stable payment services, fulfill legal obligations related to anti-money laundering, counter-terrorist financing, and anti-telecom fraud, and optimize network route selection.
Usage scenario: The SDK is invoked only when you actively select “Alipay payment” in the App mall and initiate payment for an order. We do not invoke this SDK in advance for payment purposes when you launch the App.
Information processed: Depending on the device platform and the actual SDK operation, the Alipay client payment SDK may process:
- Changeable unique device identifiers, such as AndroidID, OAID, and IDFV;
- Basic device information, such as device model, device brand, operating system and version, and screen density;
- Sensor information, such as the list of device sensors;
- Carrier information;
- Wi-Fi parameters;
- Network type and other necessary network information.
Processing method: When you actively initiate payment, the SDK transmits necessary information through encrypted network communication and opens the Alipay client to complete payment. Alipay account information, payment passwords, bank card information, and other payment operations are handled by Alipay under its own privacy rules. The App does not collect or store your Alipay payment password or bank card password.
Order information processing: To create and complete payment, we and Alipay may process necessary order payment information, including order number, product or service name, order amount, transaction time, payment status, and Alipay transaction number. This information is used to create payment orders, confirm payment results, process refunds, provide order after-sales service, and perform financial reconciliation.
Timing of invocation: The SDK is invoked only after you agree to this Privacy Policy and actively tap the Alipay payment button in the mall. Canceling or refusing Alipay payment does not affect other features that do not depend on this payment function.
Permission description:
- On iOS, the SDK mainly uses network connectivity for payment data transmission and necessary network information;
- On Android, the SDK may request device status and network connectivity permissions as required by the Alipay SDK;
- The App does not request contacts, SMS, photo library, microphone, or location permissions for Alipay App payment.
Alipay Client Payment SDK Privacy Statement: https://opendocs.alipay.com/open/01g6qm
Alipay Client Payment SDK Compliance Guide: https://opendocs.alipay.com/common/09e357
PaddleOCR Open-Source Text Recognition Component
Component name: PaddleOCR
Component type: Open-source text recognition component
Project maintainer: PaddlePaddle open-source community
Purpose: To recognize text and vehicle plate numbers in images you actively capture or select, locally on your device.
Information processed: Images you actively capture or select, text contained in those images, recognized vehicle plate numbers or other text results, and temporary on-device data necessary to complete recognition.
Processing method: Computation is performed only locally on the device. Images and recognition results are not transmitted to the PaddleOCR project maintainers or the PaddlePaddle open-source community as a result of using this component.
Timing of invocation: Invoked only when you actively use image text recognition or vehicle plate recognition.
Permission description: The component itself does not actively request camera or photo library permission. The App requests relevant permissions through the system permission mechanism only when you actively capture or select an image. We do not obtain IDFA through this component and do not use it for personalized advertising or cross-app tracking.
Project URL: https://github.com/PaddlePaddle/PaddleOCR
Open-source license: Apache License 2.0
Apple Vision System Framework
Framework name: Apple Vision
Service provider: Apple
Framework type: An image analysis and text recognition framework provided by iOS. It is not a separate third-party network OCR service integrated by the App.
Purpose: To recognize text in images you actively capture or select locally on the device and assist in extracting vehicle plate numbers.
Information processed: Images you actively capture or select, text contained in those images, recognized vehicle plate numbers or other text results, and temporary on-device data necessary to complete recognition.
Processing method: Computation is performed locally on the device through the iOS system framework. Images and recognition results are not sent to Apple as a result of using Apple Vision.
Timing of invocation: Invoked only when you actively use image text recognition or vehicle plate recognition.
Permission description: Camera or photo library permission is requested by the App through the iOS system permission mechanism based on your active operation. Apple Vision does not request contacts, location, or microphone permission for this feature.
Apple Privacy Policy: https://www.apple.com/legal/privacy/en-ww/
YOLO-Based Vehicle Plate Detection Model
Model type: An object detection model trained or converted using the YOLO architecture
Purpose: To detect Hong Kong vehicle plate regions locally on the device in images you actively capture or select, providing regions for subsequent text recognition.
Information processed: Images you actively capture or select, vehicle plate regions in those images, and temporary on-device data necessary to complete detection.
Processing method: Model inference is performed only locally on the device. The model file has no independent network or upload capability. Images and detection results are not transmitted to maintainers of the model training framework or related open-source projects as a result of using the model.
Timing of invocation: Invoked only when you actively use Hong Kong vehicle plate recognition.
Permission description: The model itself does not actively request any system permission. Camera or photo library permission is requested by the App through the system permission mechanism only when you actively capture or select an image. We do not obtain IDFA through this model and do not use it for personalized advertising or cross-app tracking.
Model description: The model locates vehicle plate regions. Vehicle plate text extraction may then be completed locally on the device using PaddleOCR or Apple Vision.
The on-device detection and recognition described above for the YOLO-based vehicle plate detection model, PaddleOCR, and Apple Vision do not constitute sharing images, detection results, or recognition results with the model training framework, related open-source project maintainers, or service providers. Except for models, open-source components, or system frameworks explicitly described as performing on-device processing, other third-party services may independently process relevant information in accordance with their own privacy policies.
We conduct necessary security and compliance review for connected third-party SDKs and services, and will update this Policy in a timely manner when third-party services or information processing rules materially change.
5. Cookies, Cache, and Local Storage
The App may store the following necessary information on your device:
- Login token and login status;
- Account settings;
- Privacy policy consent status;
- Favorite and browsing status;
- Page and image cache;
- Map display settings;
- Local configuration data such as UserDefaults.
If the App uses embedded web pages, those pages may use cookies within the scope necessary for login status, page settings, and security verification.
You may delete part of the local data by logging out, clearing relevant records, or uninstalling the App.
Deleting cache may cause some content to reload, but will not affect your basic account rights.
6. How We Share, Transfer, and Publicly Disclose Personal Information
Sharing
We do not sell your personal information to unrelated third parties.
Only in the following circumstances may we provide necessary information to relevant service providers:
- We have obtained your explicit consent;
- It is necessary to enable WeChat login, system push and JPush basic message notifications, GeeTest security verification, one-tap local mobile number login, mall Alipay payment, or other necessary features;
- When you actively use mall Alipay payment, it is necessary to provide Alipay with the order information, payment parameters, and necessary device and network information required to complete payment;
- It is required by laws and regulations, judicial authorities, or administrative authorities;
- It is necessary to protect the lawful rights and interests of users, us, or the public.
We follow the principle of minimum necessity and require partners to protect your personal information in accordance with applicable laws, regulations, and agreements.
When the YOLO-based vehicle plate detection model, PaddleOCR, and Apple Vision perform detection and recognition locally on the device, we do not share images, detection results, or recognition results with the model training framework, related open-source project maintainers, the PaddlePaddle open-source community, or Apple as a result of that processing.
Transfer
Without your explicit consent, we will not transfer your personal information to other companies, organizations, or individuals.
If merger, division, acquisition, asset transfer, or operator change occurs, we will notify you in accordance with the law and require the new personal information processor to continue to be bound by this Policy.
If the purpose or method of personal information processing changes, we will obtain your consent again as required by law.
Public Disclosure
In principle, we do not publicly disclose your personal information.
We will only make necessary disclosure after obtaining your separate consent, or as required by laws, regulations, judicial authorities, or administrative authorities.
7. How We Store Your Personal Information
We retain your personal information only for the shortest period necessary to achieve the purposes described in this Policy.
In general:
- Account profile information is retained while the account exists;
- Favorites, browsing history, and in-app messages are retained as needed for the relevant features;
- Security and operation logs are retained for the necessary period required by service security and applicable laws and regulations;
- Real-time location information is generally processed only while you use the relevant features;
- Device cache is stored on your local device until it is cleared or the App is uninstalled.
After account cancellation, we will delete or anonymize relevant personal information in accordance with the law, except where laws and regulations require continued retention.
8. How We Protect Your Personal Information
We take reasonable security measures to protect your personal information, including but not limited to:
- Using HTTPS encrypted transmission;
- Securely storing login credentials;
- Applying signature and expiration controls to login credentials;
- Verifying identity and permissions for backend management operations;
- Applying frequency limits and security checks to API requests;
- Controlling database access permissions;
- Recording abnormal requests and conducting risk investigation.
Please understand that the Internet environment is not absolutely secure.
When a personal information security incident occurs or may occur, we will take remedial measures in accordance with the law and report to you and relevant competent authorities as required.
9. Your Rights
Under applicable laws and regulations, you have the right to query, access, correct, supplement, or delete your personal information, and you may also withdraw authorization, unbind third-party accounts, or apply for account cancellation.
Query and Access
You can view account profile information, binding status, favorite records, browsing history, in-app messages, and other information in the App.
Modification and Correction
You can modify your nickname, avatar, and other profile information in the App.
Deletion
You can delete part of your information by canceling favorites, deleting records, or clearing browsing history.
Account Cancellation
You can apply for account cancellation through the account cancellation feature provided in the App.
After account cancellation, we will delete or anonymize account-related information in accordance with the law, and unbind phone number, email address, and WeChat binding relationships, except as otherwise required by laws and regulations.
Withdrawal of Authorization
You can disable notification, location, photo library, and other permissions through system settings, and you can also unbind WeChat or other third-party accounts in the App.
Please note that withdrawing authorization may cause the corresponding feature to become unavailable, but it will not affect other features.
If the App temporarily does not provide a corresponding operation entry, you may contact us through the email address published in this Policy.
10. Protection of Minors
The App is mainly intended for users with full civil capacity, and does not actively provide services to minors under the age of fourteen.
Minors should use the App with the consent and guidance of their guardians.
Minors under the age of fourteen should obtain explicit consent from their guardians before using the App.
If a guardian discovers that a minor has provided personal information to us without consent, the guardian may contact us through the contact method published in this Policy, and we will handle it in accordance with the law.
11. How This Policy Is Updated
We may update this Policy according to changes in laws and regulations, business operations, and product features.
When material changes occur, we will notify you through App pop-ups, announcements, in-app messages, or other reasonable methods, and will obtain your consent again when necessary. Material changes include:
- Major changes to the purpose of personal information processing;
- Major changes to the types of personal information processed;
- Major changes to personal information sharing, transfer, or public disclosure rules;
- Major changes to your personal information rights and how to exercise them;
- Major changes to third-party SDKs or personal information processing rules;
- Changes to the operator or contact methods.
12. How to Contact Us
If you have any questions, comments, or requests regarding this Policy or personal information protection, you may contact us through the following methods:
- Operator: Dongguan Yongzhi Technology Co., Ltd.
- Contact email: i@znnu.com
- App name: Yueche Nanxia Community
After verifying your identity, we will process and respond to your request within the period required by laws and regulations or within a reasonable period.
13. Miscellaneous
This Policy applies to the Yueche Nanxia Community App.
If a specific feature has a separate privacy notice or authorization instruction, that separate notice and this Policy together form the rules for processing personal information for that feature.
If any provision of this Policy is deemed invalid or unenforceable, it will not affect the validity of the other provisions.