Introduction
Welcome to DeepWorks software and related services. This service is provided by Deepexi Technology Co., Ltd. ("Deepexi" or "we"), whose registered address is Room 1001-1002, 10th Floor, Building 1, No. 62 Xueyuan South Road, Haidian District, Beijing. We attach great importance to the protection of users' personal information and enterprise data, and will take corresponding security protection measures in accordance with laws and regulations. This DeepWorks Privacy Protection Guide ("this Guide") explains how we collect, store, use, and otherwise use your personal information when you use DeepWorks. This Guide applies to DeepWorks product features and services provided on Windows and Mac clients and their supporting remote capabilities. Features supported by different terminals, versions, deployment methods, or account types may vary. Features that are not provided or enabled do not involve the corresponding personal information processing activities. Please carefully read and fully understand this Guide before using DeepWorks, especially terms that exempt or limit Deepexi's liability or exclude or restrict your rights. Such terms are highlighted in bold for your special attention. If you do not understand or agree to any part or all of this Guide, please do not use DeepWorks. Once you start using DeepWorks, you indicate that you have fully understood and agreed to all contents of this Guide. In specific feature or service scenarios, we may provide supplementary explanations of the purposes, scope, and methods of processing relevant information through the DeepWorks User Agreement, pop-up prompts, page descriptions, feature update notes, or other reasonable means. Such supplementary explanations and this Guide jointly constitute the personal information processing rules applicable to the relevant scenarios.
I. Definitions
1.1Individual user: a user who registers, logs in, or uses DeepWorks and related services as a natural person.
1.2Enterprise user: a user who enables, configures, manages, or uses DeepWorks and related services in the name of a legal person, unincorporated organization, government agency, public institution, social organization, partnership, individually owned business, or other entity.
1.3Administrator: an individual authorized by an enterprise user who has management permissions for enterprise accounts, organizational structure, member permissions, resources, audits, security policies, and similar matters.
1.4End user: an individual, including employees, outsourced personnel, collaborators, or other personnel authorized by the enterprise user, who is assigned an account or included within the management scope by the enterprise user and uses DeepWorks under the enterprise user's management. An end user is a type of individual user. When using services under an enterprise account, the special provisions of this Guide regarding enterprise data and end users also apply.
1.5Enterprise data: data submitted, generated, or produced by enterprise users and their end users within the scope of authorization, configuration, or management by the enterprise user when using DeepWorks based on an enterprise account. This includes enterprise information, organizational structure, account and permission information, service usage records, resource consumption records, log audit information, and input and output content of administrators and end users. Enterprise data is usually processed for purposes and by methods determined by the enterprise user.
1.6Input content: content actively submitted by a user or authorized by the user to be obtained by DeepWorks during use of DeepWorks, including text, images, documents, code, operation instructions, files, task descriptions, or other forms.
1.7Output content: content generated, returned, or executed by DeepWorks based on user input, model capabilities, tool invocation, knowledge bases, plugins, or other service capabilities.
1.8Personal information: various information recorded electronically or otherwise that relates to an identified or identifiable natural person, excluding anonymized information.
1.9Sensitive personal information: personal information that, once leaked or illegally used, may easily harm the dignity of a natural person or endanger personal or property safety, including biometric information, religious beliefs, specific identities, medical and health information, financial accounts, whereabouts, and personal information of minors under the age of fourteen.
1.10User or you: unless otherwise stated, refers collectively to enterprise users, administrators, end users, and individual users.
1.11Laws and regulations: applicable laws, administrative regulations, departmental rules, local regulations, regulatory documents, judicial interpretations, regulatory requirements, and other legally effective documents.
II. Scope of this Guide
2.1This Guide explains how, during user registration, login, configuration, use, and management of DeepWorks and related services, we collect, store, use, process, transmit, provide, disclose, delete, or otherwise process personal information actively submitted by users, generated by systems, or necessarily collected to provide services.
2.2This Guide does not apply to products or services independently provided by third parties that determine processing purposes and methods by themselves. For example, third-party models, plugins, data sources, cloud services, external websites, or enterprise-owned systems configured by users may be subject to the privacy policies, service agreements, or data processing rules of the relevant third parties.
2.3If we access or invoke third-party models, plugins, service providers, or infrastructure to provide DeepWorks features to users, and such access involves our collection, sharing, entrusted processing, or transmission of personal information, the relevant processing activities remain subject to this Guide and corresponding supplementary explanations.
2.4If an enterprise user has separate agreements with us through contracts, privatized deployment documents, data processing agreements, or other written documents, the rules for processing relevant personal information and enterprise data shall be determined by those documents together with this Guide. If there is any inconsistency, the more specific agreement shall prevail.
III. Information We Collect
3.1The ways in which we collect information include but are not limited to:
(1)Information actively filled in by users, such as the mobile phone number that may be provided during account registration, and text, images, audio, or other files uploaded or submitted during use.
(2)Information authorized and provided by third-party platforms. If you log in to and use the Software through a third-party platform, we will obtain your personal information from that third-party platform according to the agreement you signed with the social network platform.
(3)Information automatically collected. When you access and use this service, we automatically collect device and connection information, log information, usage information, sandbox environment data, and similar information.
3.2The information we collect and the purposes are as follows:
(1)When you register, log in, or use DeepWorks, you may need to provide or authorize us to process your mobile phone number, email address, login username, nickname, avatar, account identifier, verification code, login credentials, third-party account authorization information, enterprise member account, administrator account, and similar information. Some services may require real-name authentication, enterprise authentication, or administrator verification in accordance with law or account security requirements.
(2)If you choose to log in to DeepWorks with a third-party platform account or associate a third-party account with a DeepWorks account, we will process necessary information provided by that third-party account within your authorization scope, such as account identifier, nickname, avatar, mobile phone number, email address, or other information expressly displayed on the page. If relevant services require real-name identity verification in accordance with law, you may also need to complete authentication or authorize synchronization of authentication results within DeepWorks.
(3)To ensure service stability, security, and traceability, we record login time, identity identifiers, operation time, operation content, IP address, device information, client version, system type, browser type, network environment, error logs, service invocation records, resource consumption records, and similar information.
(4)To provide continuous services, troubleshoot faults, optimize experience, and prevent risks, we may collect device identifiers, operating system information, device models, client versions, browser fingerprints, network status, task execution time, input and output time, response latency, feature trigger counts, adoption status, exception stacks, crash logs, and similar information.
(5)Intelligent conversation is used to understand user input and generate answers, plans, task plans, or executable instructions. Input content you submit in conversation boxes, file entries, task entries, or remote entries may include text, images, files, code, operation instructions, scheduled tasks, webpage content, or other materials you actively provide.
(6)When the default model is used, input content that you actively submit or authorize DeepWorks to obtain will be collected and processed by us as needed for the service and sent to the corresponding model service for inference, generation, and return. To provide continuous, stable, and consistent service experience, we may save conversation records with DeepWorks, including input content, output content, conversation topics, context summaries, and task execution records. i. When using a custom model, you may need to configure the model API key, access address, or other connection parameters in DeepWorks. Such information is usually stored on the local device or in an enterprise-designated environment. Except for completing user requests, necessary transmission, security audit, troubleshooting, retention in accordance with law, or other cases expressly notified and authorized, we will not read or store input content sent by users to custom models or returned content beyond the necessary scope. ii. When you actively paste content from the system clipboard into a DeepWorks input box, task window, or file processing entry, DeepWorks processes the clipboard content locally to complete the paste, analysis, generation, or execution request you initiate. iii. To continuously improve service experience and model effects, we may use input content, output content, and service records for product improvement, model effect evaluation, and service quality optimization after applying encryption, desensitization, de-identification, anonymization, or other measures and avoiding identification of specific individuals. If the product provides an experience improvement plan or similar setting, you may disable the relevant authorization on the corresponding page. After disabling it, we will stop using your relevant input and output for that optimization purpose. iv. If your input content, feedback, uploaded files, or other submitted materials contain personal information of others, please ensure before submission that you have obtained authorization from the personal information subjects. For sensitive personal information, separate consent should be obtained in accordance with law.
(7)Intelligent operations are used to assist users in performing local operations, web access, software operations, file processing, script execution, or automated tasks based on conversation or task plan output. i. If a task can be completed in the user's local device environment, such as opening files, modifying files, reading directories, generating documents, executing scripts, or invoking local tools, DeepWorks will execute it on the user's device or in an enterprise-designated environment. We will process relevant information according to user instructions and feature implementation needs. ii. If a task involves accessing third-party websites, operating third-party software, or invoking third-party services, interaction information between the user and the third party may be independently collected and processed by that third party. Except where the user actively submits new input content through DeepWorks, or where DeepWorks must process information to complete the user's explicit instruction, we will not decide such information processing rules on behalf of the third party.
(8)Remote features. To facilitate users remotely initiating conversations, submitting tasks, or receiving results, DeepWorks may provide remote entries, mobile entries, enterprise collaboration entries, or other remote connection capabilities. When you use relevant features, we may collect account identifiers, remote entry identifiers, avatars, nicknames, binding status, input content, task status, execution results, notification records, and similar information to associate remote requests with local clients, enterprise accounts, or task environments.
(9)To implement relevant features, DeepWorks may invoke necessary permissions according to different terminals and specific scenarios. Sensitive permissions are not continuously enabled by default and usually require authorization by the user or enterprise administrator. Permission authorization does not mean that we will continuously collect corresponding information. We only process relevant information within the scope necessary to implement features. Windows permission list: i. Network access permission is necessary to ensure the normal operation of basic features such as account login, model/API invocation, plugin capability access, and task result return. This permission is required for product operation and is not optional. It is mainly used in daily login, AI Q&A, task execution, and similar scenarios. If this permission is refused or restricted, product features will be affected and DeepWorks may not function normally. ii. System clipboard read permission is needed when the user actively pastes content from the local device system clipboard into a DeepWorks input box. This permission is necessary for the paste function and is not optional. It is only used when the user actively pastes content. If refused or restricted, the user will not be able to paste copied content into DeepWorks. iii. Local file read permission is needed when the user specifies a local file and asks DeepWorks to analyze, summarize, process, or generate results from the file. This permission is optional and is used only when the user selects a relevant file or initiates a relevant task. It is mainly used for document parsing, code analysis, content extraction, task execution, and similar scenarios. If refused, DeepWorks cannot process tasks related to local files. iv. Local file deletion permission is needed when the user explicitly requests deletion of specified files, cleanup of temporary files, or cleanup of result files. This permission is optional and is used only when the user gives an explicit deletion or cleanup instruction. If refused, DeepWorks cannot execute file deletion, temporary file cleanup, or result file cleanup. v. Local file write/modify permission is needed when the user asks DeepWorks to generate, save, or modify local files. This permission is optional and is used only when the user initiates file generation, saving, or editing tasks. It is mainly used for editing documents, modifying code, generating result files, and saving task artifacts. If refused, DeepWorks cannot directly edit or save relevant files, and the user must complete the corresponding operation manually. vi. System command/code execution permission is needed when the user asks DeepWorks to execute local scripts, commands, or automated processes to complete specified tasks. This permission is optional and is used only when the user initiates relevant tasks. It is mainly used for environment checks, script execution, project builds, automation processing, and similar tasks. If refused, some automation and engineering tasks cannot be executed. vii. Browser control/automation permission is needed when the user asks DeepWorks to operate a browser to complete webpage access, testing, queries, or process automation. This permission is optional and is used only when the user initiates relevant browser operations. It is mainly used for webpage testing, form filling, page retrieval, business process automation, and similar scenarios. If refused, DeepWorks cannot execute browser automation tasks and the user must complete them manually. Mac permission list: i. Network access permission is necessary to ensure normal operation of basic features such as account authentication, model invocation, plugin access, and remote resource access. This permission is required for product operation and is not optional. It is mainly used for user login, AI Q&A, task execution, result synchronization, and similar scenarios. If refused or restricted, product capabilities will be affected and DeepWorks may not function normally. ii. System clipboard read permission is needed when the user actively pastes local device system clipboard content into a DeepWorks input box. This permission is necessary for the paste function and is not optional. It is only used when the user actively pastes content. If refused or restricted, the user will not be able to paste copied content into DeepWorks. iii. Local file read permission is needed when the user specifies a local file and asks DeepWorks to analyze, summarize, retrieve, or process it. This permission is optional and is used only when the user selects a relevant file or initiates a relevant task. It is mainly used for document parsing, code analysis, content extraction, task execution, and similar scenarios. If refused, DeepWorks cannot access local files or process tasks related to local files. iv. Local file deletion permission is needed when the user explicitly requests deletion of specified files, cache cleanup, or removal of task artifacts. This permission is optional and is used only when the user gives an explicit deletion or cleanup instruction. If refused, DeepWorks cannot execute file deletion, cache cleanup, or task artifact removal. v. Local file write/modify permission is needed when the user asks DeepWorks to create, save, or modify local files. This permission is optional and is used only when the user initiates file creation, saving, or editing tasks. It is mainly used for editing documents, modifying code, generating result files, and saving task artifacts. If refused, DeepWorks cannot directly edit or save relevant files, and the user must complete the corresponding operation manually. vi. System command/code execution permission is needed when the user asks DeepWorks to execute local commands, scripts, or automated processes to complete specified tasks. This permission is optional and is used only when the user initiates relevant tasks. It is mainly used for environment checks, script execution, project builds, automation processing, and similar tasks. If refused, some engineering and automation tasks cannot be executed. vii. Browser control/automation permission is needed when the user asks DeepWorks to operate a browser to complete webpage access, testing, queries, or process automation. This permission is optional and is used only when the user initiates relevant browser operations. It is mainly used for webpage testing, form filling, page retrieval, business process automation, and similar scenarios. If refused, DeepWorks cannot execute browser automation tasks and the user must complete them manually.
(10)When you submit questions through customer service, online consultation, surveys, feedback entries, or other channels, we may collect contact person, contact information, issue descriptions, screenshots, logs, communication records, handling results, and similar information for issue diagnosis, support, service improvement, and contract performance.
(11)To improve the continuity, personalization, and task execution efficiency of intelligent conversation and intelligent operations, DeepWorks may provide cross-session memory capabilities. Memory features may extract reference-worthy memory data based on user conversation content, task preferences, work background, project background, commonly used formats, recent concerns, and similar information, and use it as context in later conversations or task execution. You may view, edit, delete, or disable memory features through product settings. After disabling, DeepWorks will stop extracting new memory data.
(12)Enterprise users may entrust us to process enterprise data for purposes such as account and permission management, resource management, service statistics, log audit, security management, and enterprise collaboration. In such scenarios, enterprise users usually determine the processing purposes and methods, and we act as an entrusted processor to process relevant information according to enterprise user instructions, contractual agreements, and security management needs.
(13)Enterprise data may include enterprise information, organizational structure, address books, member accounts, permission configurations, login records, feature usage records, resource consumption records, log audit information, input content, output content, device environment, network environment, application environment, security detection results, file operation records, process information, command line operation records, and other information lawfully submitted by enterprise users or required by enterprise users from end users.
3.3When uploading any content, including but not limited to normal input, text, voice/audio, images, or files in other formats provided during feedback or contact with us, please pay special attention to whether such content contains or involves any third-party personal information, confidential information, or other inappropriate information. This includes but is not limited to names, contact details, or other personal identifiers. Before submitting such information, you are responsible for ensuring that all necessary lawful authorization has been obtained to avoid unintentionally disclosing others' privacy or infringing their lawful rights and interests.
3.4Before uploading, managing, collecting, processing, storing, externally providing, or entrusting us to process end users' personal information, enterprise users should fully inform end users in accordance with law of the processing purposes, methods, scope, protection measures, and entrusted processing, and obtain necessary authorization. For sensitive personal information, provision of personal information to other processors, public disclosure of personal information, cross-border provision of personal information, or other matters requiring separate consent by laws and regulations, separate consent should be obtained in accordance with law.
IV. How We Use Cookies and Related Technologies
4.1To ensure normal operation of websites and services, identify login status, save user settings, provide security protection, count visits, and improve service experience, we may use cookies, LocalStorage, device identifiers, log analysis, or similar technologies.
4.2Cookies and related technologies may be used to remember user identities, maintain session status, save preference settings, analyze service access, prevent malicious access, identify abnormal logins, or improve page loading efficiency.
4.3You may manage, refuse, or delete cookies through your browser or system settings. Disabling cookies or similar technologies may affect account login, status maintenance, preference saving, security verification, or normal use of some features.
4.4Information formed through the use of cookies and similar technologies on the DeepWorks website or related services will be processed in accordance with this Guide.
V. How We Use Collected Personal Information
5.1We will use collected information in accordance with this Guide, product descriptions, user authorization, contractual agreements, and laws and regulations under the principles of legality, propriety, necessity, and good faith.
5.2We may use relevant information to provide DeepWorks features to you, including account login, identity verification, model invocation, intelligent conversation, file processing, task execution, remote connection, message notification, enterprise management, resource metering, customer support, troubleshooting, and security assurance.
5.3We may use relevant information to maintain service stability and security, including identity verification, permission control, risk identification, anomaly detection, anti-fraud, log audit, malicious program detection, vulnerability investigation, dispute handling, and compliance retention.
5.4We may use relevant information to improve products and services, including statistics on feature usage, performance metric analysis, interaction process optimization, model effect improvement, error prompt improvement, documentation enhancement, and customer support quality improvement.
5.5Based on your account status, service usage, or subscription settings, we may send you service-related notifications, such as account security, resource consumption, product expiration, feature changes, service maintenance, and important rule updates.
5.6Subject to legal and regulatory requirements and necessary authorization, we may invite you to participate in questionnaires, interviews, product tests, satisfaction surveys, or service experience feedback.
5.7We may conduct statistics, analysis, or summaries of users' use of DeepWorks and form statistical materials, product reports, or business analysis materials that do not identify specific individuals, for internal management, business decision-making, service optimization, or external explanations.
5.8We may send you marketing information related to our products and services, such as feature updates, event invitations, promotional offers, customer research, marketing activities, and product recommendations, by email, SMS, phone, or other means.
5.9If we intend to use personal information for other purposes not directly or reasonably related to the original collection purpose, we will inform you and obtain your consent before use, unless otherwise provided by laws and regulations.
VI. How We Entrust Processing, Share, Transfer, and Publicly Disclose Information
6.1We strictly limit the sharing, transfer, and public disclosure of personal information, follow the principles of legality, propriety, necessity, and minimum scope, and take measures such as encryption, de-identification, access control, contractual constraints, and security assessments to protect information security.
6.2Entrusted processing. To implement DeepWorks-related features, we may entrust suppliers, service providers, or partners to process necessary personal information, such as cloud infrastructure, model services, SMS or email notifications, customer service, data storage, security audit, log analysis, and troubleshooting. We will agree with entrusted parties on processing purposes, periods, methods, personal information types, protection measures, and rights and obligations of both parties, and supervise their processing of personal information in accordance with the agreement.
6.3Third-party models and plugins. If users choose or authorize the use of third-party models, plugins, data sources, web services, or enterprise systems, relevant input content, output content, account information, or task information may be sent to the corresponding third party as needed for the feature. We will prompt relevant processing rules on product pages, feature descriptions, or by other reasonable means. Third-party services configured by users themselves are usually subject to data processing rules separately determined by users and the third party.
6.4Account, authentication, and enterprise management services. To complete account login, enterprise authentication, member management, permission configuration, resource subscription, payment settlement, or security verification, we may share minimum necessary information with identity authentication, enterprise management, payment settlement, SMS/email, electronic signing, or other necessary service providers.
6.5Sharing in accordance with law. We may provide necessary information in response to lawful requests from laws and regulations, judicial authorities, administrative authorities, or other competent authorities.
6.6Enterprise user scenarios. When enterprise users act as personal information processors or data controllers, they may view or process account information, usage records, input and output content, log audit information, or other enterprise data of end users within their management scope for management, audit, security, collaboration, resource statistics, and similar purposes. Enterprise users should perform notification, authorization, rights request response, and security protection obligations in accordance with law.
6.7Transfer. If personal information is transferred due to merger, division, acquisition, asset transfer, business restructuring, bankruptcy liquidation, or similar transactions, we will require the new holder to continue to be bound by this Guide. If processing purposes or methods change substantially, we will notify you and obtain necessary consent again in accordance with law.
6.8Public disclosure. In principle, we will not publicly disclose your personal information. If public disclosure is truly necessary, we will inform you in accordance with law of the purpose, information type, disclosure scope, and possible impact, and obtain your separate consent, unless otherwise provided by laws and regulations.
6.9In the following circumstances, sharing, transfer, or public disclosure of personal information may not require prior consent: where necessary for the conclusion or performance of a contract to which an individual is a party; where necessary to perform statutory duties or obligations; where necessary to respond to public health emergencies or protect the life, health, or property safety of natural persons in emergencies; where personal information disclosed by individuals themselves or otherwise lawfully disclosed is processed within a reasonable scope; or other circumstances provided by laws and regulations.
VII. How We Store Your Personal Information
7.1Personal information collected and generated within the territory of the People's Republic of China will be stored within China, unless otherwise provided by laws and regulations or separately authorized by users. If cross-border provision of personal information is truly necessary for business needs, we will perform security assessment, certification, standard contract, notification, consent, and other obligations in accordance with laws and regulations.
7.2We retain personal information only for the period necessary to achieve the purposes described in this Guide, unless laws and regulations, regulatory requirements, dispute resolution, contract performance, audit compliance, or security assurance require a longer retention period.
7.3After the retention period expires, we will delete or anonymize relevant personal information in accordance with laws and regulations. If immediate deletion is impossible for technical reasons, we will stop processing activities other than storage and necessary security protection measures.
7.4After account cancellation, we will stop providing products or services to that account and delete or anonymize relevant personal information in accordance with laws and regulations. Information that must be retained by law will be properly stored during the statutory retention period.
7.5We may extend the information retention period in the following circumstances: complying with laws and regulations, regulatory requirements, judicial or administrative authority requirements; handling complaints, disputes, controversies, or security incidents; performing relevant service agreements; or protecting the lawful rights and interests of users, us, or others.
VIII. How We Protect Your Personal Information Security
8.1We will take reasonable and feasible security measures to protect personal information against unauthorized access, public disclosure, use, modification, damage, loss, or leakage.
8.2We may use technical and management measures such as encrypted transmission, encrypted storage, access control, permission isolation, identity authentication, log audit, desensitized display, backup recovery, security detection, and vulnerability repair to protect information security.
8.3We establish management systems and operating procedures related to personal information protection, limit the scope of personnel who may access personal information, and require relevant personnel to perform confidentiality obligations.
8.4We attach importance to information security compliance and will continue to improve personal information protection capabilities based on business development, technological changes, and risk conditions.
8.5If a personal information security incident occurs, we will activate emergency plans in accordance with laws and regulations, take remedial measures, and promptly inform you of the basic situation, possible impact, measures taken or to be taken, suggestions for independently preventing and reducing risks, and our contact methods. If individual notification is difficult, we will publish relevant information by announcement or other reasonable means.
8.6To better protect information security, please properly keep your account, password, verification code, access key, device, and enterprise permission configurations, and do not disclose or transfer account credentials to others. Risks caused by users' own improper custody, improper authorization, mistaken operations, or third-party reasons shall be borne by the corresponding responsible party in accordance with law.
IX. How You Manage Your Personal Information
9.1We protect your statutory rights related to personal information. You may query, copy, correct, supplement, delete personal information, withdraw consent, cancel your account, or request explanation of personal information processing rules through product features or the methods listed in "XII. Contact Us".
9.2To protect account security and personal information security, access, modification, deletion, or export of different information may require identity verification, permission verification, or enterprise administrator confirmation. Based on technical implementation, laws and regulations, regulatory requirements, information security, dispute handling, or enterprise management needs, some information may not be immediately accessible, modifiable, or deletable.
9.3After registration, you may complete or modify account information in account settings, personal center, or corresponding feature pages. Some information under enterprise accounts may need to be uniformly maintained by enterprise administrators.
9.4You may manage message subscriptions, notification methods, experience improvement plans, memory features, permission authorization, or other configurable items according to product settings. Necessary notifications related to account security, service use, resource consumption, product expiration, and important rule changes may not be completely disabled.
9.5If personal information processed by us is inaccurate, or if you wish to withdraw authorization, delete information, copy information, or cancel your account and cannot complete it through product pages, you may contact us through the methods listed in this Guide. We will process the request after verifying your identity and respond within fifteen working days or within the period required by laws and regulations.
9.6If you need to cancel your account, you may submit an application through product pages or methods we publish. Before cancellation, we may verify identity, clear account assets, handle unfinished services, settle fees, and confirm dispute status. After cancellation, relevant services and data under the account may not be recoverable. Information required by law to be retained will be deleted or anonymized after the statutory period expires.
9.7If you are an enterprise end user and relevant personal information is processed for purposes and by methods determined by the enterprise user, you may first submit requests for query, correction, deletion, withdrawal of consent, cancellation, or similar matters to your enterprise user or administrator. We will also provide necessary assistance in accordance with laws and regulations, enterprise user instructions, and contractual agreements.
X. Revisions to this Guide
10.1We may revise this Guide based on changes in laws and regulations, product feature adjustments, service model changes, or changes in personal information processing purposes or methods.
10.2If this Guide undergoes major changes, we will notify you through page prompts, pop-ups, announcements, internal messages, emails, or other reasonable means. Major changes include important changes to processing purposes, processing methods, personal information types, sharing recipients, methods for exercising user rights, and contact methods.
10.3After this Guide is updated, if you continue to use DeepWorks and related services, you indicate that you have been informed of and accept the updated content. If you do not agree to the updates, you should stop using the affected related services.
XI. Protection of Minors
11.1We attach importance to the protection of minors' personal information. DeepWorks is mainly intended to provide services to adults and organization users with lawful authorization.
11.2If you are a minor under the age of eighteen, you should read, understand, and use this service under the supervision, guidance, and consent of your guardian.
11.3If you are a child under the age of fourteen, your guardian should carefully read this Guide and applicable rules on protection of minors' personal information before use, and use this service only after the guardian agrees.
11.4If you are the guardian of a minor, please pay attention to whether the minor uses DeepWorks after obtaining authorized consent. If you have questions, complaints, or rights requests regarding the processing of minors' personal information, you may contact us through the methods listed in this Guide.
XII. Contact Us
We have established a person in charge and handling mechanism for personal information protection. If you have any questions, complaints, suggestions, or rights requests regarding this Guide or personal information protection matters, you may contact us by the following method: email: deepworks@deepexi.com. We will review your request as soon as possible and respond within fifteen working days from receipt of the request or within the period required by laws and regulations.