Privacy Policy

I. Scope of Application, Operators and Core Principles

1.1 This Privacy Policy explains how FoxDub browser extension, official website, and associated accounts, recognition, translation, speech synthesis, heartbeat, configuration and payment services process personal information. It covers actual scenarios such as reading video subtitles, initiating web audio recognition, playing translated dubbing, registering and logging in, checking balances, purchasing goods and handling complaints. The business operations of independent video platforms and payment institutions are simultaneously subject to their own privacy rules.

1.2 "FoxDub" and "we" in this Privacy Policy refer to the operator of FoxDub services. The explanations of personal information processing and protection obligations in this Agreement apply to the products and associated services we provide.

1.3 We adhere to the principles of clear purpose, necessary scope, information transparency and restricted permissions. To complete the functions you choose, corresponding subtitles, audio and necessary account information may be processed, but this does not grant us the right to arbitrarily use your viewing content. We do not sell your subtitles, audio, personal information or viewing records, nor do we use this data for targeted advertising, credit assessment or commercial profiling unrelated to the selected functions.

1.4 We will not secretly and continuously collect audio to steal subtitle records, nor will we read unrelated personal files under the guise of translation functionality. However, "not stealing" does not mean "no network transmission occurs" or "servers have absolutely no cache and logs." Cloud recognition, third-party translation, speech synthesis, necessary caching and diagnostic logs may indeed process the content when you initiate functions, as detailed item by item below.

1.5 Reading this Agreement, installing the extension or logging into an account does not separately constitute blanket consent for all sensitive information, independent processing by third parties or cross-border transfers. Where separate consent, additional notification or other specific procedures are required by law, they must be completed prior to the relevant processing occurring. We cannot deem such procedures to have been completed solely based on the general wording of this Agreement.

II. Subtitles, Page and Media Information

2.1 To locate current video subtitles, match website rules, maintain dubbing synchronization and determine whether the page has switched, the extension reads media elements, subtitle text, subtitle tracks, video identifiers, titles, page or subtitle addresses, playback status and necessary subtitle request information from accessible pages related to the function. Some websites require page listeners to be installed before you start dubbing in order to capture subtitle requests that appear later; therefore, a blanket promise of "completely not reading page information before clicking start" cannot be made.

2.2 Page-side extraction is usually completed within the browser; subtitle text is sent to the actual service provider used during translation or synthesis, and certain subtitle resources are fetched by the extension backend. Our own servers and third parties will naturally receive network and content information necessary for the request. General website detection, video title display and page address comparison should not be used to establish a complete browsing history unrelated to translation.

2.3 The current usage duration ledger does not save video titles, viewing URLs and subtitle text for billing purposes; the usage records displayed in the user center mainly include sessions, devices, start and end times, and deducted duration. The local information retained by the extension for session binding, subtitle positioning and fault analysis constitutes different data from server billing records and cannot substitute for each other in explanation.

2.4 Subtitle and page content may contain names, contact information, health or financial information, statements by third parties and confidential materials. Please ensure lawful processing first. We do not uniformly classify originally publicly broadcast content as "containing no personal information," nor do we interpret your initiation operation as consent by all persons appearing or speaking for unrelated uses.

III. Tab Audio and Real-time Recognition

3.1 After you actively start AI simultaneous interpretation and pass account and balance verification, the extension uses browser tab audio capabilities to process the selected web audio source, convert it into audio clips suitable for recognition, and send them to our own recognition service, which then generates text via the actual recognition model provider. The current function does not use a microphone as a collection source, nor does it request camera images to generate subtitles.

3.2 Tab audio sources may include sounds from videos, courses, live streams, other participants in meetings, and notification sounds emitted from the same tab; it is not a guarantee of "only listening to the host and not processing any other sounds." When using private meetings or sensitive content, you should obtain the necessary authorizations and understand that relevant statements may enter cloud processing. We do not provide commitments regarding the authorization or tool usage of covert eavesdropping.

3.3 Original audio is used for real-time streaming and brief processing buffering; the current implementation does not provide a function to save entire segments of original audio as user cloud recording archives. However, recognition results form subtitle text, which may enter the logs described below; cloud providers also process inputs according to their own applicable rules. Stopping collection only prevents subsequent audio sending and cannot automatically withdraw already completed third-party processing.

3.4 Session closure occurs upon page refresh, navigation, switching pages or stopping recognition. When video is paused but the recognition connection remains active, audio input may be temporarily frozen while the session is retained, and wall-clock timing continues; to end that processing and timing, please use Stop Recognition. Specific boundaries should be verified against the current interface state, browser prompts and actual service behavior.

IV. Accounts, Verification and Security Credentials

4.1 Registration, login and password recovery require email, verification code, password verification values and necessary request information, used to create accounts, verify ownership, restore access and prevent abuse. Current passwords are converted into verification values on the client side before submission, but such verification values still belong to sensitive credentials usable for authentication, are not anonymous information, and should not be disclosed to any third party.

4.2 After logging in via the extension, necessary login credentials, account status and random device identifiers are saved in the browser's local extension storage, and necessary verification is performed with designated own account, heartbeat, recognition, translation, fallback synthesis and official website account handover services. Credentials should not be sent along with subtitle text to Google, Microsoft or other external content processing services.

4.3 The official website uses encrypted login session Cookies so that the server side can identify login status; current sessions typically last up to seven days, requiring re-login upon expiration, logout or verification failure. Official website page scripts do not directly read authentication values within those HttpOnly Cookies. Account synchronization for extensions jumping to the official website uses a short-term handover mechanism; opening the agreement page does not require prior login, nor does it require you to submit identity proof for reading the agreement.

4.4 Sending verification codes requires handing over emails and email content to actual mail delivery services for processing. Temporary email restrictions mainly check email domains; maintaining domain blacklists does not aim to submit your complete email to third-party blacklist sources. Anti-abuse measures may also use request time, IP address and error categories; this information should only serve verification security and necessary fault handling.

V. Devices, Heartbeats, Configuration and Usage Records

5.1 A random device identifier is generated upon extension login, used to distinguish device sessions, maintain online device limits and isolate duration consumption across different devices. This identifier is not a fixed identity generated by reading hardware serial numbers and does not imply that we can individually identify a specific real person solely from it. Heartbeat requests contain necessary account verification information, device identifiers and online status, typically occurring approximately once every five minutes.

5.2 AI billing saves user identifiers, device identifiers, session or pre-paid request identifiers, start and end times, prepaid seconds, actual deducted or refunded seconds, balance changes and settlement status. Purposes include deduction, renewal of pre-payment, disconnection remediation, balance inquiry and resolution of billing disputes. The current user center typically queries usage records for the past sixty days; this display window does not equal the backend database automatically deleting all ledgers after sixty days.

5.3 The Management Configuration Service issues the identification models, translation channels, and proprietary service configurations required for account-based functionality; it extends to caching locally and fixing the actual configuration at the start of a task. Settings such as model selection, target language, voice tone, subtitle style, volume, and playback method are primarily used to operate the functionality and shall not be converted into irrelevant advertising interest tags.

5.4 Local usage statistics are time-bucketed from queryable usage records; the usage card need not upload additional viewing titles or subtitle text. Account membership status, balance, and usage queries will naturally generate server request records. We shall not misstate that "only local charts are displayed" to imply that account usage has never been processed by servers.

VI. Purchases, Orders, Renewals and Customer Service Information

6.1 When purchasing services, FoxDub processes account ownership, products and quotes, currency, amount, order number, payment or subscription identifiers, creation time, payment status, delivery and refund records, and data returned by payment institutions necessary for transaction verification. Some return data may include the payer's email, payer or account identifiers, and related transaction evidence; we must not generalize all payment returns as completely anonymous data.

6.2 Complete bank card numbers, card security codes, and payment institution login passwords are typically processed by the payment institution on its own pages; FoxDub does not require you to input them into this service page. The transaction information we receive shall not be made public, nor should it be concatenated with subtitle text to infer personal consumption preferences.

6.3 Customer service may receive problem descriptions, order numbers, screenshots, logs, and contact information you voluntarily provide, for the purpose of handling faults, refunds, complaints, and requests regarding personal information rights. Please obscure unrelated personal information first; support staff shall not require you to publicly post complete subtitles, private meeting records, or passwords. When specific content needs to be read to assist in troubleshooting, the scope shall be explained and applicable permission obtained.

6.4 Requester identity verification shall be commensurate with risk. For sensitive account data or deletion requests, we may need to verify email control and order ownership; for general functional inquiries, collecting additional identification documents shall not be mandatory. Complaints and feedback shall not be automatically repurposed for advertising, user review promotion, or general model training.

VII. Purposes of Processing and Impact of Refusal to Provide

7.1 Subtitle and audio content are used for your selected identification, translation, synthesis, display, follow-playback, and necessary quality checks; account credentials are used for verification; devices and heartbeats are used for session and device management; ledgers are used for billing, delivery, and disputes; necessary logs are used for security, fault analysis, and service reliability. Data of different categories must correspond to specific purposes and shall not be expanded in collection merely because it is technically obtainable.

7.2 Refusing email or account verification may prevent registration, login, querying of one's own rights, or use of functions requiring authentication; refusing tab audio permissions will cause real-time identification to fail, but this shall not compel you to enable the microphone; refusing to submit subtitles or voice to the cloud will prevent completion of corresponding online identification, translation, or synthesis. You may choose not to submit materials that are not necessary for operation.

7.3 This product currently relies on online services; "stopping a certain free translation engine" shall not be understood as all content being processed locally thereafter, nor shall selecting proprietary servers be understood as proprietary servers absolutely not calling external models. The channels actually adopted are determined by current functionality, personal choice, and management configuration; relevant material changes shall remain consistent with the publicly disclosed data description.

7.4 Involving contract performance, statutory obligations, valid consent, or other bases recognized by applicable law, we shall determine the basis for processing according to specific scenarios. Consent for one purpose shall not be infinitely extended to all purposes; withdrawing consent for a non-essential purpose shall not affect other necessary processing based on existing legal grounds, nor shall it become a reason for refusing to provide unrelated basic services.

VIII. Third-party Providers and Data Flow List

8.1 The following are the main service categories involved in the current implementation. Not every task calls all channels; if a free engine fails, it may switch to backup services according to actual configuration. The actual legal entities, regions, and rules of providers shall be verified against effective service contracts and the official explanations below; one cannot hide the actual recipients under a generic term like "partner."

8.2 We shall take necessary constraints, notifications, and security measures according to the actual relationship of entrusted processing or independent provision, and obtain separate consent where legally required. Information is provided only when functionally necessary, to fulfill legal obligations, for security protection, or under other applicable lawful conditions; general cooperative relationships are not grounds for sharing all account, subtitle, and payment data.

8.3 Current production functions do not inherently send data to all historical providers due to code retaining historical debugging backends. If new identification, translation, or synthesis providers are subsequently activated in practice, the corresponding list and important data notifications shall be updated first; where re-confirmation is legally required, processing shall only commence after confirmation is completed. Third-party policies do not automatically exempt us from responsibility for selection, configuration, and transmission behaviors.

IX. Sensitive Information and Cross-border Processing

9.1 Current cloud identification and fallback translation can be performed in Singapore; account databases and some services are also deployed in Singapore; Google, Microsoft, and PayPal networks may also process necessary data in other countries or regions. Therefore, we cannot promise that all information is only kept within China or solely stored on your device. The actual receiving region of data shall be consistent with the current configuration and provider statements.

9.2 When providing personal information across borders as required by applicable laws, we shall inform the recipient of its identity, contact channels, processing purposes, methods, categories, and the means for exercising rights against the recipient prior to processing, and satisfy the requirements of applicable cross-border mechanisms and separate consent. The text on this page does not constitute a button for separate consent, nor does it certify that relevant assessments, contracts, certifications, or other procedures have been completed.

9.3 When subtitles or audio contain health, financial, identity, private meeting, minor-related information, or other sensitive data, processing may entail higher impact. Please avoid submitting materials you are not authorized to transmit. We do not conduct voiceprint identification using these features; the use of audio for transcription does not imply that additional biometric templates can be extracted. Where processing of sensitive personal information is strictly necessary, sufficient necessity must be demonstrated, and applicable enhanced protection and consent procedures must be fulfilled.

9.4 You may control subsequent processing by stopping relevant cloud functions, revoking permissions, or submitting rights requests. Necessary data retained for payment, legal obligations, or legitimate disputes may not be immediately deleted but shall not continue to be used for new unrelated purposes. We shall assist you in understanding the rights channels of external providers, rather than leaving you to bear all risks associated with cross-border processing alone.

X. Local Storage, Cookies and Temporary Content

10.1 Browser native extension storage saves login status and authentication values, random device identifiers, personal settings, configuration caches, and necessary states; browser session storage may also temporarily save tab references, page addresses, and expiration markers required to restore operations after login. These are used for the current account, operation recovery, and function execution, and do not represent that information will never leave the local machine; necessary authentication values are still sent to limited proprietary services.

10.2 Official website native storage is used for language and light/dark theme preferences; session storage may save order references or in-transit markers required for payment recovery to avoid duplicate submissions. Login cookies are used to maintain sessions, and their lifecycle differs from page preferences. You may clear these contents in browser settings; after clearing, you may need to log in again, select interface preferences, or re-query transactions.

10.3 The current official website does not integrate advertising tracking scripts or cross-site cookies for advertising purposes within pages. Ordinary static resource requests and infrastructure security logs still generate necessary network information; this statement does not mean “the website has no logs whatsoever.” When non-essential analytics, advertising, or new tracking technologies are added in the future, we shall first inform you in accordance with the law and obtain valid opt-outs where required.

10.4 Subtitle history, translations, audio queues, and playback status within web pages may be retained in memory during the current task to facilitate display, live following, and playback review; files actively exported or downloaded by users are managed by the user and the device environment. Clearing website cookies does not automatically clear extension storage, downloaded files, or server ledgers; logging out does not mean all data has been permanently deleted.

XI. Server Cache, Audio Files and Logs

11.1 The diagnostic output of the current recognition service may contain the recognized original text, and service operation logs may therefore retain subtitle content. Translation services default to primarily recording language, character count, duration, and result category; when configurations such as body text diagnostics are enabled, related text may also be recorded. We cannot promise that “subtitle body text will never enter server logs.” Such content shall be limited to fault handling, security, and necessary service disposal, and shall not be used to establish marketing-oriented viewing profiles.

11.2 Translation results may use bounded memory caches to avoid duplicate requests; caches are evicted by capacity and cleaned up according to process lifecycle, and there is no guarantee of deletion after a fixed number of minutes. Proprietary translation and synthesis services also have necessary authentication success caches, currently fixed at twelve hours; this is a verification result cache and does not indicate that all content caches are only saved for twelve hours.

11.3 The fallback TTS service saves synthesized speech as server audio files, with file names generated based on the hash/digest of text and timbre; the current implementation has no automatic expiration deletion mechanism. Audio files are used for caching and returning playback, and do not serve as your personal permanent cloud recording space; synthesized files may still reveal text content, and one cannot assume they are fully anonymized simply because the file name is a hash/digest.

11.4 The current fallback audio uses an access method where possession of the corresponding URL allows requests; audio GET requests do not perform per-user verification, and browser or network caches may retain copies. Links are not public directories, but neither are they strict account-private storage. Do not use this channel to process content requiring strict confidentiality, or forward corresponding playback links to others. Cached content associated with you should be able to be verified, restricted, or deleted through privacy request applications.

11.5 Logs, caches, and user-downloaded copies have different retention mechanisms. Stopping recognition, closing pop-ups, or deleting local data will not automatically synchronize revocation from server logs, audio files, and materials already processed by third parties. We shall explain the locatable scope, retention basis, and execution results, and shall not exclude personal information protection obligations by claiming “they are merely technical logs.”

XII. Retention Periods, Deletion and Backups

12.1 Retention shall follow the principle of the shortest period necessary to achieve explicit purposes; where legally required, transaction disputes, and security events genuinely necessitate it, corresponding ranges of data may be retained. We do not interpret “improving services” as retaining all subtitles, audio, and account information indefinitely, nor do we treat “user has not requested deletion” as the sole reason for permanently retaining unrelated content.

12.2 Local settings and login status are managed according to browser storage, logout, and cleanup operations; task buffers are cleared by session; memory translation caches are evicted by capacity and process lifecycle. Account records are retained during the normal provision of account services and handled according to applicable obligations after cancellation. The usage page displays the last sixty days, and the billing page displays the last year; both are merely query scopes and do not guarantee backend automatic cleanup periods.

12.3 The current server audio cache and some logs do not have a unified automatic deletion period; therefore, this version explicitly discloses this status quo and does not fabricate promises such as “cleared in twenty-four hours.” Operators shall formulate and implement necessary retention periods according to content categories; before automatic cleanup rules are perfected, identifiable and locatable relevant personal information shall support lawful verification and deletion requests, and shall not be refused due to the temporary absence of an automatic button.

12.4 Payment, refund, subscription, benefit ledgers, and dispute evidence may be retained in accordance with tax, audit, cybersecurity, or transaction rule requirements. Retention shall be limited to fields and timeframes necessary for legal or dispute purposes; one cannot use the reason of retaining payment evidence to simultaneously retain all private subtitles. Upon expiration, data shall be deleted or effectively anonymized; anonymization shall not merely refer to replacing an account number with another number that can still be reverse-looked up.

12.5 There may be reasonable delays in data deletion for backups and independent providers. For information that must be retained by law or is technically difficult to delete immediately, inappropriate processing other than storage and necessary protection shall cease, and reasons and scope shall be explained. Backup restoration shall prevent data that has already been deleted from re-entering general use; we do not indefinitely extend executable deletion operations by citing “backups may exist.”

XIII. Sharing, Disclosure, Human Access and Training Boundaries

13.1 Your subtitles, audio, translations, and account information are not sold to advertising platforms, data brokers, or other information resellers, and are not used for personalized advertising, loan eligibility, or credit judgments. Transmission to necessary providers to provide selected recognition, translation, synthesis, login, or payment services is distinct from selling or arbitrary disclosure; recipients, fields, and purposes shall be strictly limited.

13.2 We do not arbitrarily use your subtitles, original audio, translations, private meeting content, payment information, or customer service attachments to train or fine-tune general artificial intelligence models. Using existing models for inference and returning translations is not equivalent to obtaining training permission. Model providers may have their own retention and data rules; we cannot rely solely on this page’s commitment to assert that all their systems do not retain data or make other processing; actual service terms shall be checked, and necessary constraints and disclosures shall be fulfilled.

13.3 Ordinary use does not authorize staff to arbitrarily review subtitles or listen to synthesized audio. Human access shall be limited to specific materials explicitly requested for processing, security incidents necessitating such access, obligations required by law, or applicable compliance internal operations, with control over participating personnel and scope. Necessary diagnostics shall not be disguised as a means to evaluate private viewing habits, disseminate personal content, or create promotional case studies.

13.4 When providing information to competent authorities as required by law, the authority, necessary scope, and procedures of the request shall be verified. Except in circumstances where legal restrictions prohibit notification, appropriate explanations shall be provided. In the event of merger, change of operating entity, or asset transfer, the actual recipient and its protection responsibilities shall be informed in accordance with the law; if the new entity changes the original purpose or requires re-consent by law, corresponding procedures shall be completed, and it cannot automatically inherit the right to arbitrarily use all historical content.

13.5 FoxDub’s use and transfer of information obtained from Google APIs and other applicable browser user data comply with the Chrome Web Store User Data Policy, including Limited Use requirements. Data is used only for disclosed functions and necessary operations; this statement does not constitute a request for additional account permissions to Google, nor does it erroneously interpret other service data as coming from Google APIs.

XIV. Rights to Access, Correct, Copy and Delete

14.1 You may view membership status, AI duration, queryable usage, and your own orders through the existing product pages, and adjust language, voice tone, display, or playback options in Settings. If a page does not provide for a certain action, you may apply to access, copy, correct, supplement, delete, or restrict the processing of personal information that legally belongs to you through formal privacy request channels. We shall explain the scope of processing that can be performed, rather than refusing solely because there is no button on the interface at present.

14.2 When making a request, please provide a verifiable account email, the category of data involved, and an approximate time; it is usually unnecessary to send full subtitles or sensitive identification documents. Since audio caches may not be directly linked to accounts, if you know specific playback links or the time corresponding to the content, you may provide them privately for location purposes. We must not require you to upload private audio in public areas for the sake of facilitating location.

14.3 To prevent impersonation by others, we may implement reasonable identity verification; refusal to provide materials disproportionate to the risk of the request should not automatically result in the rejection of all rights. For matters involving others' privacy, statutory confidentiality obligations, payment disputes still being processed, or data that must be retained by law, we may restrict corresponding requests in accordance with the law, but shall explain the specific basis and alternative methods available.

14.4 Corrections shall be based on true circumstances and verifiable records, and cannot be used to forge charges, erase unsettled payable transactions, or obtain other users' account content through personal information rights requests. Conversely, reconciling accounts does not mean we have the right to permanently retain unrelated subtitles. Separably deletable content shall be handled independently, and deletion of all other information shall not be refused simply because one order needs to be retained.

XV. Withdrawal of Consent, Cessation of Processing and Account Cancellation

15.1 You may control subsequent local processing by stopping dubbing and recognition, disabling specific features, revoking browser permissions, logging out of your account, or uninstalling extensions. For specific uses legally based on consent, you may withdraw such consent through formal channels; withdrawal does not affect the legality of processing previously conducted based on valid consent, nor does it automatically terminate necessary processing still based on contractual performance or statutory obligations.

15.2 The current product does not have a self-service automatic account cancellation button; account cancellation and related server deletion require application through confirmed customer service/privacy channels. Before cancellation, please process pending orders, save records you need, and separately confirm that auto-renewal has been cancelled. We shall not set unreasonable obstacles to cancellation; remaining paid benefits and dispute resolution shall follow effective order agreements and statutory rights.

15.3 The actual execution of cancellation and deletion shall cover associated accounts, devices, authentication, and content no longer necessary; ledgers required by law to be retained shall have their use restricted. Merely logging out, removing software, or clearing page cache does not indicate that the payment institution's subscription has been cancelled, server data has been deleted, or third-party copies have synchronized away. We shall inform you of the scope executed and necessary retention exceptions.

15.4 If relevant requests involve services independently provided by third parties, we shall provide assistance and practical contact channels within our control; payment accounts, website content, and their statutory records independently decided by third parties require you to exercise corresponding rights through their channels. We shall not shift the processing responsibility for our own databases and logs entirely to third parties.

XVI. Security Measures and Incident Handling

16.1 Own online services use HTTPS or WSS to transmit necessary data, and official website login sessions are protected by encryption and HttpOnly attributes. Local authentication values, server accounts, and order data shall be accessed according to necessary permissions. We do not describe password verification values as unrecoverable anonymous data, nor do we make false guarantees such as "absolutely no leakage," "all data are end-to-end encrypted," or "all caches are private."

16.2 Security protection also includes credential control, necessary access management, input validation, rate limiting, session isolation, and exception handling. Specific measures must be consistent with actual deployment; any text cannot replace engineering execution. The boundaries of current fallback audio links and server content logs have been disclosed in Article Eleven; they still belong to content requiring restricted use and gradually improved protection.

16.3 In the event of or potential occurrence of personal information security incidents, we shall take loss-prevention, investigation, and remedial measures in accordance with legal requirements, report to competent authorities, and notify affected individuals where applicable, explaining the categories of information involved, possible impacts, measures taken, suggestions to reduce risks, and contact information. We shall not conceal substantive events that require notification by law due to concerns about reputation.

16.4 Please properly safeguard your device, email, and payment account, do not forward credentials, verification codes, or playback links containing private content to unrelated persons, and log out promptly and clear necessary local data after using shared devices. Your duty of care for security does not replace our obligation to protect; damages caused by product or operational faults shall be borne in accordance with facts and law.

XVII. Minors, Policy Changes and Versions

17.1 This product is not specifically designed for children. Guardians should guide minors to control the provision of personal information and payment behavior; when processing personal information of minors under the age of fourteen, valid consent from guardians must be obtained in accordance with the law, and applicable special protections must be implemented. Upon learning that relevant information has been collected without meeting conditions, we shall verify and delete it in accordance with the law or take other corrective measures.

17.2 This Privacy Policy version is 1.0, with the update date being Beijing Time 2026-10-10. A lengthy document does not lower the requirement for clear disclosure; important processing methods cannot be hidden only at the end of the page, nor can invalid consent be obtained through default checkboxes.

17.3 When new data categories are added, purposes are changed, new independent recipients are introduced, overseas regions are altered, or significant impacts on individual rights occur, the policy shall be updated first and highlighted in appropriate ways. Where re-obtaining consent is required by law, it shall be completed before the new processing begins. Users continuing to read, merely installing updates, or failing to discover announcements in time shall not be automatically deemed to have authorized all new uses.

17.4 When translations are provided for a certain language, the version and differences shall be explained. The current main text is provided in Simplified Chinese; switching the official website interface language will not turn the Chinese main text into another language agreement reviewed by law, nor will it change the data flow. Rights that cannot be excluded by law in your location shall not be unreasonably restricted by the language of the main text or general dispute clauses.