1. Information We Process
To provide clipping services, we may process local videos you select, exported
files, clipping results, clip-selection states, export history, device runtime
status, error information, account information, and feedback content.
The current Mainland China Android version supports phone-number and WeChat
sign-in; the HarmonyOS version also supports Huawei ID sign-in. QQ sign-in is not offered and no QQ SDK is integrated or initialized.
Account information may include your phone number,
user ID, nickname, avatar, third-party account identifier, and sign-in status.
The versions above do not integrate or invoke Google Sign-In, Apple
Sign-In, or Firebase Authentication. Other platform or regional versions are
governed by the functions actually shown in that version and the corresponding
statements in this policy.
Match records: after you sign in, the match title, match date, venue, singles or
doubles, opponent names, and per-game scores you enter in “Register Match” or “My
Matches” are stored on our servers so that you can view and synchronize them on
other devices where you are signed in. Opponent names may relate to other people,
so we recommend using nicknames. Matches cannot be created without signing in;
videos, clipping drafts, and the association between videos and matches are
stored only on this device and are not uploaded.
Recording date: when you import a video, we read the video's recording time only
on this device (or use the import time if it cannot be read) to fill in the
default match date. The recording time itself is not uploaded; it is uploaded only
in the form of the match date you save.
2. Video and Clipping Processing
Yuqiu Shike processes imported videos locally by default to detect valid rallies,
preview clips, and export results. Original videos are not automatically uploaded
to our servers during normal clipping analysis.
Match-video sharing is on by default. You can turn it off at any time in
Profile → Privacy & Help; once it is off, we submit no new training material.
While it is on, when you export a video we submit the current match video,
clipping results, and related technical features as training material, used only
for algorithm evaluation, model training, and quality improvement, and never for
advertising or public display. We de-identify where we can, for example by
obscuring file names, account identifiers, and unrelated metadata, and we
minimize the use of information unrelated to clipping. If a video shows other
people or minors, make sure you have their necessary consent; if you do not want
it submitted, turn the switch off first.
3. Accounts, Feedback, and Service Improvement
Sign-in displays account status, synchronizes basic profile data, and associates
feedback. Feedback includes ratings and comments and, when you are signed in, may
include your account ID, phone number, or email to help diagnose account issues
and improve the experience.
The current Android version provides no advertising push or personalized
recommendations based on personal information. “Recommended clips” are only local
clipping results generated from the video currently imported on your device and do
not create a profile across videos or accounts.
Message notifications are optional. Only after you consent to this policy,
actively enable “Message Notifications,” the system permits notifications, and the
channel of your device has the required configuration and service permission do we
initialize the corresponding vendor push SDK and register the local push address.
Only one matching channel is enabled per device. Declining or turning off
notifications does not affect clipping, sign-in, or in-app messages. You can turn
it off in “Message Notifications” in the message center or in system notification
settings. This choice is stored only on this device and is not synchronized to
other devices. This release establishes channel registration capability; business
message sending is not yet enabled, and a successful registration does not mean
that a message has been delivered.
4. Third-Party Services
One-tap local-number sign-in relies on carrier authentication and backend
verification. Authentication SDKs are called only after you actively check your
agreement to the User Agreement and Privacy Policy and choose local-number
sign-in. Without consent, we do not send an SMS verification code or initiate
local-number authentication.
WeChat OpenSDK is called only after you consent to the User Agreement and Privacy
Policy and actively tap WeChat. The client receives only a one-time authorization
code, which the server exchanges with WeChat; the WeChat AppSecret is never stored
in the client.
-
SDK: WeChat OpenSDK Android, package
com.tencent.mm.opensdk, developed by Shenzhen Tencent Computer
Systems Co., Ltd. It opens WeChat for account authorization and may process the
WeChat installation state and the public nickname and avatar you authorize. Our
server also processes the one-time authorization code, openid, and unionid when
WeChat returns it. SDK personal-information rules:
WeChat OpenSDK rules.
-
SDK: WeChat OpenSDK iOS, package
WechatOpenSDK,
version 2.0.7, developed by Shenzhen Tencent Computer Systems Co., Ltd. On iOS it
opens WeChat for account authorization and returns to the app through a universal
link. It may process whether the WeChat client is installed, the app identifier,
the universal link, and the public WeChat nickname and avatar you authorize; the
server also processes a one-time authorization code, the openid, and the unionid
when WeChat returns it. It is called only after you consent to this policy and
actively tap WeChat sign-in; the client stores no WeChat AppSecret. Personal
information rules:
WeChat OpenSDK personal information rules.
-
SDK: WeChat OpenSDK (HarmonyOS), package
@tencent/wechat_open_sdk, version 1.0.21, developed by
Shenzhen Tencent Computer Systems Company Limited. It opens WeChat
for account authorization or membership order payment and returns to this app.
It processes WeChat installation status, OS/API and SDK versions, app identity,
authorization requests and one-time codes, or merchant ID, prepayment ID,
nonce, timestamp, signature and callback results. Our server processes the
nickname/avatar you authorize, openid and unionid when provided.
It runs only after policy consent and your explicit WeChat login/payment action.
AppSecret and merchant private keys are not stored in the app.
Raw SDK logs and optional payment diagnostics are disabled;
app diagnostics are sanitized. See the
SDK personal information rules.
-
SDK: Huawei Account Service (HarmonyOS Account Kit), package
@kit.AccountKit, developed by Huawei Device Co., Ltd. It lets you
sign in with your Huawei ID on HarmonyOS devices. The client receives only a
one-time authorization code; our server exchanges it with Huawei for your
OpenID and, when Huawei returns it, your UnionID. With your authorization, we
obtain the phone number bound to your Huawei ID to link your existing account.
The authorization page also requests your Huawei ID nickname and avatar; the
client does not read your phone number, nickname or avatar. It runs only after
you consent to this policy and
actively tap Huawei ID sign-in; the app stores no Huawei client secret. See the
Huawei ID privacy statement.
-
SDK: 号码认证-android, package
com.mobile.auth, developed by Alibaba
Cloud Computing (Beijing) Co., Ltd. It provides one-tap local-number sign-in,
terminal adaptation, network checks, and security verification and may process
IP address, network status, device manufacturer and model, operating-system
information, SIM state, and carrier type. SDK privacy policy:
Aliyun legal agreement.
-
SDK: 号码认证-HarmonyOS, package
numberauth_standard, developed by Alibaba Cloud Computing (Beijing)
Co., Ltd. On HarmonyOS devices it provides one-tap local-number sign-in, terminal
adaptation, network checks, and security verification; its bundled carrier
components authenticate with the carrier of the current SIM, whose service
agreement is shown on the authorization page. It may process IP address, network
status, device manufacturer and model, operating-system information, SIM state, and
carrier type, and requires the INTERNET, GET_NETWORK_INFO, and SET_NETWORK_INFO
permissions solely for cellular number authentication. It is called only after you
accept this policy and choose local-number sign-in; the client receives a one-time
token that the server verifies and does not store it. SDK privacy policy:
Aliyun legal agreement.
-
SDK: China Mobile Authentication SDK, package
com.cmic.sso.sdk, developed by China Mobile Internet Co., Ltd. It
authenticates the local number in China Mobile networks and may process the
local phone number, IP address, device and operating-system information, SIM
state, network status, carrier information, and host-app package and signature.
-
SDK: 联通认证SDK, package
com.unicom.online.account, developed by China Unicom Online
Information Technology Co., Ltd. It authenticates the local number in China
Unicom networks and may process the local phone number, cellular-network IP
address, device type or model, operating-system information, SIM state, network
and Wi-Fi status, carrier information, and host-app package and signature. SDK
privacy policy:
China Unicom protocol.
-
SDK: 荣耀更新SDK, package
com.honor.updater.upsdk, developed by Shenzhen Honor Software
Technologies Co., Ltd. On HONOR devices it checks whether an App Market update
exists and lets HONOR App Market present and handle that update. This SDK does
not collect personal data, so no SDK privacy policy applies.
-
SDK: OPPO PUSH SDK, packages
com.heytap.mcssdk and com.heytap.msp.push, version
3.7.1, developed by Guangdong HuanTai Technology Co., Ltd. On devices that
support OPPO Push it verifies app identity, obtains the push address, and
provides the message notification channel. It may process the in-app push
identifier RegisterId, the client registration parameters AppKey/AppSecret, the
MCS application package name, this app's package name, the app version, and the
push SDK version. It is called after you consent to this policy, actively enable
message notifications, the system permits notifications, and the channel
configuration is valid. After registration succeeds it requests the
notification-bar permission through this SDK as OPPO requires; you decide in the
system dialog whether to allow it. SDK privacy policy:
OPPO PUSH SDK privacy policy.
-
SDK: vivo Push SDK, package
com.vivo.push, version
4.1.5.0, developed by Vivo Mobile Communication Co., Ltd. It provides the push
message channel on vivo devices and measures SDK API call success rates. It may
process basic app information (AppID, AppKey, package name, app version, SDK
version), the in-app push identifier regid, device type, system type, and system
version. It is called after you consent to this policy, actively enable message
notifications, the system permits notifications, and the channel configuration
is valid. SDK privacy policy:
vivo push privacy policy.
-
SDK: HONOR Push SDK, package
com.hihonor.push.sdk, version 10.0.13.305, developed by Shenzhen
Honor Software Technologies Co., Ltd. It provides the message notification
channel on HONOR devices. It may process device identifiers (AAID, PushToken)
and app information (AppID, app package name). It is called after you consent to
this policy, actively enable message notifications, the system permits
notifications, and the channel configuration is valid. SDK privacy policy:
HONOR SDK data security.
-
SDK: Xiaomi Push SDK, package
com.xiaomi.mipush.sdk, version 7.12.4-C, developed by Beijing Xiaomi
Mobile Software Co., Ltd. It provides the message notification channel on Xiaomi
and Redmi devices. It may process app information (package name, version and
running state), device information (manufacturer, model, region, carrier name,
etc.), device memory, OS version, SDK version, notification settings, current
network type, WLAN state, the in-app push identifier RegId, and the creation,
delivery and click times and content of push messages; the current network type
and carrier name are read on the device only. It is called after you consent to
this policy, actively enable message notifications, the system permits
notifications, and the channel configuration is valid; the SDK file log and log
upload components are turned off. SDK privacy policy:
Xiaomi Push privacy policy.
The four Android push SDKs above are not initialized on iOS/HarmonyOS, and we do
not use Firebase or third-party aggregated push.
The local open-source components Flutter, MNN on-device inference runtime,
image_picker, video_player, and SharedPreferences are used only for the interface,
local video selection and playback, on-device algorithms, and local preferences.
In the current configuration they do not independently collect, upload, or share
personal information, and these components themselves include no advertising,
push, or analytics SDK.
5. Retention and Deletion
Export history and local files are mainly stored on your device. Server-side
account, feedback, and authorization data are retained only as needed for the
service. We process local deletion, sign-out, video-sharing withdrawal, and
deletion requests according to the relevant feature scope.
Delete your account in App “Me → Account & Security → Delete Account.” After
successful deletion, server-side account data and feedback identity markers are
processed under this policy. Videos already exported locally are not
automatically deleted. If in-app deletion is unavailable, contact us through “Me
→ Feedback.”
You can delete a match in “My Matches.” The deletion is synchronized to other
devices where you are signed in, and the server keeps a deletion marker for 30
days before clearing it. Video drafts on this device are not deleted as a result.
When you delete your account, all match records on the server are deleted.
6. Data Security
We use reasonable technical and administrative measures, including minimization,
access control, transport security, and reduced error logging. No internet
service can guarantee absolute security; avoid submitting sensitive content
unrelated to clipping.
7. Your Rights
In the App you can view this policy and the User Agreement, disable match-video
sharing, submit feedback, or request access, correction, deletion, authorization
withdrawal, removal of submitted training material, or account deletion. The
account-deletion entry is “Me → Account & Security → Delete Account.” Use “Me
→ Feedback” for other requests.
8. Children and Minors
Yuqiu Shike is intended for users able to use mobile applications independently.
Minors should use the App under guardian guidance and should not submit unrelated
minor identity information in feedback.
9. Policy Updates
We may update this policy as features, services, or legal requirements change.
Material changes will be communicated reasonably in the App or on the website.
10. Contact Us
For questions, suggestions, or complaints about this policy or personal
information processing, contact us through Feedback on the Me page in the App.
