Privacy Policy

This policy explains how Muru Network Technology (Hangzhou) Co., Ltd. handles information when providing MLUE through mlue.com, the MLUE website and iOS app. It covers accounts, public creator pages, content and media, audience tools, MLUE AI, product analytics, notifications, purchases and support. Please read it together with the Terms of Service.

1. Who operates MLUE

MLUE is operated by Muru Network Technology (Hangzhou) Co., Ltd., a company based in Hangzhou, Zhejiang, mainland China (referred to as “MLUE,” “we,” “us” or “our”).

Questions or requests about this policy or your account may be submitted through our privacy request form, the support route in the product, or team@mlue.cn.

2. Information we handle

Account, identity and security data

This may include your email address, phone number when you choose a phone-based feature, username, display name, password credential in hashed form, verification and policy-consent records, login sessions, account status, device identifiers and security logs. Verification codes expire quickly and are not stored as long-term plaintext credentials.

If you use Sign in with Apple, we receive the stable account identifier, identity token and authorization data Apple provides, plus the name or email you choose to share at first authorization. An Apple private relay address is treated as an email address. If another social sign-in or connection is offered and you choose it, we receive only the profile and authorization data covered by that flow.

Profile, content and contact data

This includes your avatar, biography, background and theme choices, links, social handles, QR codes, location labels or addresses, business-card contact fields, products, forms, files and content blocks. Uploaded content can include images, video, audio and documents. A file may contain device, capture-time or location metadata, so remove metadata you do not want to provide before uploading.

MLUE stores your working draft and the content currently made public. After you complete initial setup and confirm a public page, saved workspace changes may sync to that page automatically. Individual items can still be hidden, archived or scheduled where those controls are available.

AI content and optional memory

When you use MLUE AI, we handle prompts, recent conversation context, image-generation descriptions, outputs, feedback, cited sources, execution records and generated-image information. Conversations and messages are associated with your account so they can continue across devices. If an optional long-term memory feature is available and you enable it, we also store the preferences or facts you confirm for later use.

Usage, device, notification and audience data

We handle events such as public-page views, link clicks, shares, QR scans, digital-card views or downloads, source category, device category, registration, onboarding, publishing and checkout steps. Network requests also carry an IP address, browser or device information and timestamps used for security, rate limiting, reliability and legally required network logs. Creators generally receive aggregated activity about their own pages rather than raw security logs.

If you enable iOS notifications, we handle the Apple Push Notification service (APNs) token, app version, locale, category preferences and delivery or interaction status needed to provide and measure the notification.

Visitor submissions, support and transactions

A visitor may voluntarily submit information through a creator’s form, poll, message, subscription or contact module. MLUE processes the submitted fields and makes them available to that creator. Support, report, privacy, appeal, business and allowlist requests may include a name, email, topic, description, attachments and follow-up correspondence. Do not send passwords, verification codes, identity documents or unrelated sensitive information.

If a paid feature is available, we may handle the order number, product or plan, amount, currency, channel, transaction and refund status, purchase time, invoice information and the reason you submit with a refund request. For iOS purchases, MLUE receives signed App Store transaction data and an account association token used to validate, restore and reconcile entitlements. Apple or the relevant payment provider handles payment credentials and security checks; MLUE does not receive your payment password or full card number.

3. How we use information

To create and secure accounts, sessions, drafts, public pages, links, content and media, and to synchronize supported features between the website and app.
To complete email, phone, username, Apple or other supported authentication, account recovery, connection, disconnection and security checks.
To provide AI conversations, image generation, optional memory, web-assisted research and user-requested workspace assistance, and to meter applicable usage.
To identify supported link types, render public cards, and offer embedded content or an external-link fallback where third-party rules permit.
To aggregate page and product interactions for creator insights, service reliability and product improvement, subject to the controls available in settings.
To deliver service messages, security notices and the product-message categories you select.
To handle support, privacy, reporting, infringement, appeal, business and allowlist requests and prevent abuse.
To validate orders, grant entitlements, process refunds or invoices, reconcile transactions and prevent fraud when a purchase feature is used.
To comply with applicable law and respond to a valid request from an authorized public body.

4. Public pages and visitor submissions

Information placed on a public MLUE page can be viewed, copied, shared or saved by anyone who can reach that page. Do not publish a home address, identification document, real-time location or anything you do not want public. A third-party destination linked from a page is governed by that third party’s own terms and privacy practices.

When a visitor submits information to a creator, the relevant module should identify the requested fields and intended recipient. The creator is responsible for using the submission only for the stated and lawful purpose and must not sell or disclose it without an appropriate basis. A visitor may use an available email preference link or contact MLUE to request assistance.

5. MLUE AI, web search and code execution

MLUE may store AI conversations, outputs, feedback, sources and execution records to synchronize the experience, continue a conversation, investigate abuse, process deletion requests and account for usage. Text requests may pass through automated redaction for some common credential, contact, identity and card-number patterns, but redaction is not complete and does not apply identically to every image workflow. Do not place passwords, verification codes, identification documents, card data, precise home addresses, health records or other unnecessary sensitive information in a prompt, image or memory.

Optional long-term memory is read only after you enable the feature and confirm information to save. Turning memory off stops later retrieval but does not itself erase existing items; use the memory controls to delete individual items, or delete the account to request deletion of account-linked memory.

Depending on the production configuration and feature you request, AI input may be sent to Alibaba Cloud Model Studio/Bailian and Qwen text or image models, an inference service managed by MLUE, or another OpenAI-compatible endpoint allowed by MLUE’s server configuration. Necessary input can include your prompt, recent conversation context, enabled memory, system instructions and summaries returned by a web tool. Provider logging and improvement practices depend on the relevant service configuration and terms; MLUE does not promise that every external provider keeps no logs or never uses data for service or model improvement.

If you explicitly request calculation, Python or data analysis, necessary code and the current input may be sent to Alibaba Cloud Agent Sandbox for temporary execution in an isolated environment. Older conversations, account credentials and unrelated workspace material are not intended to be passed as sandbox environment variables. Output used in the answer can remain in the conversation record.

When a web-assisted AI feature is used, a generated or predefined search query may be sent to a configured search provider such as 360 Search or Bing, and a public website may receive a server request when MLUE retrieves it. Search providers and destination sites apply their own logging and privacy practices.

MLUE does not currently use account content, AI conversations or saved memory to train an MLUE-owned foundation model. If identifiable user content is proposed for a new training purpose, we will explain that purpose separately and obtain any permission required by applicable law.

6. Cookies, Keychain and local storage

MLUE uses limited storage needed to operate the service:

session maintains an authenticated creator session and related security state, normally for no more than seven days unless ended earlier.
Short-lived OAuth challenge cookies are used to verify a login or connection flow and are cleared or expire after the flow.
Session storage may temporarily keep a requested public username, an in-progress checkout, onboarding state or recent design undo data.
The iOS app uses Keychain for login tokens, an installation-linked device identifier and necessary authorization state, and system preferences for interface settings.

MLUE does not currently use advertising cookies, an advertising network or cross-site marketing profiles. Deleting required cookies signs you out. If MLUE later introduces non-essential analytics or marketing technology, this notice and any required choice mechanism will be updated before it is used.

7. Service providers and processing locations

Core MLUE infrastructure is in mainland China. Account records, creator pages, product data, media and operational data are stored and processed primarily on shared MLUE infrastructure provided by Alibaba Cloud in mainland China. Relevant Alibaba Cloud services can include ECS compute, RDS for PostgreSQL, Object Storage Service (OSS), email, SMS, Model Studio/Bailian, Qwen models and Agent Sandbox, but a provider receives data only when the corresponding feature is configured and used.

Vercel supports the mlue.com overseas edge. Requests to mlue.com may pass through Vercel’s global edge network for domain delivery, routing, security and performance before reaching MLUE’s application infrastructure. Vercel may therefore process IP addresses, HTTP metadata and the request or response traffic that passes through the edge. Vercel is not MLUE’s primary account database or product-data system of record.

Apple is used only for Apple features. Apple independently handles information required for Sign in with Apple, APNs and App Store/StoreKit. MLUE receives the identifiers, tokens and transaction status needed to operate the feature you selected.

If you choose a social connection, payment method, AI web search or external website, that service receives the information necessary for the requested connection, transaction, search or page retrieval and applies its own privacy terms. A provider’s location, log retention and independent purposes are controlled by its service configuration, contract and applicable law.

8. International data transfers

If you access mlue.com from outside mainland China, your information will be transferred to and processed in mainland China because MLUE uses the same account, product database and core infrastructure for its domestic and international service. It may also transit through Vercel’s overseas edge as described above or be sent to another provider only when you use the relevant feature.

Privacy and data-access rules in mainland China may differ from those in your location. MLUE applies this policy and its technical and organizational controls to the information it handles. Where a law applicable to a particular transfer requires additional notice, consent, a contract or another transfer measure, MLUE will address that requirement for the relevant processing. This policy does not claim certification under, or universal compliance with, every privacy framework worldwide.

9. How long information is kept

Account, draft, public-page, media and product data is normally kept while the account remains active and then deleted or de-identified after account deletion, subject to legal exceptions and backup rotation.
AI conversations and generated content remain until you delete the conversation or account. Saved memory remains until you delete the item or account; disabling memory only stops later use.
Verification data is kept briefly for verification, abuse prevention and troubleshooting. Provider delivery records may be retained under provider or legal requirements.
Support records are generally kept for up to two years after closure; reports, infringement matters, appeals and related enforcement records are generally kept for up to three years after closure.
Necessary network and security logs are retained for the period required for security and applicable law, including any legally required minimum period.
Order, signed App Store transaction, payment, refund, invoice and reconciliation records are retained as necessary to provide the service, resolve disputes and meet tax or transaction-record obligations, even if the account is later deleted.

Deleted data may remain for a limited period in access-restricted backups until the backup is overwritten. External providers may retain their own records under their contracts, policies or legal obligations.

MLUE does not sell personal information. MLUE does not currently use IDFA, connect an advertising network, or combine MLUE data with data from unrelated apps, websites or offline sources for targeted advertising, ad measurement or data-broker activity.

MLUE discloses information to a service provider only as needed to operate the selected feature, to another user when you intentionally publish or submit it, in a company transaction subject to appropriate handling, to protect users and the service, or when required by valid legal process. Necessary transfer to an authentication, cloud, AI, search, payment or social provider is not a sale by MLUE.

11. Security

MLUE uses measures such as encrypted transport, encryption for selected credentials and memory, access controls, session validation, audit records, upload checks, rate limits and backups. No connected service can guarantee absolute security. If an incident is likely to affect personal rights, MLUE will investigate, take remediation steps and provide notices required by applicable law.

12. Your choices, access and account deletion

Depending on the feature and applicable law, you can use MLUE settings to view, correct, hide, archive or delete page data and content; manage notification and connected-account choices; view or delete AI conversations and memory; export supported account data; and request access, correction, deletion or withdrawal of a consent-based choice.

You can request account deletion from account settings. We may require recent authentication and the complete username to prevent unauthorized deletion. Deleting the iOS app does not delete the MLUE account, and deleting the MLUE account does not cancel an App Store subscription managed by Apple. Cancel that subscription separately in Apple’s subscription settings if you want recurring billing to stop.

After identity verification, we will respond to a request through the privacy request form or team@mlue.cn. We may retain or decline to delete information where necessary to perform a contract, protect another person, establish or defend a claim, preserve security, or meet a legal obligation, and will explain the reason where required.

13. Age requirement

Creator accounts are currently intended only for people aged 18 or older who can enter into the Terms of Service. MLUE does not knowingly offer creator registration and public publishing to children. If we learn that an ineligible child controls an account, we may restrict publishing and provide an appropriate contact, export or deletion route.

14. Changes and contact

We may update this policy as the service, data uses, providers or legal requirements change. The version and dates at the top will be updated. If a change materially affects personal rights, we will use an appropriate in-product, app or email notice; where renewed consent is required, changing this page alone will not replace that consent.

For privacy questions or requests, use the privacy request form or email team@mlue.cn.