Rolling League / ITT Assist 隐私政策
Privacy policy

账号与服务条款 / Account and service terms

使用账号服务前，请阅读本页隐私说明，并只关联属于自己的球员资料。登录账号和球员身份分别管理；选择名字不构成最终身份核验。使用同一已验证账号的共享资料可在关联 App 中使用。退出登录和解绑不会删除云端数据。报名线下比赛前，仍须阅读并同意该赛事的资格、付款退款、比赛规则及免责条款；各赛事的条件以报名时展示的说明为准。球拍估算仅用于观察变化，不能代替实物校准或专业测量。资料更正、身份争议或服务问题可联系 hituptennis@gmail.com。

Before using account services, read the privacy information on this page and link only your own player profile. Sign-in accounts and player identities are managed separately; selecting a name does not resolve an identity dispute. Shared data may be used in associated apps signed into the same verified account. Signing out or unlinking does not delete cloud data. Before entering an in-person event, you must also review and accept that event’s eligibility, payment/refund rules, match rules and waiver as shown at registration. Racket estimates track changes and do not replace physical calibration or professional measurement. Contact hituptennis@gmail.com for corrections, identity disputes or service questions.

中文

1. 服务与账号

本应用由 Hitup Tennis 提供，为独立服务，并非 USTA 官方应用。我们处理 Google 或 Apple 登录提供的已验证账号标识、姓名和邮箱，用于登录、账号管理和支持。隐藏邮箱可能是 Apple 转发地址。姓名并非实名认证依据；不会仅因姓名或邮箱相同合并不同登录账号。我们不索取 ITT 或 USTA 网站密码。

登录账号与球员身份分别管理。你主动选择的 ITT 或 USTA 球员关联可在使用同一共享账号服务的 App 中沿用；球拍资料属于登录账号。退出登录或解绑球员不会自动删除云端资料、取消已报名赛事、转移比赛身份或退款。

2. 球员、报名和比赛资料

我们处理姓名、性别、完整出生日期、联系电话、邮箱、球员标识、队伍、评级、关联确认及报名资料，用于身份匹配、赛事资格、安排比赛和联系。搜索姓名或球员编号会发送到后台查询；查询词不进入下述功能使用统计。赛事记录包括组别、赛程、可约时间、比分、确认状态、名次、弃权或中途退赛原因。若主动选择健康原因，我们会保存该原因分类；请勿提交不必要的详细医疗资料。

参赛姓名、组别、评级、赛程、比赛结果和排名可向赛事参与者或页面访问者显示。对手可查看约赛联系电话和可约时间。完整出生日期及邮箱不作为公开成绩展示。ITT 未来出勤状态按队伍权限显示，可选缺席原因仅本人和有权限的队长可见；USTA 的个人出勤选择不向其他队员公开。公开的官方历史赛事资料不会因解除 App 绑定而删除。

3. 支付、兑换券和退款

我们保存线下网球赛事的报名订单、支付金额及状态、交易标识、退款、报名券发放与核销和领奖记录。支付卡资料在 Stripe 托管页面填写，按 Stripe 的条款处理；App 和赛事后台不读取或保存完整卡号或安全码。工作人员按权限处理报名、退款、评级核实和领奖。赛事付款购买线下参赛服务，不购买数字内容。报名券、退款及参赛资格以具体赛事规则为准。

4. 头像、导入和球拍工具

你选择发布的头像会上传，并按球员页面权限展示。导入截图在手机上识别文字，确认后将文字提交后台；选择文本文件时会读取并提交其中的文字。主动提供的文字、网页地址和私有计分卡用于相应导入或管理功能。相机仅在相应拍摄或扫码功能中使用；App 不读取通讯录或手机短信。

球拍检测在授权后短时使用麦克风，在手机上识别频率，不上传原始录音，也不长期保存录音。球拍昵称、拍面面积、线材与线径、穿线日期和设定磅数、识别频率、质量摘要及设备和 App 版本发送至后台，用于计算、基准、历史和同一账号同步。功能记录保留至删除；球拍诊断摘要最多保留90天。检测值用于观察相对变化，不替代专业测量。

5. 使用统计、失败与崩溃诊断

为排查问题、统计功能使用及改进服务，我们记录 App 和板块打开、页面访问、功能操作类型、前台时长、加载耗时、登录与恢复结果、绑定结果，以及固定错误分类、随机请求关联编号和系统提供的崩溃或无响应分类。记录包括事件发生时间、平台、系统与 App 版本、会话、哈希化安装标识，以及当时的登录状态、绑定状态和可用的哈希化账号范围标识。

这些标识属于去标识化数据，不能称为完全匿名。已登录、未登录、未绑定、已绑定和资料未知的情况分别统计；安装数不等于人数。延迟上传按事件发生时的状态归类，不能识别原始账号或板块的系统退出记录标为未知。功能使用统计不收集姓名、手机号、邮箱、生日、搜索词、比分内容、券码、支付卡信息、访问凭证、错误原文或原始堆栈；Android 未捕获异常只使用安全类型和代码指纹；iOS 使用 MetricKit 提供的延迟崩溃和卡顿诊断摘要，不上传原始堆栈。没有第三方广告标识或跨公司广告跟踪。

原始使用事件按14天到期策略清理，活跃去重安装哈希集合按32天到期策略清理，不含个人标识的每日汇总保留约13个月（395天）；云存储到期删除异步执行。手机待发送队列最多保留7天并限制条数与重试。系统诊断受系统版本和可用性影响，不保证捕获全部崩溃。

6. 通知、请求安全与客服

开启手机通知后，我们处理推送令牌、安装与 App 标识、语言、偏好、投递及已读状态，在 iOS 上使用 Apple 推送通知服务（APNs），在 Android 上使用 Google Firebase Cloud Messaging 发送通知。权限可在 App 或系统设置中关闭。站内消息按各板块规则保留。必要请求日志包含请求路径分类、状态、耗时及哈希化网络或安装标识，用于安全和故障排查；安装完整性可在 iOS 上通过 Apple App Attest、在 Android 上通过 Google Play Integrity 核验。

你主动发起的邮件或登录/绑定申诉可包含回复邮箱、问题类别和说明、选填球员信息，以及 App/系统版本和请求编号。仅有权限的工作人员访问客服记录。申诉记录目前没有自动到期删除规则；如需删除，请联系下方邮箱并提供工单编号。邮件内容由你自行填写，不要发送密码、验证码、恢复代码或银行卡信息。

7. 服务提供商、保存与删除

数据通过 HTTPS 传输。我们使用 AWS 等受控云服务，以及登录、推送和支付服务提供商，在提供上述功能所需的范围内处理数据。对其他用户的展示遵循上述赛事、队伍和球员权限。我们不出售这些个人数据，不将本次功能数据用于独立模型训练。

账号、关联及私有功能资料保留至删除或服务不再需要。你可在 App 的账号设置申请删除，或通过下方无需登录的网页及邮箱提出请求。删除共享账号会影响同一账号在 ITT Assist、Tennis Assist 和 Rolling League 使用的共享资料。RL 历史参赛者会去标识化；公开官方比赛资料、必要的订单、退款、券核销和安全审计记录可因对账、争议、安全或法律义务保留。未结赛事或资金事项可能需先处理，但始终可通过邮件发起删除请求。我们会说明仍需保留的范围和原因，不承诺所有数据统一即时清除。

8. 联系与个人资料请求

本应用不以儿童为主要目标。若涉及未成年人资料，或需要访问、更正、导出、删除资料，请邮件联系 hituptennis@gmail.com。我们会核实账号控制权后处理，不会只凭公开球员姓名修改或删除账号。

查看完整账号删除流程

English

1. Service and accounts

Hitup Tennis provides this independent app. It is not an official USTA app. We process the verified identifier, name and email supplied through Google or Apple sign-in for authentication, account management and support. Apple Hide My Email may supply a relay address. A profile name does not verify legal identity; matching names or emails do not automatically merge different sign-in accounts. We do not request ITT or USTA website passwords.

Sign-in accounts and player identities are managed separately. The ITT or USTA identity you choose to link can be used in apps using the same shared-account service. Racket records belong to the signed-in account. Signing out or unlinking a player does not automatically delete cloud records, cancel entries, transfer a competition identity or issue a refund.

2. Player, registration and match information

We process names, gender, full dates of birth, phone numbers, email addresses, player identifiers, teams, ratings, linking confirmations and entry details for identity matching, eligibility, competition operations and communication. Name or player-number searches are sent to the backend to find records; search text is not included in the feature-usage analytics described below. Match data includes divisions, schedules, availability, scores, confirmation status, placements and selected forfeit or retirement reasons. If you choose a health-related reason, that category is retained. Do not provide unnecessary detailed medical information.

Player names, divisions, ratings, schedules, results and standings can be displayed to participants or people viewing event pages. Opponents can view the contact phone number and availability used to arrange matches. Full birth dates and email addresses are not published as results. Future ITT attendance uses team permissions; an optional absence reason is limited to the player and an authorized captain. Personal USTA availability choices are not shown to other teammates. Unlinking an app profile does not delete public official match records.

3. Payments, vouchers and refunds

We retain orders for in-person tennis events, payment amounts and status, transaction identifiers, refunds, registration-voucher issuance and redemption, and prize-claim records. Card information is entered on Stripe-hosted checkout under Stripe’s terms; the app and event backend do not read or retain full card numbers or security codes. Authorized staff handle entries, refunds, rating verification and prize claims. Event fees pay for in-person participation, not digital content. Event rules govern vouchers, refunds and eligibility.

4. Photos, imports and racket tools

Profile photos you choose to publish are uploaded and shown under player-page permissions. Import screenshots are recognized on the phone; the text is sent to the backend after you confirm. Selecting a text file reads and submits its text. Text, links and private scorecards you provide support the relevant import or management feature. The camera is used when you choose a capture or scanning feature. The app does not read your address book or phone messages.

Racket measurements briefly use the microphone with permission to identify frequency on the phone. Raw audio is not uploaded or retained long-term. Racket nickname, head size, string materials and gauges, stringing date and machine tension, frequency, quality summaries, and device/app versions are sent to the backend for calculation, baselines, history and same-account synchronization. Functional records remain until deletion; racket diagnostic summaries are retained for at most 90 days. Estimates track relative change and do not replace professional measurement.

5. Usage, failures and reliability diagnostics

To troubleshoot and improve the service, we record app and module opens, page visits, feature-action categories, foreground duration, load times, sign-in and session-restoration outcomes, player-link outcomes, predefined error categories, random request-correlation IDs, and crash or unresponsive-exit categories supplied by the system. Records include event time, platform, OS/app version, session, hashed installation identifier, and the authentication state, linking state and available hashed account-scope identifier at the time of the event.

These identifiers are pseudonymous, not fully anonymous. Signed-in, signed-out, linked, unlinked and unknown-profile activity is distinguished; installations are not people. Delayed reports retain event-time context. System exits with no reliable original account or module are marked unknown. Feature-usage events do not collect names, phone numbers, email addresses, birth dates, search text, score contents, voucher codes, payment-card information, credentials, raw error messages or raw stacks. Android uncaught-exception summaries use a safe category and code fingerprint. iOS uses delayed crash and hang summaries supplied by MetricKit; raw stacks are not uploaded. We do not use advertising IDs or cross-company advertising tracking.

Raw usage events expire under a 14-day policy; hashed installation sets for active-installation deduplication expire under a 32-day policy; daily aggregates without personal identifiers remain for approximately 13 months (395 days). Cloud expiration is processed asynchronously. The phone’s bounded retry queue retains pending events for at most seven days. System diagnostics depend on OS version and availability and do not capture every crash.

6. Notifications, request security and support

If you enable phone notifications, we process push tokens, installation and app identifiers, language, preferences, delivery and read status, using Apple Push Notification service (APNs) on iOS and Google Firebase Cloud Messaging on Android. You can turn permission off in the app or phone settings. In-app messages follow their module’s retention rules. Necessary request logs include route categories, status, duration and hashed network or installation identifiers for security and troubleshooting. Apple App Attest on iOS and Google Play Integrity on Android may be used to verify installation integrity.

An email or sign-in/linking support request you initiate may contain your reply email, issue category and explanation, optional player details, and app/OS versions and request ID. Only authorized staff access support records. Support tickets currently have no automatic expiration rule. To request deletion, contact the email below with your ticket number. You choose your email content. Never send passwords, verification codes, recovery codes or payment-card details.

7. Providers, retention and deletion

Data is transmitted over HTTPS. We use controlled cloud services such as AWS, and sign-in, notification and payment providers, to process data needed for these features. Disclosure to other users follows the event, team and player permissions above. We do not sell this personal information or use these functional data for separate model training.

Account, linking and private functional records remain until deletion or until no longer needed for the service. Request deletion in account settings, or through the no-sign-in webpage and email below. Deleting a shared account affects its shared data in ITT Assist, Tennis Assist and Rolling League. Historical RL participants are de-identified; public official records and necessary order, refund, voucher-redemption and security-audit records may remain for reconciliation, disputes, security or legal obligations. Unsettled participation or financial matters may need resolution first, but you can always initiate a request by email. We will explain the scope and reason for retained data rather than promise immediate erasure of every record.

8. Contact and personal-data requests

The app is not primarily directed to children. For questions involving a minor or requests to access, correct, export or delete information, email hituptennis@gmail.com. We verify control of the account before acting; public player information alone does not authorize an account change or deletion.

Read the full account-deletion process