QuMiro Privacy Policy
Last Updated:
I. Introduction and Scope of Application
This version was updated on October 7, 2026. Changes apply under the published effective-date arrangements after formal publication and completion of legally required notice or consent procedures. Updating a file does not automatically expand the purposes, scope, or retention periods of existing personal information processing.
QuMiro values your personal information and privacy. This Policy explains how we collect, use, store, share, transfer, publicly disclose, and protect personal information when providing interest-based social networking, content community, activity, messaging, notification, personal planning, and related services, and how you may exercise the relevant rights.
This Policy applies to the QuMiro iOS application and other services that expressly reference this Policy. Where a third party processes personal information through its independent product or service, that third party’s privacy rules apply.
We process personal information in accordance with privacy, data protection, cybersecurity, protection of minors, and other laws and regulations applicable to your location, the operator’s location, and the relevant processing activities. This Policy does not diminish rights that cannot be waived under applicable law.
II. Basic Principles for Our Processing of Personal Information
- Lawfulness, legitimacy, necessity, and good faith: We process only information directly related to the Services for specific and reasonable purposes.
- Minimum necessity: We will not refuse to provide basic features because you decline to provide nonessential information, but the corresponding additional features may be unavailable.
- Openness and transparency: We explain processing rules through this Policy, permission descriptions, page notices, or separate notifications.
- Purpose limitation: We do not process personal information in a manner unrelated to the purposes known to you; if a purpose materially changes, we will provide notice again and obtain consent in accordance with law.
- Security and accountability: We adopt technical and management measures appropriate to the risks and exercise necessary management over entrusted processors.
III. How We Collect and Use Personal Information
The following items are based on the current Service features. Whether information is actually collected depends on the features you use, the content you provide, device permissions, and the login methods available at runtime.
3.1 Account Registration, Login, and Security
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Email account information | Email address, email verification code and verification status, encrypted password hash, and password setup or reset records | Registration, login, identity verification, account recovery, and sending security emails | Necessary for email login; performance of the service contract, obtaining consent, and safeguarding account security |
| Apple login information | Apple user identifier, identity token, authorization code, and the name or relay email Apple provides with your authorization | Login with Sign in with Apple, identity linking, account merging, and revocation of authorization as required by Apple | Necessary for Apple login; performance of the service contract and based on your authorization |
| Agreement consent records | Codes, versions, and times of agreements accepted | Demonstrating your confirmation of the Terms of Service and Privacy Policy and managing version updates | Necessary for contract performance, legal obligations, and dispute handling |
| Session and security information | Internal user identifier, session identifier, token hash, successful or failed login, logout and revocation events, login method, login time, last activity time, revocation status, request time, request identifier, IP address, and abnormal verification records | Maintaining login status, managing device sessions, preventing account theft, abuse, and attacks, and troubleshooting | Necessary for performance of the service contract and safeguarding network and data security |
| Login device summary | Client platform, device model or type, operating system version, and App version and build number | Identifying the login environment, reviewing account sessions, investigating unusual logins, and troubleshooting | Necessary to safeguard account and Service security; unavailable optional fields do not block login |
| Installation identifier | Random installation UUID generated by the client; only a keyed hash separated by purpose is stored in login device and source records | Rate limiting and abuse prevention for unauthenticated authentication requests and helping associate an installation environment; not used as a public device identifier or advertising identifier | Necessary to safeguard account and Service security |
Verification codes, access tokens, and refresh tokens are sensitive security credentials. We process them only to the extent necessary for authentication and will not ask you to disclose them in posts, comments, or messages.
The login device summary does not collect the personal name you assign to your device. The server determines the source IP from trusted network connections and proxy configuration. Operational pages display masked addresses by default. Only personnel with dedicated permission may read an encrypted raw IP within its retention period when needed to investigate a security issue, and that access is audited. Login source records do not use an external IP geolocation service.
3.2 Profile and Social Relationships
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Basic profile | Nickname and profile picture | Creating an account profile and identifying users in the community and activities | Necessary to provide account and community features |
| Optional profile | Bio, city of residence, interest categories, language, profile visibility scope, and whether the profile can be found through search | Completing the profile, content and activity discovery, and language and privacy preferences | Proactively provided by you and may be modified or deleted |
| Social relationships | Following, follower, and blocking relationships and operation times | Providing following feeds, relationship management, blocking, and safety protection | Necessary to provide social features you actively use |
You may control the display of certain information through profile visibility scope and discoverability settings. Your nickname, profile picture, and public content may still be seen by other users in the community, activities, or shared pages.
3.3 Posts, Comments, and Interactions
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Published content | Post title, body, language, city, topics, visibility scope, associated activity, and publication time | Publishing, displaying, searching, and managing community content | Proactively submitted by you; performance of the content publishing service contract |
| Media and location | Images and profile pictures you choose to upload, image technical attributes, and manually selected place names and cities | Displaying images, profile pictures, and post locations | Proactively selected and provided by you |
| Comments and interactions | Comments, reply relationships, likes, favorites, and related times | Providing discussion, interaction, and content management | Proactively submitted or performed by you |
| Content governance information | Content status, version, and review or handling records | Preventing illegal or noncompliant content, handling complaints, and restoring content incorrectly classified | Fulfilling legal obligations and maintaining community safety |
Posts, comments, nicknames, profile pictures, location tags, and interaction statistics set as public are public information. Do not publish identity documents, precise residential addresses, private contact details, itineraries, health or financial information, information about minors, or other unnecessary sensitive personal information in public content.
3.4 Activity Publication, Registration, and Management
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Activity information | Title, summary, description, category, tags, time, time zone, number of participants, registration deadline, fee type and description, activity rules, and cover image | Creating, displaying, searching, and managing activities | Proactively submitted by the activity organizer |
| Location information | Country or region, city, district, and venue name; optional precise latitude and longitude, meeting point, and navigation information; location visibility scope | Displaying activity locations, providing navigation, and controlling precise locations under public or members-only visibility rules | Necessary for offline activities; precise locations are proactively entered by the organizer, who selects the visibility scope |
| Online participation information | Meeting or streaming link, platform name, room code, optional access code, and participation instructions | Providing online activity access and controlling display under activity access rules | Proactively provided by the organizer as needed for the online activity; do not enter personal login passwords or unrelated credentials |
| Participation information | Registration, application reason, member status, role, join or withdrawal time, and activity announcements | Processing registrations, managing members, sending activity notifications, and providing group access | Necessary to perform the service contract for an activity you initiate or participate in |
| Risk and governance information | Activity risk level, status changes, cancellation, suspension, member handling, and related records | Activity safety, dispute handling, and platform governance | Necessary to fulfill legal obligations and protect user safety |
Precise latitude and longitude, meeting points, and itineraries may constitute sensitive personal information. Activity organizers shall enter only the locations necessary for an activity and carefully set the visibility scope. Participants may not use members-only locations for purposes unrelated to the activity.
Online links, room codes, and access codes may also let a recipient enter a meeting or stream. Share them according to the actual visibility shown on the activity page and do not place members-only information in a public description. Once you enter a third-party meeting or stream, that service’s rules govern its processing of audio, video, nicknames, or access logs.
3.5 Messages and Notifications
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Conversations and messages | Conversation participants, message body or structured content, sending time, reply relationships, read position, unread count, message status, and pin, mute, and list visibility settings | Providing direct messages, message requests, activity group communications, and conversation management | Necessary to perform the messaging service contract |
| In-app notifications | Notification type, object identifier, content summary, read status, and creation time | Providing interaction, activity, message, security, and service reminders | Necessary for performance of the service contract and reasonable operations |
| Push information | APNs device token, sandbox or production environment identifier, token status, and notification category preferences | Sending notifications you choose to receive to your device and handling invalid tokens | Processed after you allow system notifications and enable the corresponding categories |
We will not use general notification settings to circumvent necessary notices concerning account security, agreement updates, or handling of illegal or noncompliant conduct. Push notification content will avoid unnecessary sensitive information where possible, but lock screen display remains determined by your device settings.
Removing a conversation from your own chat list changes only your list display and clears its unread state as part of the operation; it does not delete message history or the other person’s records. The conversation may reappear after a new message or when you start it again. This differs from deleting personal information or deleting your account. Message text is also subject to the content safety checks explained in Section 3.8.
3.6 Personal Plans and Reminders
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Plan content | Plan title, notes, date and time, time zone, location, recurrence rules, completion status, and associated activity | Creating and synchronizing personal tasks, schedules, and activity plans | Proactively submitted by you; performance of the planning service contract |
| Reminder information | Reminder lead time, reminder time, and reminder delivery records | Scheduling local or service notifications and avoiding duplicate reminders | Proactively set by you |
Personal plans are provided only to the account holder by default. Do not use QuMiro reminders as the sole reminder method for medical, emergency, or other high-risk matters.
3.7 Search, Recommendations, and Location Assistance
- When you enter search terms, filters, a city, or a location, we process those inputs to return posts, activities, users, or location results. The App locally caches up to 10 recent search terms on the device, with a default maximum cache period of 7 days; you may delete individual recent searches or clear them all. Search requests are sent to the server to return results, but the current Services do not create a server-side search history that is associated with your account on a long-term basis. The current Services primarily use user-initiated searches and rule-based ranking. If we enable personalized recommendations or server-side search profiling in the future, we will provide separate notice before enabling them.
- When you use city of residence recommendations, post or activity place selection, nearby place recommendations, or map positioning with “While Using the App” permission, the device supplies the location for that request to infer a city, limit the query area, recommend nearby places, or show your map position. Availability of approximate or precise location depends on system authorization. We do not continuously track your location in the background based on this permission.
- You may decline location authorization and select a city or place manually. Disabling permission affects only recommendations and positioning that depend on it. A place you select and publish with content has a different purpose from the device location used to assist that selection; it does not mean other users always see your live location.
- When you publish a post, we prefer the city resolved from your current location if you have already granted permission. If permission is unavailable or location lookup fails, we try to infer a city from the request IP address. The post stores only the city and source type, fixed at publication; it does not follow later movement or store raw IP addresses or precise coordinates in the publication-origin field. IP estimates can be inaccurate. If no reliable city is available, the origin is omitted without blocking publication.
- IP city lookup uses [DB-IP Lite](https://db-ip.com/db/lite.php) data hosted on our servers under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Lookup is local; this feature does not send your IP address to DB-IP.
3.8 Reports, Appeals, Credit, and Security Governance
| Information Type | Specific Information | Purpose of Use | Necessity and Processing Basis |
|---|---|---|---|
| Report information | Reporting user, reported user, target content or activity, reason, description, evidence reference, severity, and submission time | Accepting reports, verifying facts, and protecting users and community safety | Necessary to fulfill legal obligations and protect lawful rights and interests |
| Appeal information | Appellant, related enforcement action, reason for appeal, review result, and rationale | Providing appeal, correction, and restoration mechanisms | Necessary to fulfill legal obligations and safeguard user rights |
| Text rule match summaries | Internal user identifier, related content or conversation identifier when available, submission scenario, matched field, rule name or configured expression, category, observe or block result, rule version, recording time, request identifier, and a hash used to avoid duplicate records | Verifying matches for noncompliant or prohibited expressions, investigating false positives, refining rules, and handling necessary safety issues | Necessary for community and communication safety, protection of lawful rights, and applicable governance duties |
| Credit and restriction information | Rule trigger records, credit events, account or feature restrictions, duration, and revocation records | Enforcing community governance, preventing repeated harm, and handling disputes | Necessary to maintain Service security and lawful rights and interests |
Reports, appeals, and evidence involving other users shall be submitted only to the extent necessary. We may restrict disclosure of some information to relevant parties in order to protect the safety of reporting users, witnesses, or other users.
Current text rules process controlled text when submitted, including posts, comments, profiles, activity instructions, and direct and activity group messages, and match enabled Chinese, English, and variant expressions. Observation records necessary summaries only; blocking may reject that submission. A text match alone does not automatically deduct credit or impose an account penalty. Section IX of the “QuMiro Terms of Service” explains false-positive feedback and review.
The match register does not additionally store the complete submitted text or raw IP addresses. Original messages, posts, and other content remain subject to their own business purposes and retention rules. Matched expressions come from rule configuration or match summaries, and the deduplication hash is a necessary derived record; the register must not be treated as free of personal information. Access is limited to personnel with the appropriate permission. Records are not public or used for advertising or sensitive identity profiling, nor are they a complete evidence record or real-time monitoring record of all violations. Section IX sets out retention.
3.9 Customer Service, Complaints, and Operational Communications
When you contact us by email, in-app feedback, or another public channel, we process your contact details, account identifier, issue description, screenshots, attachments, and communication records to verify identity, respond to requests, troubleshoot issues, and retain handling records. Do not submit sensitive personal information unrelated to the issue.
IV. Device Permissions
You may manage permissions in iOS system settings. Refusing or disabling a permission will not affect basic features that do not depend on that permission.
| System Permission | Trigger Scenario | Processing Method and Impact |
|---|---|---|
| Location While Using the App | City of residence recommendations, post or activity place selection, nearby place recommendations, and map positioning | The current approximate or precise location assists city or place selection or shows your map position; manual selection remains available without permission, and no continuous background location is performed |
| Camera | You actively scan a QR code for a QuMiro user, activity, or post | Used to recognize the QR code in the camera view; if refused, the scanning feature will be unavailable |
| Photo picker | You actively select a profile picture, post image, or activity cover image | Reads the items you select through the system photo picker and does not require access to the entire photo library |
| Notifications | You choose to enable push notifications or plan reminders | Used to display reminders, sounds, and badges; corresponding categories may be disabled in system settings or within the application |
V. Legal Bases for Our Processing of Personal Information
Depending on the laws applicable to the relevant processing activities and the actual circumstances, we process personal information on one or more of the following grounds only where those laws permit them and the corresponding conditions are met:
- Obtaining your consent or separate consent;
- Necessity for concluding or performing a contract to which you are a party;
- Necessity for performing statutory duties or legal obligations;
- Necessity for responding to a public health emergency or, in an emergency, protecting the life, health, and property safety of natural persons;
- Processing, within a reasonable scope, personal information that you have disclosed yourself or that has otherwise been lawfully disclosed;
- Other lawful grounds for processing provided by applicable law.
Where processing relies on consent, you have the right to withdraw consent, but withdrawal does not affect processing activities already carried out on the basis of consent before withdrawal.
VI. Cookies, Advertising Identifiers, and Automated Decision-Making
- The QuMiro iOS application does not rely on Cookies to provide basic native application features. If we provide services through webpages and use necessary Cookies to store sessions, security settings, or language preferences, we will provide corresponding explanations and controls separately on the webpages.
- The current version does not collect IDFA for advertising purposes, does not sell personal information, and does not integrate advertising SDKs used for cross-App tracking. If this changes in the future, we will update this Policy and obtain consent in accordance with law before enabling such processing.
- The current version does not impose account penalties through solely automated decision-making that has a material impact on personal rights and interests. Text matching may automatically reject the relevant submission, while observation does not impose an automatic penalty. Matching can produce false positives or miss harmful content; you may edit content or request an explanation or review. Search ranking, risk rules, or anti-abuse signals may assist content display and security determinations; major governance decisions will provide manual review or appeal channels.
VII. How We Entrust Processing, Share, Transfer, and Publicly Disclose Personal Information
7.1 Entrusted Processing
To provide infrastructure, email, storage, push notification, security, or customer service capabilities, we may entrust service providers to process necessary information. We will agree with entrusted parties on the purpose, period, and method of processing, the categories of information, protection measures, and the responsibilities of both parties, and will supervise their processing activities.
7.2 Sharing
Except in the following circumstances, we will not provide your personal information to other personal information processors:
- After obtaining your separate consent;
- Where necessary to perform an activity, transaction, or other contract in which you participate, and after we have explained the recipient and processing rules to you;
- In accordance with laws and regulations, legal proceedings, or lawful requests made by competent authorities;
- Where necessary to protect your or other users’ or the public’s life, health, property safety, or major lawful rights and interests, and it is difficult to obtain the individual’s consent;
- Where a transfer is genuinely necessary due to a corporate merger, division, restructuring, asset transfer, or similar transaction, we will inform you of the recipient and require the recipient to continue complying with this Policy; if the purpose or method of processing changes, the recipient shall obtain consent again in accordance with law.
7.3 Public Disclosure
We publicly disclose personal information only when you actively publish it publicly, when we have obtained separate consent in accordance with law, or when required by laws and regulations or competent authorities. Posts, comments, public activities, public profiles, and public locations will be displayed to other users according to the visibility scope you select.
7.4 List of Third-Party Services
The following third-party services process necessary information only when the corresponding feature is actually enabled and you use that feature.
| Third Party or Service Type | Information That May Be Processed | Purpose | Role and Notice |
|---|---|---|---|
| Apple Inc. and its affiliates - Sign in with Apple | Apple user identifier, identity token, authorization code, name or email you authorize Apple to provide, and device and network information | Apple login, identity linking, and revocation of authorization | Apple independently processes its login interface and account services; Apple’s published rules prevail |
| Apple Inc. and its affiliates - Apple Push Notification service (APNs) | Device token, App identifier, notification payload, and delivery status | Sending push notifications to iOS devices | Used only after you allow notifications and enable push notifications; lock screen display is controlled by device settings |
| Apple Inc. and its affiliates - MapKit, maps, and location services | Location search terms and query region you enter, and approximate or precise location when you authorize its use | Location search, map display, city recommendations, and navigation assistance | Apple may independently process request information under its own rules |
| Email delivery technical services | Recipient email address, verification code or necessary service email content, and sending status | Sending registration, login, password reset, and service emails | Relevant technical service providers process necessary information only within the scope entrusted by us |
The current version does not integrate analytics, advertising, payment, contacts, or third-party crash analytics SDKs. We will continuously verify the SDKs, network requests, and App Store privacy labels actually used as the Services are updated and will update this Policy when processing methods change.
VIII. Personal Information Storage and Cross-Border Processing
- Personal information is stored and processed where the infrastructure that we and our entrusted technical service providers actually use is located. Those locations may differ from your country or region. We comply with data localization, cross-border transfer, and related protection requirements under applicable law; storage and processing locations depend on actual Service deployments and technical service provider configurations.
- Sign in with Apple, APNs, map services, or other global third parties may process relevant information through infrastructure in different countries or regions. To the extent required by applicable law, we will verify cross-border scenarios, adopt applicable standard contracts, certification, security assessments, or other lawful mechanisms, and, where legally required, inform you of the cross-border recipient’s name and contact details, the purpose and method of processing, the categories of information, and the method for exercising rights, and obtain your separate consent.
- If the Services involve a new cross-border personal information processing scenario, before carrying out the relevant processing we will supplement the cross-border recipient and processing rules in accordance with law and fulfill the notification, separate consent, and other obligations required by applicable law.
IX. Retention Periods for Personal Information
We retain personal information only for the shortest period necessary to achieve the purposes described in this Policy. Where laws and regulations prescribe a minimum retention period, or retention is genuinely necessary for litigation, dispute handling, or security audits, we retain it for the corresponding period. The data retention principles for the current Services are as follows:
| Information Category | General Retention Principle |
|---|---|
| Account, login identity, and profile | Retained while the account exists; after account deletion, use will cease and the information will be deleted or anonymized, while necessary account status and deletion records may continue to be retained for fraud prevention, dispute handling, and fulfillment of legal obligations |
| Authentication sessions, refresh history, and session device summaries | Retained while a session is valid or recoverable; related records are cleaned up as a session group 30 days after absolute expiration or 30 days after revocation. Short-term inactivity is not absolute expiration and does not cause early deletion of records needed for session recovery and refresh-token reuse detection |
| Verification codes | Used for authentication during their validity periods; after expiration or use they no longer serve as valid credentials, while related hashes, statuses, and security records are retained as necessary for cybersecurity and abuse prevention |
| Login device and source events | Newly recorded successful or failed login, logout, and revocation events are retained for at most 30 days, with a shorter period used where appropriate; queries stop at expiration and cleanup tasks delete the records. Shorter periods apply to existing records; a later increase does not extend older records or restore expired records. This period does not determine retention of valid or recoverable sessions |
| Raw login source IP addresses | When retention is necessary, stored separately in encrypted form for at most 10 days and no longer than the associated event. A shorter period may apply, or storage may be disabled. Read access stops immediately at expiration and cleanup tasks delete the records in batches. Tasks run hourly; completion depends on normal task operation and the cleanup backlog |
| Posts, comments, activities, messages, and media | Retained while you use the corresponding features; after you delete or withdraw them or delete your account, they will cease to be displayed or will be deleted or anonymized according to product capabilities, but information necessary for discussion structure, activity safety, other persons’ rights and interests, backup rotation, and dispute handling may be retained for a necessary period |
| Precise activity locations | Retained during the period necessary for activity organization, performance, and safety handling; after an activity ends or is canceled, no longer used for real-time activity organization, but may be retained on a restricted basis for the period necessary to handle incidents or complaints or fulfill legal obligations |
| Personal plans | Retained while the account exists and the plan has not been deleted; deleted through system processes after the plan is deleted or the account is deleted, with backup copies cleared after the rotation cycle ends |
| Recent search terms | Up to 10 terms, cached only on the current device for a default maximum of 7 days; you may delete them individually or clear them all from the search page, and they may be deleted earlier if the system clears the App cache |
| Text rule match records | Retained for 30 days by default. The administrative configuration permits 1–365 days, but the shortest necessary period must be chosen for false-positive investigations, safety governance, and applicable law; configuration capacity alone does not justify an extension. Queries and cleanup use the period then in effect, and expired records are excluded from the ordinary register. Cleanup runs hourly in batches; completion depends on task operation and the backlog. Retention changes requiring notice follow Section XIV, and deleted records cannot be restored. This configuration is independent of the login-event and raw-IP retention limits |
| Push device tokens | Retained while the device registration remains valid and you allow push notifications; disabled or deleted after you sign out of the device, disable the relevant service, or the token becomes invalid |
| Report, appeal, credit, restriction, and audit records | Retained for the period necessary for case handling, appeals, limitation periods, platform governance, and legal obligations, with access restricted |
| Customer service and rights request records | Retained for the period necessary to complete requests, demonstrate handling results, and resolve disputes |
| Governance and security operational audits | Retained with restricted access for security governance, dispute handling, and legal obligations; operation types and user or session identifiers in existing authentication audits are separate from login device and source events and do not contain those events’ raw IP addresses or device summaries |
| Proxy logs and backup copies | Managed separately under the applicable infrastructure log retention and backup rotation policies. The 30-day event and 10-day raw IP periods above apply to business records and do not mean that all technical logs or backup copies are cleared on the same day. Backups are used only for disaster recovery and are overwritten or deleted within the applicable rotation cycle |
X. How We Protect Personal Information
- We protect personal information through identity authentication, least privilege, transmission encryption, credential hashing or encryption, access controls, operational audits, backup and recovery, rate limiting, anti-abuse measures, security incident response, and other measures.
- Passwords are verified in an irreversible manner, and the server does not store your passwords in plaintext; highly sensitive credentials such as Apple authorization credentials are stored using encryption and subject to restricted access.
- We restrict access through identity and permission rules for nonpublic information such as precise activity locations, direct messages, personal plans, reports, and appeals. Users shall nevertheless properly safeguard their accounts and share public links with caution.
- No internet service is absolutely secure. If personal information has been or may have been leaked, altered, or lost, we will immediately take remedial measures and notify competent authorities and affected individuals, as required by law, of the type of incident, potential impact, measures taken or to be taken, recommendations for reducing risks, and contact details, except where the law permits us not to notify individuals.
XI. Your Personal Information Rights
To the extent provided by applicable law, you have the right to:
- Be informed and make decisions: Understand and decide how we process your personal information;
- Restrict or refuse: Restrict or refuse processing based on consent or in nonessential scenarios;
- Access and copy: Access account profile, content, activity, plan, and other information and request a copy in accordance with law;
- Correct and supplement: Modify inaccurate or incomplete information in your profile, account security settings, or related features;
- Delete: Delete content, plans, or other deletable information you publish, or request that we delete information when statutory conditions are met;
- Withdraw consent: Disable system permissions, notification categories, or related features to withdraw consent-based processing;
- Delete your account: Submit an account deletion request through “Me - Settings - Account & Privacy - Account Security - Delete account”;
- Request explanations: Require us to explain the personal information processing rules;
- Complain and appeal: Submit complaints, reports, or appeals regarding personal information processing or account governance decisions;
- Rights relating to deceased users: Where permitted by law and where the user did not make other arrangements before death, close relatives may exercise rights of access, copying, correction, deletion, and other rights in accordance with law for lawful and legitimate interests.
You may submit a request through in-product features or the privacy contact email specified in this Policy. To protect account security, we may verify your identity, account ownership, and the scope of the request. We generally respond within fifteen business days; for complex requests or where the law provides another time limit, we will explain the processing progress.
Where permitted by law, we may refuse or restrict processing of requests that are repetitive, manifestly without legitimate grounds, require excessive technical costs, may harm another person’s lawful rights and interests, or are submitted by a person whose identity cannot be verified, and we will explain the reasons. You may still lodge a complaint with the competent personal information protection authority.
XII. Account Deletion
- You may initiate account deletion through “Me - Settings - Account & Privacy - Account Security - Delete account” in the application. Before deletion, the system will require your confirmation and may require you to first handle ongoing activities or other unfinished matters.
- After account deletion is completed, we will revoke login sessions and login identities and stop providing account services. The email login identifier will be disassociated directly from the original account according to the system design; Apple authorization will be revoked as required by Apple, or incomplete deletion will be prevented if authorization cannot be safely revoked.
- The profile will cease to be displayed publicly and will be deleted or anonymized. User Content, activities, member relationships, reports and appeals, and audit records will be hidden, deleted, anonymized, or retained on a restricted basis according to other users’ rights and interests, content structure, activity safety, dispute handling, and legal obligations.
- Copies in backups will be overwritten or deleted during the normal backup rotation cycle; during that period they will be used only for disaster recovery and no longer for routine business processing.
XIII. Protection of Minors’ Personal Information
- The Services are primarily intended for adults. Minors shall use the Services under the guidance of a guardian and comply with applicable legal requirements concerning age, guardian consent, and children’s personal information protection. Where applicable law requires stricter protection, those requirements apply.
- Children under the age of fourteen shall use account-based Services only with guardian consent and after we provide dedicated protection mechanisms. Until we provide such mechanisms, children under the age of fourteen shall not register an account or submit personal information.
- If we discover that we have collected a child’s personal information without guardian consent, we will delete it or take other necessary measures as soon as possible after verification. A guardian may request access to, correction of, or deletion of the relevant information through the privacy contact email.
- Minors and guardians shall exercise caution when publishing photos, school information, residential addresses, precise locations, itineraries, and contact details, and when participating in offline activities organized by strangers.
XIV. Policy Updates
- We may update this Policy due to changes in laws and regulations, Service features, third parties, or data processing methods, and will publish it within the application, on webpages, or at another reasonable location.
- We will highlight through pop-ups, notifications, or other prominent means changes that materially affect processing purposes or methods, categories of personal information, retention periods, recipients, or your rights. Where consent or separate consent is required by law, we will obtain consent again. A file edit or administrative configuration change does not retroactively expand existing authorization; we will not process existing personal information for a new purpose before required notice or consent is completed.
- Historical versions of this Policy and the versions accepted by users will be retained as necessary under law and for dispute handling.
XV. Contact Us
If you have questions, comments, complaints, or reports concerning this Policy, personal information processing, or the exercise of rights, you may contact us through the following methods:
- Personal Information Processor: Chengdu Qumai Technology Co., Ltd.
- Privacy Contact Email: support@qumiro.com
- In-App Path: Me - Settings - Account & Privacy - Account Security, or the customer service and feedback channel published at the relevant time
We generally verify and respond within fifteen business days; where applicable law specifies another time limit, we follow that limit. If you are dissatisfied with the handling result, you may submit a complaint or report to the competent privacy or data protection authority, or bring proceedings before a court with jurisdiction in accordance with law.