Privacy Policy
Last updated: 29 May 2026
Effective date: 29 May 2026
Welcome to Memene (the "Platform"). Hangzhou Yuansun Technology Co., Ltd. and its affiliate Hong Kong Artificial Intelligence Association (collectively "we") operate and provide the services. We attach great importance to your privacy and personal information security. This policy explains how we collect, use, store, disclose and protect your personal information when you access or use Memene and the related services (the "Services").
Please read this privacy policy carefully before using the Platform, especially the highlighted parts, to understand how we handle your personal information. By choosing to continue using Memene, you agree that we may process your personal information in the manner described herein.
1. How we collect and use your personal information
1.1 Information you actively provide
We may collect the following personal information in the scenarios described below in order to deliver our Services:
1.1.1 Account registration and sign-in
When you register or sign in via email or a third-party account (such as WeChat or GitHub) we may collect:
- Email address for account creation and verification;
- Username and avatar obtained through authorised third-party login;
- Public information from third-party accounts within the permission scope you grant.
1.1.2 Content creation and interaction
When you publish or interact with content on Memene, we may store:
- Content you submit such as text, images or video;
- Your IP address and device information used for security auditing.
1.1.3 Subscription and notifications
If you subscribe to newsletters or notifications, we may collect:
- Email address for delivering daily briefings and important updates;
- Device information to send personalised push notifications.
1.2 Information obtained from third parties
Where permitted by law, we may obtain supplementary information from third parties (such as social networks or advertising partners) to offer better personalisation and analytics. We will ensure that these third parties have obtained your consent before sharing information.
1.4 Device identifiers and installed app information (Android App)
To deliver push notifications, enable third-party login and protect account security, the App may process the following information when implementing related features. We only process data within the scope necessary for those features and do not use it for advertising profiling unrelated to our services.
| Information type | Purpose | Collection method | Scope of use |
|---|---|---|---|
| Device MAC address / network hardware address / OAID and similar device identifiers | Register Alibaba Cloud and OEM push channels, bind push targets, one-tap login environment verification, account and push security | Automatically read on device by Alibaba Cloud Mobile Push SDK, OPPO/Xiaomi/Huawei/Honor/vivo push SDKs, and Alibaba Cloud number authentication SDK; Android 10+ may use OAID instead of MAC | Push registration and delivery, login and security only; stored on servers in China; not sold or shared with unrelated third parties |
| Installed app list / installed application information | (1) Detect whether WeChat is installed to provide WeChat login; (2) Number authentication SDK terminal environment security checks to prevent fraud and abnormal login | WeChat Open Platform SDK checks whether WeChat client is installed; number authentication SDK performs environment checks (not full app-store-style profiling) | Login and security scenarios only; not used for targeted marketing or sharing full install lists with unrelated third parties |
- You may disable notification permission in system settings to stop push-related processing; if you decline WeChat login, we will not query WeChat installation status for that purpose.
- See Chapter 10 for the full third-party SDK list.
1.3 How we use your personal information
- To create and maintain your account;
- To provide personalised content, recommendations and notifications;
- To ensure platform security, prevent fraud and troubleshoot issues;
- To comply with legal obligations or cooperate with competent authorities.
2. How we share, transfer or disclose your personal information
2.1 Sharing
We do not share your personal information with companies, organisations or individuals outside of Memene unless:
- We obtain your explicit consent;
- Sharing is necessary to provide core features (for example, service providers that support message delivery);
- Sharing is required by law or competent authorities.
2.2 Transfer
If Memene undergoes a merger, acquisition or restructuring, your personal information may be transferred to the new operator. We will require the new operator to continue to comply with this policy or obtain your consent again.
2.3 Public disclosure
We will not publicly disclose your personal information unless you explicitly agree or disclosure is required by law.
3. How we store and protect your information
3.1 Storage location and period
Your personal information is generally stored within China. We retain it only for the period necessary to achieve the purposes described in this policy, unless laws require a longer retention period.
3.2 Security measures
We adopt industry-standard measures such as encryption, access control and security audits to protect your data. Although we work hard to safeguard your information, the internet is not absolutely secure, so please keep your account credentials safe and create strong passwords.
4. Your rights
You have the following rights under applicable laws:
- Access and correction: you may view and edit your personal information in the account settings;
- Deletion: you may request deletion of your account and related data where permitted by law;
- Withdrawal of consent: you may adjust your notification preferences or unsubscribe from newsletters at any time.
If you wish to exercise these rights, please contact us at official@hkai.ai.
5. Cookies and similar technologies
We use cookies and tracking technologies to improve your experience. You can adjust cookie settings in your browser, but disabling cookies may affect certain features.
6. Protection of minors
Memene is intended for users aged 18 and above. If we learn that information from minors was collected without guardian consent, we will delete it promptly.
7. Updates to this policy
We may update this policy from time to time. If the changes are material we will notify you via website announcements, email or other reasonable means. Please review the latest version regularly.
8. Contact us
If you have any questions or requests about this policy, please contact us at official@hkai.ai. We will respond within 30 days.
This policy applies to Memene and its related services. Third-party services accessed through the Platform are subject to their own privacy policies.
9. Account Closure
You may request to deactivate your account at any time by sending an email to official@hkai.ai. Please use your registered email address and specify "Account Deactivation Request" to facilitate identity verification. After confirming your identity and ensuring there are no outstanding matters, we will complete the account deactivation within 15 business days and delete or anonymize your personal information within 30 days.
- Your account information and identifiable personal data will be deleted or anonymized;
- Information related to others or public content may be retained in an anonymous form;
- Due to legal, financial, or security requirements, we may retain certain records for the minimum necessary period as required by law.
Deleted data may be retained in an isolated environment for up to 90 days due to system backups and will be automatically purged upon expiration. Once the account deactivation is completed, it cannot be restored.
10. App-Specific Information
To ensure the normal operation and service functionality of the Memene mobile application on iOS and Android platforms, this section provides supplementary information regarding third-party SDKs and system permissions used in the App version. If you only use the Web version, you may skip this section.
10.1 Scope of Application
This section applies to the Memene mobile application downloaded and installed through the App Store, Android app stores, or other official channels.
The application is jointly operated by Hangzhou Yuansun Technology Co., Ltd. and its affiliate Hong Kong Artificial Intelligence Association.
10.2 Third-Party SDK Information
To enable third-party login, push notifications, number authentication and other features, we have integrated the following third-party SDKs in the App.
Some SDKs may involve device MAC address, OAID and similar identifiers, as well as installed app information read for WeChat login and number authentication security checks. We only call relevant interfaces when necessary and strictly follow data minimization.
| SDK Name | Provider | Data Collected | Purpose | Privacy Policy |
|---|---|---|---|---|
| WeChat Open Platform SDK (expo-wechat) | Tencent Technology (Shenzhen) Co., Ltd. | WeChat OpenID, UnionID, nickname, avatar; device identifiers; checks whether WeChat is installed for WeChat login | Third-party login; detect WeChat installation to launch authorization | View Privacy Policy |
| Alibaba Cloud Number Authentication SDK | Alibaba Cloud Computing Co., Ltd. | Mobile number (from carrier gateway), device identifiers, network info, terminal environment info (including installed app info for security checks) | One-tap phone login; terminal environment security and anti-fraud | View Privacy Policy |
| Alibaba Cloud Mobile Push (EMAS Push) | Alibaba Cloud Computing Co., Ltd. | Device identifiers (MAC/OAID/Android ID etc.), push token, device model, OS version, network status | Push registration, message delivery and delivery statistics | View Privacy Policy |
| OPPO PUSH SDK | Guangdong HeyTap Technology Co., Ltd. | Device identifiers, RegId, device model, OS version | OEM push channel on OPPO devices | View Privacy Policy |
| Xiaomi Push SDK | Beijing Xiaomi Mobile Software Co., Ltd. | Device identifiers, RegId, device model | OEM push channel on Xiaomi devices | View Privacy Policy |
| Huawei HMS Push / Honor Push SDK | Huawei Software Technologies Co., Ltd. / Honor Device Co., Ltd. | Device identifiers, Push Token, device model | OEM push channel on Huawei / Honor devices | View Privacy Policy |
| vivo Push SDK | vivo Mobile Communication Co., Ltd. | Device identifiers, RegId | OEM push channel on vivo devices | View Privacy Policy |
| expo-notifications | Expo, Inc. | Notification permission status, device model, OS version | Request system notification permission; manage local notification channels | View Privacy Policy |
| Apple Push Notification service (APNs) | Apple Inc. | Push registration token (Device Token) | iOS push channel for subscription updates, interaction messages and system notifications | View Privacy Policy |
We do not collect personal information unrelated to our services through the above SDKs, nor do we use the collected information for unauthorized purposes.
For specific data processing methods of third-party SDKs, please refer to their respective privacy policies.
10.3 System Permissions
To ensure the core functionality of the application, we may request the following system permissions.
You can manually enable or disable these permissions in system settings, but disabling them may affect certain features.
| Permission | Purpose | Required |
|---|---|---|
| Network access | Connect to servers, load news content, sync data | Yes |
| Storage read/write | Cache article images, save preferences | No |
| Notification | Receive push notifications such as subscription updates and interaction messages | No |
| Device information | Read the system-provided Android ID (Settings.Secure.ANDROID_ID) as a device identifier, used for push channel binding, message deduplication and sign-in device recognition. We do not read sensitive identifiers such as IMEI, MAC address, IMSI or SIM serial number. | No (declining prevents push delivery but does not affect core features such as reading or sign-in) |
We will not access sensitive permissions such as contacts, photo albums, camera, microphone, or location without authorization.
10.4 Data Security and Cross-Border Transfer
Data storage and processing for the App version are consistent with the Web version, all completed on servers within China.
We will not actively transfer personal information overseas unless required by laws and regulations or with your explicit authorization.
10.5 App Self-Start and Associated-Start Disclosure
To ensure that push notifications, subscription updates and other notification services are delivered in a timely manner, the App integrates Alibaba Cloud Mobile Push and OEM push SDKs (OPPO, Xiaomi, Huawei, Honor, vivo on Android) and Apple Push Notification service (iOS). When a new notification arrives, the operating system wakes the App's process through these push channels to deliver the message; when you tap a notification in the system notification tray, the operating system launches the App and navigates to the corresponding page. These behaviors constitute App self-start / associated-start. Details are as follows:
| Item | Description |
|---|---|
| Trigger scenario | (1) When a push message is received, the system push service wakes the App's process to deliver the message; (2) when you tap a notification in the system tray, the OS launches the App and navigates to the corresponding page. |
| Purpose | To ensure timely delivery of subscription updates, interaction messages and system notifications. |
| Frequency | Triggered only when a push is received or when you actively tap a notification. The App does not run continuously in the background, nor is it woken on a timer. |
| Necessity | The push mechanisms of mobile operating systems require the App to register system broadcast receivers; without them, you cannot receive any notification while the App is closed. |
| Third-party App association | The App does not actively start any third-party App. If, after tapping a notification, you are taken to a browser, WeChat or other apps, those launches are triggered by your own actions. |
How to disable: You may turn off the push toggle at Profile → Push Management → APP Push, which will guide you to the system notification settings page to revoke this app's notification permission. You may also revoke the notification permission directly in system settings. Once disabled, the self-start / associated-start behaviors above will no longer occur.
Consent timing: We only use device identifiers for login registration, push binding and core services after you read and agree to the Terms of Service and this Privacy Policy; you may tap Disagree and exit the App.
10.6 Device Identifier Disclosure
To establish push notification channels, recognise the same device across multiple accounts (with sign-out unbinding), deduplicate push messages, enable one-tap login and security controls, the App may read and use the following device identifiers (see Section 1.4):
| Identifier | Source | Purpose | Storage | Revocation |
|---|---|---|---|---|
| Android ID | The system API Settings.Secure.ANDROID_ID (accessed through the expo-application module) | Used as one on-device identifier; concatenated with account ID and reported as push token for channel binding and delivery; unbinds push on account switch or sign-out; server deduplication. | Used in memory and requests, reported to servers in China; not used for ad profiling. | Uninstall the App, disable push, or factory reset (resets Android ID). |
| MAC address / OAID and similar identifiers | Automatically read on device by Alibaba Cloud Mobile Push, OEM push SDKs and number authentication SDK | Push channel registration and delivery, one-tap login environment checks, account and push security | Core features only; stored on servers in China | Disable notifications, decline related login methods, or uninstall the App |
We do not actively collect IMEI, MEID, IMSI, SIM serial number or similar sensitive identifiers for advertising or unrelated purposes. On iOS we use a random UUID stored in Keychain, not linked to hardware identifiers.
10.7 Policy Updates and Applicable Versions
If we add new third-party SDKs, advertising services, or analytics tools to the App in the future, we will promptly update the relevant information in this privacy policy and seek your consent again during version updates.
This section takes effect from the Memene App May 2026 version.