Mozhenzhen Privacy Policy

1. Who we are

Mozhenzhen is operated by Wuhan Luye Network Technology Co., Ltd. This policy applies to mozhenzhen.com and the Android app with package name com.mozhenzhen.app. It does not apply to third-party websites or apps you choose to visit.

2. Information we process

• Usage analytics: We use randomly generated browser or installation and session identifiers, platform and version, language, campaign source, search result counts, filters, report views, download clicks, outbound clicks, app opens and loading errors to measure use and return visits. Analytics does not record search text, hardware identifiers, passwords or verification credentials. Daily browser/installation observations are retained for up to 400 days and locally queued events for up to 24 hours. Clearing site or app data removes the corresponding local identifiers. Native analytics starts only after the existing privacy-consent flow permits it.
• Public browsing: To return pages, protect the service, and measure product use, we process request time, page, network address, browser or app version, device class, and necessary access and error information.
• Account sign-in: Password sign-in stores only an irreversible hash of the normalized account identifier, a redacted label, and a salted password-derived value. Phone sign-in processes the full phone number, its redacted form, and a short-lived code. Regular pages and logs do not display full phone numbers, passwords, or codes.
• Account activity: We process saved items, follows, comments, feedback, notifications, verification records, and provider claims that you create.
• Model verification: We process the endpoint, API key, model, tier, and results you submit. Continuous-verification credentials are encrypted. Public reports retain redacted conclusions only. The native Android layer does not read or store API keys.
• Media uploads: We read only the files you select when adding images or videos to a comment or feedback item; we do not scan your entire photo library.

3. Permissions and local storage

The first Android release uses network access only. It does not request location, contacts, phone, SMS-reading, microphone, camera, advertising ID, persistent background, or broad storage permissions. Media and files are selected through the system picker with per-use authorization.

On first use, the app presents its privacy notice. Business pages and native usage analytics start only after consent; rejecting it loads neither. A material policy update requires consent again. Registration, sign-in, and other operations involving an account or personal data display the User Agreement and Privacy Policy before submission and require your confirmation. The WebView and website store the current public-session identifier and necessary anonymous interaction identifiers locally. Clearing app data removes the local session but does not delete the server-side account.

4. Why we use this information

We process this information only to provide public research, sign-in and account sync, interactions, model verification, continuous tasks, support feedback, security, troubleshooting, and compliance audits. We do not sell account data, phone numbers, API keys, or verification credentials, and we do not use native advertising or device-fingerprinting SDKs.

5. Third-party processing

For sign-in or SMS delivery, Alibaba Cloud CAPTCHA and SMS services process the necessary risk-verification data, network and device environment, phone number, and delivery information. Third-party purchase pages open in the system browser and their operators independently process data after the redirect. See the Third-party Data Processing List.

6. Retention and security

• Public sign-in sessions last no more than 30 days by default and are revoked immediately after sign-out, account deletion, or a security action.
• SMS codes expire after five minutes by default. Sending, validation, and rate-limit facts are retained only for the minimum period needed for abuse prevention and auditing.
• Account data and continuous-verification credentials you create are retained while the account or feature requires them. They are deleted, revoked, or de-identified when you cancel the task or delete the account.
• Security, audit, and dispute-resolution facts required by law are retained with restricted access only for the legally required or necessary period, then deleted or anonymized.

We use separated access, session hashing, credential encryption, log redaction, HTTPS, and least privilege. Do not submit passwords, codes, or API keys in comments, feedback, screenshots, or email.

7. Your rights

You can view account data, history, saved items, and notifications in Account; sign out; and permanently delete the account after a second verification step. Use Feedback or the contact email to request corrections, deletion of specific content, an explanation, or to make a complaint.

8. Minors

Mozhenzhen is intended for AI-service buyers with the relevant legal capacity. Minors should use it under a guardian's guidance and should not independently submit payments, account credentials, or model API credentials.

9. Contact us

For questions about these terms, personal-data processing, or account deletion, contact us at bd@mozhenzhen.com. Do not send passwords, SMS codes, or API keys by email.