Privacy Policy

01   Who is responsible and what this covers

REALM DATA LIMITED is the operator responsible for Monu (怪伴) and this website. Contact our privacy team at support@yumiecho.com. Our registered address and country of incorporation are pending confirmation. The planned launch is limited to the United States and users aged 18 or older.

This review draft describes the current Android and iOS development implementations. It is not yet an effective release policy. Final provider arrangements, retention periods, deletion handling, hosting, and the effective date must be confirmed before publication. Platform and version differences are identified below.

02   Account and profile information

Google sign-in supplies an account identifier and authentication credentials so the App can sign you in and separate local account data. Android uses the stable Google subject identifier for the local session. The iOS implementation also receives and stores the Google email address and display name in its local session. We do not receive your Google password.

The App stores the nickname and birthday or age-range profile information you enter, onboarding status, chosen companion, collection progress, and language preferences on your device. These support your profile and companion experience. The reviewed AI request code does not automatically append Google identity, email, or profile birthday to chat requests; information you put in a message can still be included.

03   Messages, memories, and sensitive information

Your messages, AI replies, message identifiers and timestamps, companion identifiers, and generated memory titles, summaries, and topic metadata are stored locally to display conversations and maintain continuity. Companion progress is calculated from qualifying replies. Memory removal flags can be kept to avoid recreating a removed topic.

Conversations may reveal emotions, relationships, health concerns, or other sensitive information. These details are not required profile fields. Avoid sharing passwords, payment details, exact location, or unnecessary sensitive information about yourself or others. Choosing to include such details in text or transcribed speech can cause them to be sent to the AI provider.

04   AI processing and the information sent

The App connects directly over HTTPS to the DeepSeek API at api.deepseek.com. For replies, it sends the current text, selected recent conversation context, and instructions describing the companion’s personality. A voice message is transcribed locally; its text, rather than the audio file, is sent through this AI flow.

The same provider is used to assess ambiguous safety risks and identify conversation memories. These requests can include user text, selected messages and their identifiers and roles, and existing topic keys, titles, and removal flags. AI processing is therefore not limited to the visible reply. Requests also expose network information such as your IP address and ordinary connection metadata to the receiving service.

Before release, the App must clearly identify this recipient, the data and purposes, and obtain the required explicit permission before sending personal information. Microphone permission, Google sign-in, and accepting general terms do not replace that permission. Declining AI transmission means online AI replies and related AI analysis cannot operate; you can avoid sending further content by not using those features.

05   Microphone and local voice processing

Microphone access is used when you choose voice input. The current implementations record audio in the App’s private storage and use bundled Vosk models for on-device speech recognition. Saved voice messages can be played back. Audio may remain after transcription fails so that you can retry. The reviewed voice-to-AI path does not upload the original audio to DeepSeek or use a cloud transcription service.

You can deny or revoke microphone permission in your device settings and use text input instead. Revoking permission stops future microphone access; it does not erase recordings already saved. No camera, contacts, photo-library, or precise-location permission is requested by the reviewed App configuration. Text may still contain information you choose to provide.

06   Service providers and other recipients

Google processes authentication through its sign-in services. DeepSeek processes the AI requests described above. Their processing is subject to the applicable service arrangements and their own legal obligations; we remain responsible for the disclosures and controls required for Monu. Vosk is used as an on-device recognition library, not a remote recipient in this implementation.

DeepSeek’s public consumer privacy policy explicitly excludes the processing rules for end users of downstream developer applications. It is background information, not a substitute for the contract and data-processing terms that apply to Monu’s API usage. The applicable contracting entity, processing locations, retention, deletion assistance, and any training or human review of requests remain unverified. We therefore do not promise zero retention or exclusion from model training.

If you email support@yumiecho.com, the operator and its email service process your address, message, and any attachments to respond and handle requests. Send only necessary information. The email provider and its retention arrangements must be documented before release. Information may also be disclosed where required by law or necessary to address a legitimate security or legal claim, subject to applicable safeguards.

07   Website, advertising, and analytics

The current static website does not set analytics or advertising cookies, use tracking pixels, offer a registration form, or store a language preference. Choosing English or Chinese opens a different public page. Fonts and product images are served with the website. Following an external link or opening an email app involves that destination’s services.

When hosted publicly, requests will necessarily reach the hosting provider with information such as IP address, requested URL, and browser connection headers. The production host, access-log settings, recipients, and retention period are not yet selected. The reviewed App dependencies do not show an advertising, behavioral analytics, or purchase SDK; this is not a promise about unconfirmed future integrations.

The reviewed implementation does not contain a mechanism to sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. Future integrations must be reviewed before launch or introduction, including any required opt-out controls. AI processing is disclosed separately and must not be described as “no data sharing”.

08   Storage, security, and international transfers

Profiles, conversation databases, recordings, memories, and progress are primarily stored in the App’s private device storage and separated by account. iOS uses Keychain for its local Google session. HTTPS protects the reviewed AI requests in transit. Device storage and operating-system protection do not amount to a guarantee of end-to-end encryption or perfect security.

Monu does not currently operate a conversation synchronization backend. However, operating-system backup or device-transfer services may copy local app data depending on platform settings and the release configuration; Android currently allows system backup. Device loss, app-data removal, and backup restoration can affect availability and deletion. Local storage does not mean information can never leave the device.

Use from the United States can involve processing outside the United States by Google or DeepSeek. DeepSeek’s general service policy describes processing in China, but the exact locations and safeguards applicable to this API integration have not been confirmed. Before release we must document the actual countries and arrangements and assess applicable cross-border restrictions; no data-residency or transfer-compliance assurance is made by this draft.

09   How long information is kept

Local profile, chat, recording, memory, and progress data currently remain until removed by the applicable App controls or device-storage management. There is no verified automatic time-based expiry. Signing out preserves these records. Recordings associated with a cleared conversation are removed through the chat-clear flow. Removing a memory card can retain its source messages and removal metadata.

Google and DeepSeek may retain data under their applicable service arrangements. Clearing local data does not automatically erase a provider’s records. The API request/log retention periods, backup retention, support-email retention, and any legally required exceptions must be specified before release. We will not substitute an invented number of days or an unsupported “never stored” claim for those facts.

10   Your controls and deletion requests

You can view your local conversations, edit your profile, remove memories from the list, and clear a companion’s chat using the available App controls. A cleared chat does not reset all profile information or revoke already claimed companions. Removing a memory is not the same as deleting its underlying conversation.

For a Monu account or personal-data deletion request, email support@yumiecho.com with the subject “Monu deletion request”. Identify the sign-in email if available, the device platform, and whether you want an entire account or specific data deleted. Do not send a password, ID token, or private conversations. We may need proportionate information to verify that you are entitled to make the request.

This email is the designated request channel; the support workflow, response timing, provider-deletion coordination, and complete in-app account deletion flow have not yet been verified. This draft is not proof that account deletion is implemented or that a request has been completed. We cannot remotely erase device-only records through a backend that does not exist; local removal instructions and provider handling must be part of the final process.

Signing out only ends the local session. Uninstalling or clearing app storage may remove local files but does not necessarily remove system backups, iOS Keychain items, Google service records, or data already sent to DeepSeek. Revoking Monu’s access through Google account settings does not itself erase those records or delete your Google account. Do not rely on any one of these actions as complete deletion.

11   Privacy rights and sensitive-data choices

Depending on applicable U.S. federal or state law and its scope, you may have rights to know or access personal information, correct inaccuracies, obtain a portable copy, request deletion, restrict certain sensitive-data uses, or opt out of sale, sharing, targeted advertising, or certain profiling. We do not promise that a particular state statute applies to every user or that an automated export tool currently exists.

Contact support@yumiecho.com to exercise applicable rights, withdraw consent, ask about a request decision, or submit an appeal where available. An authorized agent may contact us subject to reasonable verification. We will handle requests within the time required by applicable law, explain applicable exceptions, and not unlawfully discriminate for exercising rights. You may also contact the relevant state regulator.

Withdrawing AI permission applies to future processing and does not by itself reverse earlier transmission. A usable in-app withdrawal control and any additional consent and policy required for consumer health or other sensitive data must be completed and checked for the intended U.S. release. Monu is not a healthcare provider and does not promise HIPAA coverage or medical confidentiality.

12   Adults only and information about minors

Monu is intended for adults aged 18 or older and is not directed to children. People under 18 must not use it, even with parental permission. If you believe an underage person has used Monu or provided personal information, contact support@yumiecho.com so the matter can be assessed and appropriate access and deletion steps taken.

Do not upload personal information about children or other people unless you have lawful authority and a necessary reason. The release must enforce its adult-only audience policy; this webpage alone is not an age-verification mechanism.

13   Changes, language, and contact

We will update this policy when actual processing changes, identify the effective date, and provide appropriate notice of material changes. Where a new use requires permission, we will obtain it before that use. English is the default; Simplified Chinese is available and is intended to carry the same meaning.

Operator: REALM DATA LIMITED. Privacy, support, complaints, appeals, and deletion requests: support@yumiecho.com. Registered address, country of incorporation, production domain, and effective date: pending confirmation. Review draft updated October 14, 2026.