ZaiYu Terms of Service
1. Parties and acceptance
These Terms are between you and Dongguan Yimu Technology Co., Ltd.. By checking acceptance, requesting a verification code, registering or continuing to use ZaiYu, you acknowledge these Terms and the Privacy Policy.
2. Age and account
- You must be at least 21 and have legal capacity to use the service.
- Your mobile number is the primary login credential. Use a number you control and protect verification codes and devices.
- Do not sell, rent, lend or transfer an account or impersonate another person.
3. Profile and verification
- Provide profile information honestly and do not use false identity or deception.
- Certain functions, especially hosting events, may require identity verification. Divorce verification is optional. Verification does not guarantee character, finances, current marital status or offline safety.
- A valid identity document should normally be bound to only one verified account at a time; it may be used again after a lawful account deletion releases the verification record.
4. Discover, matching and chat
Recommendations are information ranking only and are not a dating, credit or safety endorsement. You remain responsible for assessing interactions and offline meetings.
5. User content
You are responsible for text, images, audio and event content you submit and must have the necessary rights. You grant us the limited rights necessary to store, display, transcode, moderate, transmit and share such content as part of the service.
6. Events and offline safety
- Events may be hosted by members or approved merchants. Hosts must accurately describe time, venue, fees, capacity and rules.
- Attendees must assess risks and comply with law, venue rules and safety guidance.
- We may cancel, delist or restrict events for safety, complaints, violations, force majeure or legal requirements.
7. Event fees, payment and refunds
Fee type, amount, currency, VIP discount and refund rules shown before payment apply. Apple App Store Mainland-China storefront uses WeChat for event payment; other Apple storefronts use Stripe/Apple Pay; Google Play uses Stripe; China Android/Huawei use WeChat. Payment is complete only after server-side confirmation.
8. VIP
Benefits, price, term and auto-renewal are shown on the purchase page. iOS VIP uses Apple StoreKit/App Store; other builds use available methods. Active auto-renewal should be turned off before account deletion.
9. Prohibited conduct
- Illegal activity, fraud, money solicitation, gambling, pornography, violence, harassment, threats or hate.
- Impersonation, forged verification material or deceptive requests for off-platform transfers.
- Scraping, reverse engineering, attacks, bypassing security, verification-code/API abuse.
- Infringement of privacy, intellectual property, portrait or reputation rights.
- Illegal or manifestly dangerous events.
10. Moderation and account measures
We may take legally permitted measures including moderation, warnings, feature restrictions, delisting, suspension, blocking, preservation of necessary evidence and reporting to authorities.
11. Third-Party SDK & Services List
The table below lists services used for SMS, storage, moderation, maps, verification, payments and push. Actual activation depends on device, distribution channel, Apple App Store storefront for Apple builds, phone region where relevant (such as SMS), and your actions.
This list reflects the current App/Server integration and conditionally enabled capabilities. A service does not receive the listed data from that scenario unless the relevant function is triggered.
| SDK / Service | Provider | Purpose | Data potentially processed | Trigger | Cross-border |
|---|---|---|---|---|---|
| Tencent Cloud SMS | Tencent Cloud and affiliates | Send login verification codes to +86 mobile numbers | Mobile number, verification code, delivery result and necessary request data | When the user requests a verification code | Generally processed in Mainland China |
| AWS End User Messaging SMS | Amazon Web Services | Send login verification codes to non-Mainland-China numbers (currently mainly +852) | Mobile number, verification code, delivery status and necessary request data | When a non-+86 user requests a verification code | May be processed outside Mainland China; triggered only for the relevant login flow |
| Tencent Cloud COS | Tencent Cloud and affiliates | Store profile photos, chat images/audio, event images and feedback attachments | Uploaded images, audio, attachments and random object paths | When the user uploads or sends media | Primarily configured in Mainland China service regions |
| Tencent Cloud IMS | Tencent Cloud and affiliates | Moderate images for prohibited or inappropriate content | Images or temporary image URLs and moderation results | When a user uploads images intended for display | Generally processed in Mainland China |
| Tencent Cloud IAI Face Detection / Comparison | Tencent Cloud and affiliates | Human portrait detection and Hong Kong ID portrait-to-selfie comparison | Face images/features and detection/comparison results | When the relevant portrait check is enabled or the user performs Hong Kong identity verification | Generally processed in Mainland China; separate consent is requested for sensitive personal information |
| Tencent Cloud OCR / Identity Verification | Tencent Cloud and affiliates | Recognise Mainland China ID cards, Hong Kong ID cards and divorce documents / Decree Absolute | Document images, name, ID number, OCR result, risk indicators and request IDs | When the user initiates identity or divorce verification | Generally processed in Mainland China; separate consent is requested for sensitive personal information |
| Tencent Location Services | Tencent and affiliates | Nearby members/events, distance calculation, event venue search and navigation | Coordinates, accuracy, place queries, POI/address information and necessary device/network data | When location is authorised or a venue is searched/selected | Generally processed in Mainland China |
| Stripe | Stripe, Inc. and affiliates | Card payment for paid events on Google Play builds and Apple App Store builds whose storefront is outside Mainland China | Amount, currency, payment status and payment/fraud-prevention data. Full card numbers are handled by Stripe and are not stored by ZaiYu servers | When a Google Play user, or an Apple user whose App Store storefront is not CN/CHN, pays for a paid event | May be processed outside Mainland China; triggered only when the relevant payment method is used |
| WeChat OpenSDK / WeChat Pay | Tencent/WeChat Pay entities and affiliates | WeChat sharing and payment/contract flows for Apple Mainland-China storefront builds and China Android/Huawei builds | Necessary device/app identifiers, shared content, order number, amount, payment/contract status | When the user actively uses WeChat sharing or the installed build is routed to WeChat Pay | Generally processed in Mainland China |
| Apple StoreKit / App Store | Apple Inc. and affiliates | iOS VIP purchases, restore purchase and subscription verification, plus reading the App Store storefront when first available for the installation to route Apple-build event payments and push | Product ID, transaction/original transaction identifiers, purchase/subscription state, storefront country/region code locked for the installation and Apple verification data | When an iOS user buys/restores VIP or the Apple build needs to select its event-payment/push route | May be processed outside Mainland China depending on Apple service arrangements |
| Baidu Cloud Push SDK | Beijing Baidu Netcom Science Technology Co., Ltd. and affiliates | Deliver chat, match, event and system notifications on Apple Mainland-China storefront builds and China Android/Huawei builds | Baidu channel_id, hardware model, OS version, Android ID (Android) or IDFV (iOS), and minimum business navigation identifiers required in the notification payload | After Privacy Policy acceptance and OS notification permission when storefront/build routing selects Baidu | These routes use Baidu Cloud Push and do not use Expo/EAS push |
| Expo / EAS Push | 650 Industries, Inc. (Expo) | Push chat, match and event notifications to Apple builds whose App Store storefront is outside Mainland China and to all Google Play builds | Expo Push Token, notification title/summary and navigation identifiers | When the Apple storefront is not CN/CHN, or the user is on Google Play, and notifications are enabled | May be processed outside Mainland China; Apple Mainland-China storefront and China Android/Huawei routes do not use EAS Push |
| Google Firebase Cloud Messaging (FCM) | Google LLC | Underlying push delivery for Google Play Android builds (including possible indirect use by Expo/EAS) | Push token, notification payload and necessary app/device data | When notifications are enabled on a Google Play build | May be processed outside Mainland China; Google Play Variant 2 always uses the EAS/FCM route |
| Huawei Push Kit (reserved / currently disabled) | Huawei and affiliates | Reserved for a possible future Huawei Push route; current Huawei Variant 4 uses Baidu Cloud Push | If enabled later: Huawei Push Token, notification payload and necessary app/device data | Not triggered by the current four build variants; only after Huawei Push is explicitly enabled | Current Huawei Variant 4 uses Baidu Cloud Push; if enabled later, processing follows the actual Huawei Push Kit service region |
| Alibaba Cloud Mobile Push (reserved / currently disabled) | Alibaba Cloud and affiliates | Reserved for a possible future Android push route; the current four build variants do not use Alibaba Cloud Mobile Push | If enabled later: Aliyun Device ID/push identifier, notification payload and necessary app/device data | Not triggered by the current four build variants; only after Aliyun Push is explicitly enabled | The current four build variants do not use this route; if enabled later, processing follows the actual service region |
| Facebook Sharing (conditional) | Meta Platforms, Inc. and affiliates | Allow the user to share a public event link to Facebook | The public event link selected by the user and information independently processed by Facebook | Only when configured in the build and the user taps Facebook share | May be processed outside Mainland China |
12. Intellectual property
Software, brand, UI design and platform-created content are owned by the operator or lawful rights holders.
13. Service changes and liability
We reasonably maintain the service, but third parties, networks, devices, force majeure or regulation may cause interruptions. Liability is determined under applicable law.
14. Account deletion and termination
You may delete the account in-app. The old mobile number will cease to authenticate the deleted account; deletable data is deleted/anonymised and legally retained transaction/security/dispute records are restricted. Objective unfinished obligations may need to be resolved first.
15. Governing law and disputes
These Terms are governed by the laws of the People’s Republic of China. Disputes should first be negotiated; unresolved disputes may be submitted to a competent court at the operator’s domicile as permitted by law.
16. Contact and updates
Contact: info@wootrade.cn. Version 2026-09-06; effective 2026-09-06.