Jax Sets Privacy Policy

Version: 1.0　Effective date: 2026-10-24

1. Who processes your information

This policy is provided by Jax, an individual operator. It covers Jax Sets and the Jax platform services that support its accounts and sync. Contact: jaxops@163.com. It explains information needed for actual features and does not authorize undisclosed future collection.

2. Information and purposes

You may leave your nickname blank and choose not to specify gender. Training records may retain the profile snapshot from the time of training; changing your current profile does not automatically rewrite history. Do not include unnecessary identity documents, medical records or other people's information in plan names or feedback. Apple may process sign-in information under its rules. Our use is limited to account verification and necessary security, not access to other Apple Account content.

3. System permissions and local features

We explain permissions when needed for relevant features, and the system provides the choices. Current iOS workout sessions support training operation and the lock-screen experience. Under the current design, we do not read existing health history or write Jax training records to the Health database. Workout sessions request workout-related authorization. If declined, the corresponding session capability is unavailable; authorization can be managed in system settings. Live Activities, alerts and sounds are also subject to system settings.

Import, export and file selection use system pickers to access content you select; this does not authorize scanning the entire device. Cloud sync does not currently upload avatar files. Refusing an unnecessary permission does not affect unrelated features. We explain affected features where permission is requested. Privacy policy confirmation does not replace system authorization.

4. Providers, disclosures and storage location

The initial service region is mainland China, and business servers for accounts and cloud sync are hosted on Tencent Cloud in mainland China. Providing an English version does not mean overseas distribution is enabled. We will review applicable requirements and update this policy before expanding availability or changing data storage locations.

Apple provides identity verification and related system capabilities under its own rules. Cloud drives shown in file pickers and email services are selected by you or operated by the relevant providers. We do not sell your training content or use it for advertising profiles. We do not currently offer advertising or third-party behavioral tracking. Providers used for hosting, security and support should process information only within the described scope; “third-party services” is not a blanket description for undisclosed recipients.

We use Apple for Sign in with Apple and the information needed for identity verification (Apple's notice); Tencent Cloud for mainland-China server hosting of account, sync and security-related data; and 163 Mail to receive feedback, contact details and attachments you choose to send. Do not email passwords, verification codes or unrelated sensitive information. Before sharing information for a new independent purpose, we will explain the recipient, purpose and data involved and meet applicable notice and consent requirements.

5. Retention, deletion and security

Local content is retained while you use the features until you delete, replace or clear it through available system actions. Secure storage, device backups and exported files may have different lifecycles. Synced content is retained as necessary for account and sync services and processed through the relevant deletion workflow when requested. Reinstallation is not a request to delete cloud data.

We retain information for the shortest period necessary for the stated purposes, according to its category:

- General troubleshooting and application error logs are retained for 30 days. Relevant network security logs subject to legal retention requirements are retained for at least six months. We limit fields and access to what is necessary for troubleshooting, security and legal obligations, and do not log passwords, tokens, Apple authorization codes or complete training request bodies.

- Database backups are managed by the operator for disaster recovery; recovery of every historical version is not guaranteed. Backups are not used for advertising or purposes unrelated to recovery and security.

- Residual copies after deletion or account closure are not used for ordinary business and are removed during normal backup cleanup. Effective deletion and revocation requests must be applied during restoration so deleted content does not return to ordinary service.

Eligible online content is processed for deletion promptly after a request is verified; account closure progress is shown in the app or explained by email. Agreement records are retained only as necessary to establish applicable versions and handle rights requests. Minimal deletion markers are retained only while relevant copies may still be restored, with periodic review and removal of unnecessary information. Where a statutory retention period has not expired or deletion is temporarily technically infeasible, processing is limited to storage and necessary security protection.

We use transport protection, access controls and credential protection to reduce unauthorized access risks. We do not claim zero risk, end-to-end encryption or permanent recoverability. We take response and notification measures required by applicable rules if a security incident occurs.

6. Your choices and rights

You can use local features without signing in, choose whether to move local data as described on screen, and manage devices, permissions and your account. Signing out or revoking Apple authorization does not delete Jax cloud data. In-app deletion applies only to Jax Sets; contact the email address above for requests concerning the entire Jax Account.

Use available app controls or the contact address to request access, copies, correction or deletion, withdraw consent where processing relies on it, or exercise other applicable rights. We verify identity in a necessary and proportionate way and explain the outcome or a lawful reason why a request cannot be met. We do not ask for unrelated sensitive information. We normally respond within 15 working days of receiving a request with the result, any necessary additional information, or a progress update. For complex cases, we explain the reason and expected timeframe. Stricter applicable legal requirements take precedence. Withdrawal does not affect prior lawful processing, but may affect the relevant feature, without blocking unrelated local features. Necessary deletion and rights channels remain available if you have not accepted revised terms.

7. Children and young people

In mainland China, cloud accounts and cloud sync are not offered to children under 14 at initial release. Local timers that do not require an account remain available. Users aged 14–17 must obtain guardian consent to use accounts and cloud services and exercise under guardian guidance. We do not market to children or encourage excessive exercise.

Local features without an account do not require age information; local use does not mean there are no network access logs.

The app does not verify age or guardianship through an age selector or guardian checkbox, and does not routinely request identity documents or a full date of birth. If you believe we have inadvertently received information from a minor who does not meet these conditions, contact us by email. We will carry out necessary verification and take deletion or other protective measures as applicable.

8. Policy changes

This policy is available through About and the sign-in agreement links, with historical versions retained by the operator. Routine text updates do not trigger app notifications, additional checkboxes or suspension of sync. Updated versions and effective dates are available through About and the sign-in agreement links. New processing purposes are enabled only after establishing the appropriate basis and obtaining any required confirmation. Silence is not consent, and one sign-in confirmation is not authorization for every future purpose.

jaxops@163.com