用户隐私政策-googleplay-英文

GemNearby Privacy Policy

Effective Date: April 22, 2025

Applicable Version: Google Play Version (Data Stored in Singapore)

GemNearby is operated by Shenzhen Zhangxun Technology Co., Ltd. (hereinafter referred to as “we” or “us”), and we are committed to protecting the privacy of your personal data. **We securely store your personal information on encrypted servers in Singapore**, in compliance with the Singapore Personal Data Protection Act (PDPA) and the Anti-Money Laundering and Counter-Terrorism Financing Act (AMLA). This Privacy Policy explains how we collect, use, store, share, and protect your personal information when you use our services through the GemNearby App (hereinafter referred to as the “App”). Please read this policy carefully and consent to it before using our services. If you have any questions, please contact us via “My” > “Online Customer Service” within the App.

---

1. Scope of Application

This policy applies to the GemNearby App (Google Play version), including features such as nearby recommendations, messaging, identity verification, notifications, and translation. **All user data is stored on encrypted servers in Singapore**, and some features may involve cross-border data transfers, as detailed in “Section 4 (1) Data Storage Location.” If you use GemNearby through other platforms (e.g., iOS App Store), certain terms may vary due to platform differences.

---

2. How We Collect and Use Personal Information

2.1 Personal Information We Collect

To provide GemNearby services, we may collect the following personal information. You may refuse to provide non-essential information, but this may prevent you from using certain features (e.g., nearby recommendations, verification, translation).

1. Registration and Login

- Data Types: Email address, Apple ID/Google account identifier, name, profile picture

- Purpose: To create an account, verify identity, provide login services, and populate your profile (name, profile picture) to enhance user experience

- Collection Methods:

- You manually enter your email address for registration/login

- Through Apple Sign-In (iOS), we collect Apple ID identifier, name, and profile picture (user-optional sharing)

- Through Google Sign-In (Android), we collect Google account identifier, name, and profile picture (via profile/email scope)

- Impact of Refusal: Refusing to provide an email or sign-in option will prevent registration or login; refusing to provide a name or profile picture will not affect login but may prevent automatic profile population

- Data Processing: Data is stored on encrypted servers in Singapore (AES-256 encryption) and shared with Apple/Google to support sign-in, subject to their privacy policies (Apple: https://www.apple.com/legal/privacy/en-ww/; Google: https://policies.google.com/privacy)

2. User Profile

- Data Types: Profile picture, nickname, preferred categories (e.g., gemstone types), nationality/region

- Purpose: To display your profile (profile picture, nickname, preferred categories, nationality/region) to enhance transaction credibility

- Collection Methods: You manually set or upload your profile picture, nickname, preferred categories, and select your nationality/region; the profile picture may be auto-populated via Google/Apple Sign-In (editable by you)

- Impact of Refusal: Refusing to provide this information will result in an incomplete profile but will not affect other functions

3. Messaging

- Data Types: Text chat records, images, voice messages, video messages (may include faces)

- Purpose: To support text, voice, and video messaging

- Collection Methods: You input or upload content, transmitted in real-time via Tencent Cloud IM SDK

- Translation Feature: You may choose to translate chat records (text messages). Upon clicking the translate button, selected text is translated into the specified language via the Volcengine Translation API (provided by ByteDance)

- Impact of Refusal: Refusing to provide content will prevent sending specific content or using the translation feature, but other messaging methods remain available

- Data Processing: Chat data (text, images, voice, video) is stored only on your device locally, with zero server storage. Translated text messages are transmitted to Volcengine Translation via SSL/TLS encryption and are not stored after translation. Please review the Volcengine Translation Privacy Policy (https://www.volcengine.com/docs/4/privacy)

4. LocationWhen you use the “Nearby” feature (recommending nearby users or pushing nearby procurement demands), we collect your location information via the Amap Location SDK with your explicit consent.

- Permission Request: Requested upon first accessing the homepage or using the “Nearby” feature (precise or approximate location)

- Data Types: Precise location (latitude/longitude) or approximate location (city)

- Purpose: To recommend nearby users or push nearby procurement demands based on your location, enhancing transaction efficiency

- Permission Persistence: Once granted, location permission remains effective for subsequent App use unless manually revoked

- Collection Scope: Location is collected only when the App is in the foreground (homepage or “Nearby” feature), not in the background

- User Control: You may choose “Allow” or “Deny” during the initial request or manage permissions via device settings (iOS: Settings > Privacy > Location Services > GemNearby; Android: Settings > Location > GemNearby)

- Impact of Refusal: Refusing location permission will prevent use of the “Nearby” feature or receiving procurement demand recommendations but will not affect other functions (e.g., messaging, verification)

- Data Processing: Location information is stored on encrypted servers in Singapore (AES-256 encryption) only during the use of the “Nearby” feature and is deleted immediately upon disabling the feature or account deletion (see “Section 4 (2) Data Retention Period”). Please review the Amap Location SDK Privacy Policy (https://lbs.amap.com/pages/privacy/)

If you refuse to provide location information or permissions, you will not be able to use the “Nearby” feature but can still use other services.

5. Identity VerificationYou may apply for GemNearby verification (identity or business verification) to enhance account credibility. Verification is optional, and refusing verification does not affect basic functions (e.g., messaging, content browsing). We collect the following personal information through manual uploads, reviewed internally by GemNearby:

- Identity Verification: With your explicit consent, you must upload an ID card or passport information page (containing name, date of birth, and possibly ID/passport number) to verify identity. ID/passport images are stored on encrypted servers in Singapore and retained for 5 years to comply with Singapore’s AMLA requirements. We do not extract or store ID/passport numbers.

- Industry Verification: With your explicit consent, you must upload gemstone industry work proof (at least 2-3 items) to verify industry identity, including:

- Business card

- Selfie holding ID card/passport (including face)

- Jewelry exhibition pass

- Photo at a gemstone inspection counter (including equipment, may include face)

- Selfie in front of a jewelry counter (including face)

- Photo with company logo (may include face)

- Permission Requests:

- Camera Permission: Requested when first using the camera to take verification photos, used for capturing selfies or proof materials

- Storage Permission: Requested when first uploading verification materials from the gallery, used to access device files

- User Control: You may grant/deny camera permission (uploading from gallery does not require camera permission) or storage permission (denying prevents file uploads)

- Impact of Refusal: Denying camera permission allows uploading from the gallery; denying storage permission prevents uploading verification materials but does not affect other functions

- Verification Review: All materials (including ID/passport images and other photos) are manually reviewed internally by GemNearby and not shared with third parties. Photos are used solely to verify identity or industry background, with no facial feature extraction. Except for ID/passport images, other photos are deleted immediately after review. Industry proof files (encrypted) may be provided to the company you apply to verify against their employee database. If verification fails, you may need to provide additional materials or may be unable to complete verification.

- Data Processing: Name, date of birth, industry proof files, and ID/passport images are stored on encrypted servers in Singapore (AES-256 encryption). Name, date of birth, and industry proof are retained for the verification validity period (default 1 year) or until account deletion, deleted immediately upon deletion unless required by AMLA to retain for 5 years. ID/passport images are retained for 5 years per AMLA, deleted after 5 years or account deletion (whichever is later).

If you refuse to provide the above information or permissions, you will not receive a verification badge but can still use other functions.

6. Voice and Video MessagingYou may use GemNearby’s voice or video messaging features to communicate with friends or business partners in real-time. With your explicit consent, we collect the following information via Tencent Cloud IM SDK to support this feature:

- Permission Requests:

- Microphone Permission: Requested when first initiating voice or video messaging, used to collect audio data for real-time communication

- Camera Permission: Requested when first initiating video messaging, used to collect video streams for video communication

- Data Types: Audio data (voice messaging, video messaging), video stream (video messaging, may include faces)

- Purpose: To encrypt and transmit audio and video streams via Tencent Cloud IM SDK for real-time voice/video communication

- User Control: You may grant/deny permissions during the initial request or manage them via device settings (iOS: Settings > Privacy > Microphone/Camera > GemNearby; Android: Settings > Apps > GemNearby > Permissions)

- Impact of Refusal: Denying microphone permission prevents voice or video messaging; denying camera permission prevents video messaging, but text messaging remains available

- Data Processing: Voice and video messaging data is transmitted in real-time only during the session, not stored on our servers, and is removed from the device immediately after the session ends, with no backups. Data transmission uses SSL/TLS 1.2 or higher encryption, processed solely via Tencent Cloud IM SDK, with no other third-party services involved. Please review the Tencent Cloud IM SDK Privacy Policy (https://cloud.tencent.com/document/product/269/80923)

If you refuse to provide the above permissions, you will not be able to use voice or video messaging but can still use text messaging or other services.

7. NotificationsWe send friend messages or service updates (e.g., new messages, verification status) via device system notifications. To support push notifications, we use the following services:

- Firebase Cloud Messaging (FCM) (Google Play version): Sends push notifications to Android devices

- Apple Push Notification Service (iOS version): Sends push notifications to iOS devices

- Tencent Cloud IM SDK Push Services: Integrates the following sub-SDKs to support notifications on different device brands:

- OPPO Push SDK

- Huawei Push SDK

- vivo Push SDK

- Xiaomi Push SDK

- Meizu Push SDK

- Honor Push SDK

- Permission Request: Requested upon first installing the App or triggering the notification feature

- Data Types: Device token, device model, operating system, device identifiers (e.g., IMEI, Android ID, OAID, MAC address), notification content, network information (e.g., IP address)

- Purpose: To send new message reminders, verification status updates, or other service notifications

- Auto-Start Behavior: Some push SDKs (OPPO, Huawei, vivo, Xiaomi, Meizu, Honor, FCM) may auto-start to support notifications, potentially increasing device power or data usage; optimization is recommended via system settings

- User Control: You may grant/deny notification permission or disable it via device settings (iOS: Settings > Notifications > GemNearby; Android: Settings > Apps > GemNearby > Notifications). You may also restrict auto-start or data usage via system settings (Android: Settings > Apps > GemNearby > Auto-Start/Data Usage)

- Impact of Refusal: Denying notification permission prevents receiving push notifications, but you can view messages in the App’s “Messages” section

- Data Processing: Notification-related data is stored on encrypted servers in Singapore (AES-256 encryption) and deleted immediately upon account deletion (see “Section 4 (2) Data Retention Period”). Please review the privacy policies of each push SDK (see Appendix)

We may send service notifications via your provided contact information (e.g., email), and you may unsubscribe following the instructions in the email.

8. Device PermissionsTo provide GemNearby services, we may request the following device permissions. All permissions require your explicit consent, and you may manage them at any time via device system settings. Refusing permissions may affect certain functions but not core functions (e.g., text messaging, content browsing). We do not request contact permissions and will not access your contacts. Specific permissions include:

- Location Permission:

- Purpose: To collect your location information (precise or approximate) via Amap Location SDK for the “Nearby” feature (recommending nearby users, pushing procurement demands)

- Request Timing: Upon first accessing the homepage or using the “Nearby” feature

- Data Types: Precise location (latitude/longitude) or approximate location (city)

- Permission Persistence: Once granted, location permission remains effective for subsequent App use unless manually revoked

- Collection Scope: Location is collected only when the App is in the foreground (homepage or “Nearby” feature), not in the background

- Impact of Refusal: Refusing location permission prevents use of the “Nearby” feature or receiving procurement demand recommendations but does not affect other functions

- Storage Permission:

- Purpose: To read/write device storage for saving text chat records and images (local storage) or accessing files for uploading verification materials

- Request Timing: Upon first saving chat records or uploading verification materials

- Data Types: Chat records, images, verification files

- User Control: You may grant/deny or clear local data by uninstalling the App

- Impact of Refusal: Prevents saving chat records or uploading verification materials but does not affect other functions

- Camera Permission:

- Purpose: To take verification photos (e.g., selfies) or conduct video messaging

- Request Timing: Upon first using the camera to take verification photos or initiate video messaging

- Data Types: Photos, video streams (may include faces)

- User Control: You may grant/deny or upload verification materials from the gallery (no camera permission required)

- Impact of Refusal: Prevents taking verification photos or video messaging, but you can upload from the gallery or use text/voice messaging

- Microphone Permission:

- Purpose: To support voice and video messaging by collecting audio data for real-time communication

- Request Timing: Upon first initiating voice or video messaging

- Data Types: Audio data

- User Control: You may grant/deny or disable via device settings (iOS: Settings > Privacy > Microphone > GemNearby; Android: Settings > Apps > GemNearby > Permissions)

- Impact of Refusal: Prevents voice or video messaging but allows text messaging

- Notification Permission:

- Purpose: To send push notifications (e.g., new messages, verification status) via FCM, Apple Push Notification, and Tencent Cloud IM sub-SDKs

- Request Timing: Upon first installing the App or triggering the notification feature

- Data Types: Device token, device model, operating system, device identifiers

- User Control: You may grant/deny or disable via device settings (iOS: Settings > Notifications > GemNearby; Android: Settings > Apps > GemNearby > Notifications)

- Impact of Refusal: Prevents receiving push notifications, but you can view messages in the App

- Network Permission:

- Purpose: To support messaging (Tencent Cloud IM SDK, Volcengine Translation), login (Apple/Google Sign-In), notifications (FCM, etc.), and other network communications

- Request Timing: Automatically requested when the App runs

- Data Types: IP address, login identifiers, chat data

- User Control: You may restrict by disabling network access (e.g., turning off Wi-Fi/data)

- Impact of Refusal: Prevents all network functions (e.g., messaging, login, translation)

Data Protection: Data collected via permissions is protected under this policy, stored on encrypted servers in Singapore (AES-256 encryption) or locally on your device, and deleted upon account deletion (see “Section 4 (2) Data Retention Period”). For permission-related questions, please contact us via “My” > “Online Customer Service.”

2.2 How We Use Personal Information

We use your personal information solely for the following purposes:

- To provide and optimize GemNearby services (e.g., nearby recommendations, messaging, verification, notifications, translation)

- To verify identity and industry background, preventing fraud

- To send service notifications (e.g., new messages, verification status)

- To comply with legal requirements (e.g., AMLA anti-money laundering requirements)

We will not use your personal information for other purposes unless we obtain your explicit consent or as required by law.

---

3. How We Process, Share, Transfer, and Disclose Personal Information

3.1 Processing

We may delegate certain data processing to the following third-party service providers, who are bound by data processing agreements to handle your information securely in accordance with this policy and applicable laws:

- Amap Location SDK (AutoNavi Software Co., Ltd.): Collects location information (precise/approximate) for the “Nearby” feature. Privacy Policy: https://lbs.amap.com/pages/privacy/

- Apple Sign-In (Apple Inc.): Collects Apple ID identifier, name, and profile picture for iOS device login. Privacy Policy: https://www.apple.com/legal/privacy/en-ww/

- Google Sign-In (Google LLC): Collects Google account identifier, name, and profile picture for Android device login. Privacy Policy: https://policies.google.com/privacy

- Tencent Cloud IM SDK (Tencent Computer Systems Co., Ltd.): Provides text, voice, video messaging, and push notifications, including the following sub-SDKs:

- OPPO Push SDK (Guangdong Huantai Technology Co., Ltd.)

- Huawei Push SDK (Huawei Software Technology Co., Ltd.)

- vivo Push SDK (Vivo Mobile Communication Co., Ltd.)

- Xiaomi Push SDK (Xiaomi Mobile Software Co., Ltd.)

- Meizu Push SDK (Zhuhai Meizu Communication Equipment Co., Ltd.)

- Honor Push SDK (Honor Device Co., Ltd.)Privacy Policy: https://cloud.tencent.com/document/product/269/80923

- Volcengine Translation (Beijing ByteDance Technology Co., Ltd.): Processes user-selected chat records (text messages) for translation. Privacy Policy: https://www.volcengine.com/docs/4/privacy

- Push Notification Services:

- Firebase Cloud Messaging (FCM) (Google Play version): Collects device token, device model, and operating system for Android push notifications

- Apple Push Notification Service (iOS version): Collects device token, phone model, and system version for iOS push notifications

These services may involve cross-border data transfers (see “Section 4 (1) Data Storage Location”). Auto-start behavior may increase device power or data usage, which you can restrict via system settings.

3.2 Sharing

We share your personal information only in the following cases:

- Verification Information Sharing: Industry proof files (encrypted) may be provided to the company you apply to verify against their employee database

- Third-Party Service Sharing:

- Login identifiers (Apple ID/Google account), name, profile picture, and notification data (device token, identifiers) are shared with Apple, Google, FCM, and Tencent Cloud IM sub-SDKs to support login and notifications

- User-selected chat records (text messages) are shared with Volcengine Translation to support the translation feature

We do not share chat data (images, voice, video), verification photos (including ID/passport images), location information, or profile information (including profile picture, nickname, nationality/region) unless we obtain your explicit consent or as required by law.

3.3 Transfer

We will not transfer your personal information to any third party unless we obtain your explicit consent or as required by law (e.g., company mergers, acquisitions).

3.4 Public Disclosure

We will not publicly disclose your personal information unless we obtain your explicit consent or as required by law (e.g., court orders).

---

4. How We Store Personal Information

4.1 Data Storage Location

Your personal information is stored on encrypted servers in Singapore (AES-256 encryption), operated and managed by Shenzhen Zhangxun Technology Co., Ltd. To provide certain features (e.g., nearby recommendations, messaging, translation, sign-in, push notifications), some data may be transmitted to other regions via third-party services, including:

- Mainland China: Amap Location SDK (location information), Tencent Cloud IM SDK (messaging and notifications), Volcengine Translation (chat record translation)

- United States: Firebase Cloud Messaging (push notifications), Apple Sign-In, Google Sign-In (login data)

All cross-border data transfers comply with the Singapore Personal Data Protection Act (PDPA) and relevant data protection regulations, using SSL/TLS 1.2 or higher encryption to ensure data security.

4.2 Data Retention Period

We retain your personal information only for the period necessary to fulfill the purposes outlined in this policy or as required by law, as follows:

- Chat Records and Images: We do not store any text chat records, images, voice, or video chat data. All chat data (including text, images, audio, video) is stored only on your device locally, with zero server storage. Translated chat records (text messages) are processed via Volcengine Translation and not stored after translation. You may delete chat records at any time (see “Section 5 (3) Deleting Your Information”), and they are removed from the device immediately, unrecoverable, with no backups.

- Verification Information:

- ID/Passport Images (containing name, date of birth, possibly ID/passport number): Stored on encrypted servers in Singapore (AES-256 encryption), retained for 5 years per AMLA requirements, deleted after 5 years or account deletion (whichever is later). We do not extract or store ID/passport numbers.

- Name, Date of Birth, Industry Proof Files (e.g., business card, exhibition pass): Stored on encrypted servers in Singapore (AES-256 encryption), retained for the verification validity period (default 1 year) or until account deletion, deleted immediately upon deletion unless required by AMLA to retain for 5 years.

- Other Photos (e.g., selfies with ID, counter photos, possibly containing faces): Used only for internal manual review by GemNearby, deleted immediately after review, with no storage of facial data or feature extraction.

- Location Information: Stored on encrypted servers in Singapore only during the use of the “Nearby” feature, deleted immediately upon disabling the feature or account deletion.

- Login Identifiers and Notification Data (e.g., email address, Apple ID/Google account identifier, name, profile picture, device token, device identifiers like IMEI, Android ID): Retained until account deletion for account management and notification delivery, deleted immediately upon deletion.

- Profile Information (profile picture, nickname, preferred categories, nationality/region): Retained until account deletion, deleted immediately upon deletion.

Account Deletion: Upon account deletion, we immediately delete your personal information (e.g., location information, login identifiers, notification data, profile information), except where required by AMLA to retain (e.g., ID/passport images, name, date of birth, industry proof for 5 years). Chat data (text, images, voice, video) is stored only on your device locally and removed upon App uninstallation. Due to backup systems, some data may remain in encrypted backups for up to 30 days, used solely for system recovery and inaccessible, then automatically deleted.

Legal Compliance: We comply with PDPA and AMLA, retaining data only as necessary, deleting or anonymizing it once the purpose is fulfilled or legal requirements expire. For data retention questions, please contact us via “My” > “Online Customer Service,” and we will respond within 15 working days.

---

5. How You Can Manage Your Personal Information

5.1 Accessing Your Information

You may access your personal information at any time by logging into the GemNearby App:

- Profile: View your profile picture, nickname, preferred categories, and nationality/region in the “My” section

- Chat Records: View text, image, voice, and video records in the “Messages” section

- Verification Information: View verification status in “My” > “Verification”

To access other information (e.g., location data), please contact us via “My” > “Online Customer Service,” and we will respond within 15 working days.

5.2 Correcting Your Information

You may correct inaccurate personal information at any time:

- Profile: Update your profile picture, nickname, preferred categories, and nationality/region in “My” > “Edit”

- Verification Information: To correct name, date of birth, or industry proof, please contact us via “My” > “Online Customer Service”

We will process corrections within 15 working days after verifying your identity.

5.3 Deleting Your Information

You may delete certain personal information yourself, and deleted data is unrecoverable:

- Profile Information: Log into the GemNearby App, go to the “My” section, click your profile picture/name, enter the profile preview page, click “Edit,” and delete your profile picture, nickname, preferred categories, nationality/region, etc.

- Chat Records (text, images, voice, video):

- Delete All Chat Records: In the “Messages” section, select the chat contact to delete, click the delete operation to remove all chat records with that contact (including text, images, voice messages, video messages, etc.)

- Delete Partial Chat Records: Enter a conversation window with a contact, select single or multiple chat records (including text, images, voice messages, video messages), and click the delete operation to remove selected records

- Uninstall the App: Uninstalling the GemNearby App clears all locally stored chat records (text, images, voice, video)

Data Processing: We do not store any chat records (text, images, voice, video); all chat data is stored only on your device locally, with zero server storage. Translated chat records (text messages) are processed via Volcengine Translation and not stored. Upon deletion or App uninstallation, data is removed from the device immediately, unrecoverable, with no backups, giving you full control over your chat data.

To delete other personal information (e.g., verification information, location data), please contact us via “My” > “Online Customer Service,” and we will process your request within 15 working days after verifying your identity, except where required by law (e.g., ID/passport images retained for 5 years).

5.4 Withdrawing Consent

You may withdraw consent for the collection and use of personal information at any time:

- Permission Withdrawal: Disable permissions (e.g., location, camera, microphone) via device settings

- Notification Withdrawal: Disable notifications via device settings or unsubscribe from email notifications

- Feature Withdrawal: Stop using specific features (e.g., disable “Nearby” feature, skip translation)

Withdrawing consent may affect related functions but not other services. For assistance, please contact us via “My” > “Online Customer Service.”

5.5 Deleting Your Account

You may delete your GemNearby account via “My” > “Settings” > “Delete Account.” Upon deletion:

- Your personal information (e.g., location information, login identifiers, notification data, profile information) is deleted immediately, except where required by AMLA to retain (e.g., ID/passport images, name, date of birth, industry proof for 5 years)

- Chat data (text, images, voice, video), stored only on your device locally, is removed upon App uninstallation

- Backup data may remain for up to 30 days, used solely for system recovery, then deleted

After deletion, you will be unable to log in or use GemNearby services, and data is unrecoverable. For assistance, please contact us via “My” > “Online Customer Service,” and we will process within 15 working days.

---

6. How We Protect Personal Information

We take the following measures to protect your personal information:

- Technical Measures: Data storage and transmission use AES-256 encryption; chat and translation data use SSL/TLS 1.2 or higher encryption

- Administrative Measures: Restrict employee access, with only authorized personnel handling data, and conduct regular security training

- Contractual Measures: Sign data processing agreements with third-party service providers to ensure data security

In case of a data breach, we will notify you immediately and report to the Singapore Personal Data Protection Commission (PDPC), taking remedial actions. If you identify data security issues, please contact us via “My” > “Online Customer Service.”

---

7. Protection of Minors

GemNearby services are not intended for minors under 18. If you are a minor, please use the service with parental consent or have a guardian operate on your behalf. If we discover that minor data was collected without parental consent, we will delete it immediately. If you are a guardian with questions, please contact us via “My” > “Online Customer Service.”

---

8. How This Policy Is Updated

We may update this Privacy Policy based on GemNearby service adjustments or legal requirements to ensure compliance with the latest data protection standards. Updated policies will be notified to you before taking effect via:

- Login Prompt: When you log into the GemNearby App, a pop-up or login interface will prompt you to review and agree to the new policy

- Website Announcement: Updates will be posted on the GemNearby official website (www.gemnearby.com) for your review

After the new policy takes effect, you must agree to it to continue using GemNearby services. If you disagree, you will be unable to log in or use the App and may choose to delete your account via “My” > “Settings” > “Delete Account,” after which we will delete your personal information immediately (see “Section 5 (5) Deleting Your Account”).

We update the policy periodically based on service changes or legal requirements (e.g., PDPA), with no fixed schedule. We recommend reviewing this policy regularly for the latest information. For questions, please contact us via “My” > “Online Customer Service,” and we will respond within 15 working days.

---

9. How to Contact Us

If you have questions about this policy or personal information processing, please contact us via:

- Online Customer Service: “My” > “Online Customer Service” (within the App)

- Email: gemnearbyservice@163.com

We will respond to your request within 15 working days. If you are dissatisfied with our handling, you may file a complaint with the Singapore Personal Data Protection Commission (PDPC).

---

Appendix: Third-Party Service Privacy Policies

- Amap Location SDK: https://lbs.amap.com/pages/privacy/

- Apple Sign-In: https://www.apple.com/legal/privacy/en-ww/

- Google Sign-In: https://policies.google.com/privacy

- Tencent Cloud IM SDK and Sub-SDKs: https://cloud.tencent.com/document/product/269/80923

- Volcengine Translation: https://www.volcengine.com/docs/4/privacy

- Firebase Cloud Messaging (FCM): https://policies.google.com/privacy

- Apple Push Notification Service: https://www.apple.com/legal/privacy/en-ww/