Eigenteam Privacy Policy
Introduction and Important Notice
Eigenteam values your personal information and privacy. This Policy explains how we process personal information when we provide the mobile app, connection and management of the Eigenteam AI Band and Eigenteam AI Card, cloud sync, speech-to-text, AI summaries and sales analysis, and CRM, and how you can exercise your rights.
Personal information protection contact email: business@eigenteam.ai
Please read and fully understand this Policy before you log in or use the service, especially the parts highlighted in bold on the rights of people who are recorded, sensitive personal information, third-party services, AI processing, data retention and deletion, and personal information rights. Use the relevant service only after you understand and agree. If you do not agree to this Policy, do not log in or use the corresponding service.
Please note in particular:
- Recording, transcription, and AI analysis may involve personal information about you and about third parties such as customers, colleagues, store staff, and the other party to a call. The content may also include sensitive content such as health, financial accounts, identity information, location trails, and trade secrets. When voice is used for voiceprint recognition or identity verification, voice characteristics are biometric sensitive personal information.
- Your agreement to this Policy does not mean that other people in a recording have agreed. The enterprise customer and the person actually recording must, before recording, tell participants about recording, upload, transcription, and AI analysis, and obtain consent or confirm another lawful basis.
- Information needed for basic features is processed separately from information for optional features. Refusing non-essential information or permissions does not affect features unrelated to that permission. Where sensitive personal information is processed, personal information is provided to another personal information processor, publicly disclosed, or provided across borders, we will give enhanced notice and obtain separate consent as required by law.
- We will not use your recordings, transcripts, prompts, or AI output for general model training, advertising profiles, or other unrelated purposes merely because you agreed to this Policy. If we later need them for optional product improvement, human annotation, or model training, we will explain that clearly, obtain separate consent, and provide a way to opt out.
1. Scope
- This Policy applies to the Eigenteam mobile app, companion Eigenteam AI Band and Eigenteam AI Card devices, cloud services, CRM, AI sales analysis, website, or admin console that we provide.
- Systems provided by the enterprise customer itself, and websites or services independently operated by third parties, are not covered by this Policy. We will make a reasonable effort to prompt you before a redirect. You should read that third party’s privacy rules.
- This Policy does not apply to personal information processing that an enterprise customer carries out independently outside Eigenteam.
2. Roles in Personal Information Processing
2.1 Information Eigenteam processes for its own purposes
For account assignment and identity verification, service security, device binding and after-sales support, billing, customer support, compliance audits, and duties we bear under law, if we decide the purposes and means ourselves, Eigenteam is the personal information processor and is responsible for that processing under this Policy.
2.2 Information whose purposes and means the enterprise customer decides, and which Eigenteam processes on instructions
The enterprise customer usually decides why and how it collects and uses employee information, CRM customer information, sales follow-ups, recordings, transcripts, and sales analysis data. When we provide hosting, sync, transcription, analysis, backup, or technical support on the enterprise customer’s instructions, the enterprise customer is usually the personal information processor and Eigenteam is usually a processor acting on instructions.
We will agree in the enterprise contract or data processing agreement on the purposes, period, methods, types of information, safeguards, rights and duties of both parties, and conditions for onward processing. We process only on lawful, clear instructions. We do not use entrusted data for our own advertising, profiling, or model training without separate consent. When the engagement ends, we return or delete the data as required by law and contract, and do not keep it on our own. We will provide permission settings and access controls appropriate to the service risk, take measures to prevent access beyond authority, and bear liability under law for Eigenteam’s own unauthorized processing or inadequate security measures.
2.3 Responsibilities the enterprise customer bears itself
The enterprise customer must ensure that its purposes and means are lawful, legitimate, and necessary; give notice to employees, customers, and recording participants and establish a lawful basis; configure least privilege and the shortest retention period; respond to individual rights requests; and manage access, export, disclosure, and deletion by its administrators and employees.
2.4 Third-party service providers
Cloud computing, object storage, ASR, and large-model providers process information only to the extent necessary for the relevant feature. When they act as our processors, they are bound by the processing agreement. If a third party decides the purposes and means itself, we will, before providing the information, tell you its name, contact details, purposes, methods, and types of information, and obtain separate consent as required by law. The current version does not integrate SDKs for advertising, user profiling, or third-party analytics. If we later add a third-party SDK or component that processes personal information, we will update the relevant disclosure in a timely way as required by law.
3. How We Collect and Use Personal Information
The table below lists business feature, type of information, purpose and method, necessity, recipient, period, and user control. Information marked “necessary” is required for that feature. It does not mean the whole app requires it. If you do not use the feature, you do not need to provide it.
| Business feature | Type of information | Purpose and method | Necessity | Permission / source | Recipient | Retention | User control |
|---|---|---|---|---|---|---|---|
| Account assignment, login, and account security | Account and password assigned by the enterprise or by us; enterprise and organization role; account ID, login time, login IP, and unusual-login records | Assign a managed account, verify identity, complete login, and prevent account takeover | Necessary for the account service | Entered by the enterprise / Eigenteam; entered by the user; network | Eigenteam | For the life of the account. Account deletion is completed within fifteen business days after identity and permission checks. Related data is handled under Section 7 | Request access, correction, deactivation, or deletion |
| Enterprise organization and member management | Enterprise name, organization ID, department, position, role, account identifier, member status, and permission records | Create the organization, manage members, assign roles, and record permission changes | Necessary for the enterprise service | Entered by the enterprise / administrator, or generated by the system | Eigenteam; the enterprise customer and authorized administrators. An administrator may not view a user’s recordings, transcripts, or AI analysis without the recording user’s authorization. The user may authorize viewing, download, export, or deletion orally or by contract | One year by default. The enterprise contract may set a different period. General audit logs are kept for three months by default, unless the law requires longer | Ask an administrator to change organization information. Recording authorization can be withdrawn. Individual rights can also be raised with us directly |
| CRM customer management | Customer name, company, title, mobile number, and notes entered by an enterprise member or provided by the enterprise customer | Create customer records, record the sales process, and collaborate on sales | Necessary for the corresponding CRM feature. The enterprise customer should enter only information needed for sales management | Provided by an enterprise member or the enterprise customer; network | Eigenteam as a processor on instructions; authorized people in the enterprise | One year by default. The enterprise contract may set a different period. After the cooperation ends, a default three-month window applies, after which data is returned, deleted, or anonymized as required by law and contract | Access, correct, or delete in CRM. A recorded customer may make a request to the enterprise customer or to us |
| Scan or SN device binding | QR code content, device serial number (SN), binding code, device model, bound account / organization, and bind and unbind time | Identify the device, check ownership, prevent mistaken binding, and support after-sales and asset management | Necessary to bind a device | Camera scan or manual entry; network | Eigenteam; enterprise device administrators | One year by default. The enterprise contract may set a different period. Binding information that is no longer necessary is deleted after unbinding | Enter the SN manually instead of using the camera. Unbind in device management |
| Bluetooth search, connection, and management | Eigenteam AI Band or Eigenteam AI Card name, SN, MAC address, Bluetooth connection information, and device status | Discover nearby devices, connect, show device status, and send control commands | Necessary for the hardware connection feature | Bluetooth | The app and the Eigenteam AI Band or Eigenteam AI Card. Eigenteam receives the SN, device name, MAC address, and status information needed for account binding and device management | Local temporary connection information is no longer used after the connection ends. Cloud device-management information is kept for one year by default. The enterprise contract may set a different period | Turn off the Bluetooth permission or unbind. After it is turned off, devices cannot be searched, connected, or managed |
| Start / stop recording | Control commands, recording status returned by the device, start / stop time, and device identifier | The app sends control commands over Bluetooth to a bound Eigenteam AI Band or Eigenteam AI Card. Recording is performed by the device | Necessary for recording control | Bluetooth. The phone microphone is not used | Eigenteam AI Band or Eigenteam AI Card and the app | Processing stops after the local connection session ends | Operate or turn off the device to stop recording. Turn off the Bluetooth permission. Unbind the device |
| View, upload, sync, and delete recordings | Audio files; file name, time, duration, size, format, checksum, upload progress, failure reason, and associated device / customer / employee | Under the current product design, after the user starts an upload, the file is sent over Wi-Fi or a cellular network to the enterprise customer’s growth system. If upload fails, the user taps to retry | Necessary for cloud recording, transcription, and analysis | Bluetooth transfer from the Eigenteam AI Band or Eigenteam AI Card, file-storage access, and network | Eigenteam; the enterprise customer’s growth system; Alibaba Cloud OSS in the Hangzhou region | Recording master files and related business data are kept for one year by default. The enterprise contract may set a different period. After the cooperation ends, they are handled as agreed when the default three-month window ends | Cancel an upload in the app, or tap to retry after a failure. After deletion is started, we begin deletion or anonymization under the system where the data resides, the enterprise customer’s control of the data, and the rules in Section 7 |
| Cloud storage and download | Audio, transcripts, summaries, analysis results, CRM links, and download records | Provide cross-device access, enterprise collaboration, backup and restore, and export in the enterprise customer’s growth system | Necessary for cloud features | Network | Eigenteam; the enterprise customer; Alibaba Cloud infrastructure in the Hangzhou region; enterprise personnel authorized orally or by contract by the recording user | Recording master files and related business data are kept for one year by default. The enterprise contract may set a different period. After the cooperation ends, a default three-month window applies, after which data is returned, deleted, or anonymized as required by law and contract | View, download, delete, or contact the enterprise administrator or us |
| ASR transcription | Audio the user chooses to process and the corresponding task identifier; the transcript that is returned | Convert speech to text | Necessary for the transcription feature | The user taps transcribe, or the user turns on automatic processing; network | Eigenteam currently uses Alibaba Cloud speech recognition | Transcripts kept by Eigenteam are kept for one year by default. The provider processes them only as needed to provide ASR and secure the service. The period for call records, security logs, or temporary cache depends on the service configuration, contract, and applicable law | Do not tap transcribe. Turn off automatic processing. Delete the transcript and source recording |
| AI summary, Q&A, sales analysis, and review | Transcript, prompts, and customer or opportunity context needed for the feature the user chooses; AI output, summaries, analysis, tags, and suggestions | Generate summaries, answers, sales suggestions, reviews, and CRM follow-up content | Necessary for the corresponding AI feature | The user taps the AI feature, or the user turns on automatic processing; network | Eigenteam currently uses DeepSeek, Kimi, and Tongyi Qianwen | Business inputs and outputs kept by Eigenteam are kept for one year by default. Model providers process them only as needed to provide the capability and secure the service. The period for call records, security logs, or temporary cache depends on the service configuration, contract, and applicable law | Do not tap the feature. Turn off automatic processing. Delete inputs and outputs. Give feedback or corrections on results |
| Device maintenance | SN, device model, firmware / hardware version, time, configuration, update status, error codes, and device status | Unbind, calibrate time, reset, update firmware, idle auto-shutdown, and diagnose faults | Necessary for the corresponding maintenance feature | Bluetooth, network, and system files | Eigenteam and its Alibaba Cloud infrastructure in the Hangzhou region | Device configuration is kept for one year by default. General maintenance and after-sales logs are kept for three months by default | Do not use the maintenance feature. Configure optional features as prompted on the page |
| Support, feedback, and rights requests | Account, contact details, description of the issue, communication records, and files or logs the user chooses to provide, plus identity-check materials | Locate issues and handle complaints, after-sales requests, and individual rights requests | Necessary to handle the request. Attachments are chosen by the user | Submitted by the user through the contact email or another public channel | Eigenteam | Three months by default, unless a legal duty or dispute handling requires longer | You do not have to provide non-essential attachments. After the request is handled, you may ask for deletion of content that the law allows to be deleted |
| Operational security and fault diagnosis | IP address, network type, phone brand and model, operating system and version, app version, error, crash, and performance logs, request time, and account ID | Protect connection and account security, troubleshoot faults, and keep the service stable and compatible across versions | Only fields necessary for security and stability are processed. The current version does not collect Android ID, OAID, IDFV, advertising identifiers, location, or the app list for this feature | Generated automatically by the app / system; network | Eigenteam. The current version does not use third-party advertising, profiling, or analytics SDKs | Network operation logs are kept for at least six months as required by law. Other general diagnostic logs are kept for three months by default | You may ask us to delete diagnostic information that the law allows to be deleted. Necessary security logs cannot be turned off separately |
3.1 Sources of information
We obtain information from: information you submit directly; information the enterprise customer or an administrator provides to create the organization and perform employment or business-management duties; CRM entries or recordings entered by other enterprise members; a bound Eigenteam AI Band or Eigenteam AI Card; information the app and servers generate to the extent necessary for operational security; and third-party systems authorized by you or the enterprise customer.
If we indirectly obtain your personal information from a third party, we will require the provider to explain the source and lawful basis, and will tell you when the law requires it. The enterprise customer must not upload data obtained by theft, unlawful purchase, unauthorized scraping, or other unlawful means.
3.2 Information about third parties in recordings
- Before recording starts, the enterprise customer and the person actually recording must explain, in a way the other person can understand and perceive: who is recording, the purpose, whether it will be uploaded to the cloud, whether it will be transcribed or analyzed by AI, who in the enterprise may access it, the retention period, and how to make a rights request.
- A user’s upload of a recording only means that, where they already have the required authorization or another lawful basis, they instruct us to process that recording to provide the storage, sync, transcription, summary, analysis, and CRM services they chose. It does not mean recording participants have consented, and it does not authorize us to use the data for model training, advertising, sale, or other unrelated purposes.
- Recording is performed by the Eigenteam AI Band or Eigenteam AI Card, which indicates recording status with its indicator light. The app only sends control commands to the device. When connected in the foreground, it can display the device status it receives. It does not provide a recording-status prompt after it moves to the background or the screen locks. If a participant refuses or asks to stop, the person recording must operate or turn off the Eigenteam AI Band or Eigenteam AI Card directly and confirm with the device indicator light that recording has stopped.
- If a recording participant makes a request to us and the enterprise customer decides how the related data is processed, we will check identity and clues, forward the request to the enterprise customer, and provide necessary help. If we decide the processing ourselves, we will respond directly as required by law.
- Recordings that involve private conversations, minors, medical information, finance, identity information, whereabouts, trade secrets, or other high-risk content should be subject to stricter necessity review, permissions, and retention periods. The enterprise customer should support a reasonable alternative when a participant refuses recording.
3.3 Optional model improvement or human review
We do not currently use users’ audio, transcripts, prompts, CRM context, or AI output to train Eigenteam’s own general-purpose models, unless we give a clear notice in the future and obtain the authorization required by law. When we select and configure model services, we will prefer enterprise or API configurations that do not use enterprise business data to train independent models, and will use contracts, product settings, permission management, and other reasonable measures to limit service providers from using data beyond the entrusted purpose. If a service provider, processing purpose, processing method, or type of information changes, we will update the relevant disclosure as required by law. Where consent or separate consent is required, we will obtain it before processing.
3.4 Network access before the first consent
Before you make a privacy choice on first launch, the app makes only the minimum network communication needed to display this Policy and the Terms of Service and to protect page and transmission security. The minimum access logs generated in that process, such as IP address and request time, are used only for transmission and security, not for user profiling or operations analysis. At this stage we do not start personal information processing for login, advertising or user profiling, recording upload, CRM sync, Bluetooth search or connection, ASR, or AI analysis, and we do not request camera, Bluetooth, or file-storage permissions. If you choose not to agree, the app does not start that non-essential business processing.
4. System Permission List
For the current version, Eigenteam requests necessary permissions such as camera, Bluetooth / nearby devices, and file access when the corresponding feature is triggered. Network access is used for login, upload, cloud processing, and other online services. We request and use permissions only to the extent necessary for the feature. Refusing a non-essential permission does not affect features unrelated to it. Network access is usually a basic app capability and does not show an ordinary runtime permission dialog.
| System permission | Use and information | Whether necessary, and the effect of refusal | Trigger and control |
|---|---|---|---|
| Camera | Scan the Eigenteam AI Band or Eigenteam AI Card QR code and read the device-binding information in it | Necessary for scan-to-bind. If refused, scanning is unavailable, but you can still bind by entering the SN manually | Requested when the user taps scan-to-bind. Can be turned off in system settings |
| Bluetooth / nearby devices | Search for and connect to the Eigenteam AI Band or Eigenteam AI Card, and transfer device status, control commands, and recording files | Necessary when connecting a device. If refused, devices cannot be searched, connected, or managed. Unrelated features such as CRM are not affected | Requested when the user enters device connection. Can be turned off in system settings |
| File storage | When the user starts a recording upload, read the file to be uploaded and save upload parts or retry information that is needed | Necessary for file upload. If refused, recording files cannot be uploaded. Features that do not need file access are not affected | Requested when the user selects and uploads a file. Can be turned off in system settings |
| Network access | Connect to Eigenteam services, the enterprise customer’s growth system, Alibaba Cloud in the Hangzhou region, ASR, and model services | Necessary for login, upload, transcription, analysis, and online services. After the network is disconnected, only local features the product expressly supports can be used | Connects when login, upload, and other online features are used. The user can disconnect through system network settings |
The current version does not request or use the phone microphone, location, photo / media library, notifications, contacts, phone, SMS, calendar, app list, advertising tracking, or sensor permissions. Recording in the app is performed by the Eigenteam AI Band or Eigenteam AI Card, not the phone microphone. If a later version truly needs a new permission, we will first assess necessity, update this Policy and the permission list, and request it as required by law when the corresponding feature is used.
The usual path to turn a permission off is “System Settings — Apps — Eigenteam — Permissions.” Names differ slightly by system. Turning a permission off does not affect processing that was lawfully completed before it was turned off. You may also request deletion of information already created. Network access can be managed in system network settings.
5. Sensitive Personal Information and Separate Consent
- We treat recordings and transcripts as high-risk content and apply enhanced protection. Whether they are sensitive personal information as defined by law depends on the specific content and use. Voiceprint characteristics, identity information, financial accounts, health, location trails, and personal information of minors under 14 are, or may be, sensitive personal information.
- For processing that requires separate consent by law, such as processing sensitive personal information, providing personal information to another personal information processor, public disclosure, or cross-border provision, we will give enhanced notice and obtain separate consent before processing. For technical processing by a service provider acting only on instructions from Eigenteam or the enterprise customer, we will carry out entrusted processing, necessary notice, and security duties according to the actual legal relationship. The product may still ask for confirmation before upload, transcription, or AI analysis.
- Separate consent must not be bundled with account assignment, login, basic CRM, or unrelated permissions. Users may refuse or withdraw. Withdrawal affects only the corresponding feature and does not affect lawful processing based on consent before withdrawal.
- The enterprise customer must itself complete enhanced notice and lawful-basis management for employees, customers, and recording participants. We will provide product mechanisms to support this, but a technical prompt does not replace the enterprise customer’s legal duties.
6. Entrusted Processing, Sharing, Transfer, and Public Disclosure
6.1 Entrusted processing and third-party recipient list
We provide service providers with the minimum information, only for clear, reasonable, and necessary purposes, and use contracts, service configuration, and permission management to limit their purposes, data scope, security measures, and onward processing. Cloud capabilities and data storage for the enterprise customer’s growth system currently use Alibaba Cloud services in the Hangzhou region. The current version does not integrate SDKs for advertising, user profiling, or third-party analytics.
| Category / feature | Service / recipient | Information received | Purpose and method | Location, period, and training | Privacy rules |
|---|---|---|---|---|---|
| Cloud computing, databases, and object storage | Alibaba Cloud services in the Hangzhou region | Accounts, organizations, CRM, recordings, transcripts, AI results, and logs needed for secure operation | Provide computing, databases, object storage, backup, and security services for the enterprise customer’s growth system | Main business data is deployed in Hangzhou, mainland China. Eigenteam business data is kept under Section 7. The provider’s technical logs and temporary data are handled under the service configuration, contract, and applicable law | Alibaba Cloud Legal Statement and Privacy Policy |
| ASR | Alibaba Cloud speech recognition | Audio selected by the user and the corresponding task identifier; the service returns the transcript | Speech-to-text | The provider processes data only as needed to provide speech recognition and secure the service. We do not authorize it to use enterprise business data for its own advertising profiles or unauthorized model training. Call records, security logs, and temporary cache are handled under the service configuration, contract, and applicable law | Alibaba Cloud Legal Statement and Privacy Policy |
| Large models | DeepSeek, Kimi, and Tongyi Qianwen model services | Transcript, prompts, customer or opportunity context, and the corresponding task identifier needed for the feature the user chooses; the service returns model output | Summaries, Q&A, sales analysis, and reviews | The provider processes data only as needed to provide model capability and secure the service. We prefer enterprise / API configurations that do not use customer business data for independent training, and we limit independent use by contract and configuration. Call records, security logs, and temporary cache are handled under the service configuration, contract, and applicable law | DeepSeek Privacy Policy, Kimi Privacy Policy, Alibaba Cloud Legal Statement and Privacy Policy |
The table in this section is the current third-party information-sharing list. If a provider, the information received, the purpose, the region, or the retention period changes, we will update this section. We will not replace our own accurate disclosure with “please refer to the third party’s policy.”
6.2 Sharing
Except in the following cases, we do not provide your personal information to other personal information processors:
- We have told you the recipient’s name and contact details, the purposes, methods, and types of information, and have obtained separate consent;
- Laws and regulations, litigation or dispute resolution, or a lawful request from a competent authority require it;
- The enterprise customer shows enterprise business data to its members within lawful permissions. An administrator may not view a user’s recordings, transcripts, or AI analysis without the recording user’s authorization. The user may authorize the administrator, orally or by contract, to view them, and may also authorize download, export, or deletion. The enterprise customer and administrators must keep proof of the content, scope, and validity period of the authorization, and must keep necessary records of viewing, download, export, deletion, and withdrawal.
6.3 Transfer
We do not sell personal information. If a merger, division, reorganization, asset transfer, dissolution, or bankruptcy involves a transfer of personal information, we will tell you the recipient’s name and contact details and require the recipient to continue to follow this Policy. If the recipient changes the original purposes or methods, it must obtain consent again.
6.4 Public disclosure
We do not publicly disclose personal information in principle. If disclosure is truly necessary, we will explain the purpose, type of information, necessity, and impact, and obtain separate consent, unless the law provides otherwise.
7. Storage Location, Retention, and Deletion
7.1 Storage location and cross-border transfer
Under the current deployment, Eigenteam’s main business data storage and core cloud processing are in mainland China. Cloud databases, object storage, and backups currently use Alibaba Cloud in the Hangzhou region. We do not proactively provide personal information collected or generated in mainland China to parties outside mainland China.
If a later change in service architecture, suppliers, or business involves cross-border provision of personal information, we will, before it actually happens, complete a personal information protection impact assessment, tell you about the overseas recipient and how to exercise rights, obtain separate consent, and meet security assessment, standard contract, certification, or other applicable conditions, and we will update this Policy.
7.2 Retention periods
We keep information only for the shortest time necessary for the purpose. Recording master files, transcripts, summaries, AI analysis, and other business data are kept for one year by default. The enterprise customer may agree a different period in the contract. After the enterprise service ends, a default three-month window applies for data export and migration, unless the contract says otherwise. When that window ends, we return, delete, or anonymize the data as required by law and contract. Backups, temporary objects, upload parts, and general service logs rotate on a three-month cycle by default. Network operation logs are kept for at least six months as required by law.
| Data category | Ordinary retention | Handling after deletion or account closure | Exceptions |
|---|---|---|---|
| Account and organization information | One year by default. The enterprise contract may set a different period | Account deletion is completed within fifteen business days, and data in online business systems that is no longer necessary or has no lawful basis is deleted or anonymized. Backups follow the rotation mechanism | Legal duties and dispute handling |
| CRM and sales records | One year by default. The enterprise contract may set a different period | After the enterprise contract ends, a default three-month window applies, then deletion or anonymization | Records the enterprise must keep by law |
| Device binding and maintenance records | One year by default. General maintenance logs are kept for three months by default | Information that is no longer necessary is deleted after unbinding or account deletion. Backups are cleared within the three-month rotation period | After-sales, product quality, and dispute handling |
| Recordings cached on the device or in the app | Recordings on the device are managed by the user or enterprise customer. Temporary cache created by the app for transfer is kept for at most three months by default | After the user completes deletion, handling follows device connection status, product features, and the cache mechanism. If it cannot be handled immediately, it is handled when the device reconnects or when the relevant period ends | Legal preservation and dispute handling |
| Cloud recordings | Recording master files are kept for one year by default. The enterprise contract may set a different period | After deletion is started, online primary storage and direct derived data that is no longer necessary are deleted or anonymized. After the post-cooperation window ends, they are handled as agreed. Backups are cleared by the rotation mechanism | Legal preservation and dispute handling |
| Temporary ASR audio and transcripts | Transcripts kept by Eigenteam are business data and are kept for one year by default. The provider’s call records, security logs, or temporary cache follow the service configuration, contract, and applicable law | Delete transcripts and related tasks within Eigenteam’s control that are no longer necessary, and send corresponding instructions to the provider as the contract and service capability allow | Service security, legal duties, and dispute handling |
| AI inputs and outputs | Business inputs and outputs kept by Eigenteam are kept for one year by default. The enterprise contract may set a different period. The model provider’s call records, security logs, or temporary cache follow the service configuration, contract, and applicable law | Delete inputs, outputs, and related tasks within Eigenteam’s control that are no longer necessary, and send corresponding instructions to the provider as the contract and service capability allow | Service security, legal duties, and dispute handling |
| Network operation logs | At least six months as required by law | Deleted or anonymized when the period ends | Where the law requires otherwise |
| Crash, support, and general audit logs | Three months by default | Deleted or anonymized when the period ends | Dispute handling, or where a legal duty requires longer, is excluded |
7.3 Deletion
- We will delete or anonymize data on our own initiative when the retention period ends, the purpose has been achieved or cannot be achieved, you withdraw consent and there is no other lawful basis, you delete your account, the service stops, or the processing violates law or the agreement.
- Data that cannot be deleted immediately because of backup rotation, security logs, legal retention duties, or technical limits will no longer be used for ordinary business processing. It will be processed only as necessary for legal duties, security protection, and similar purposes, and will be deleted or anonymized when the relevant retention period ends.
- After a user starts deletion and completes the corresponding action, we will start deletion or anonymization of recordings, transcripts, summaries, AI analysis results, and related business data that no longer have a lawful basis or are no longer necessary, according to product features, device connection status, and the data-processing relationship. Data in online business systems will be handled within a reasonable period. For data controlled by the enterprise customer, we will follow its lawful instructions and the parties’ agreement, while protecting the rights individuals have under law.
8. Your Personal Information Rights
8.1 Access, correction, supplementation, and copies
You may access or correct content you are allowed to access on the account, CRM, recording, and analysis pages in the app, or request access, correction, supplementation, or a copy of personal information at business@eigenteam.ai.
8.2 Deletion
You may use the delete function on the relevant recording, transcript, AI result, or CRM data page, or make a request at business@eigenteam.ai. Deletion requests for data we process on the enterprise’s instructions are usually decided by the enterprise customer, and we will help. If the enterprise customer refuses, we will ask it to explain the legal basis. That does not remove our responsibility for our own processing.
8.3 Withdrawal of consent and turning off permissions
You may withdraw the relevant authorization or request deletion at business@eigenteam.ai, and you may turn off camera, Bluetooth, and file-storage permissions in system settings, or manage network access. Withdrawal does not affect lawful processing based on consent before withdrawal. Turning off a permission only makes the corresponding feature unavailable.
8.4 Account deletion
Eigenteam accounts are assigned by the enterprise or by us in the backend or on H5. The app does not currently let individuals apply for an account themselves. You may tap “Request account deletion” in the app to open an email to business@eigenteam.ai, or ask the enterprise administrator to disable, reclaim, or delete the account. After the necessary identity and permission checks, we will complete account deletion within fifteen business days and, based on the nature of the data, the enterprise customer’s control of the data, and applicable law, delete or anonymize related personal information in online business systems that no longer needs to be kept or no longer has a lawful basis, and tell you the result. Data that must continue to be kept by law, and data that cannot be deleted immediately because of backup rotation or similar technical reasons, will not be processed except for legal duties, security protection, and similar necessary purposes, and will be deleted or anonymized when the relevant period ends. Conditions for deletion must not be unnecessarily stricter than the conditions for assigning the account.
After an employee leaves the enterprise or deletes the account, that person no longer accesses, downloads, or exports enterprise data. Enterprise business data created while performing work duties is still managed by the enterprise customer in accordance with law, but the natural person still has statutory rights over personal information in that data that relates to them, and may make a request at business@eigenteam.ai.
8.5 Restricting or refusing automated decision-making
If an AI score or analysis is used to make a decision that has a significant effect on an employee or customer, you have the right to request an explanation and the right to refuse a decision made solely by automated decision-making. Eigenteam’s AI output should not be the sole basis for performance evaluation, dismissal, credit, pricing, or other significant decisions. If the enterprise customer enables leaderboards, employee scoring, automatic alerts, or automatic writing into CRM, it should set up human review, objection, and correction mechanisms.
8.6 How we respond, and exceptions
- When you submit a request through the contact details in this Policy, please state the account, enterprise, relevant recording or customer clue, and the specific request. For security, we check only the information necessary to handle the request. We do not ask for identity documents unrelated to the request.
- We will complete the check and respond within fifteen business days after the necessary identity checks. If the matter is complex or the law provides otherwise, we will explain the reason and the expected time. Reasonable requests are in principle free of charge.
- We may refuse or limit a response, and explain the reason and remedies, where the law says a response is not required, the request would seriously harm another person’s lawful rights, trade secrets are involved, or identity cannot be verified.
- If you are a recording participant but do not have an Eigenteam account, you may still make a request through the contact details in this Policy. We will ask only for the minimum clues needed to locate the record, and will handle it together with the relevant enterprise customer.
9. How We Protect Personal Information
- We will establish mechanisms for data classification, least privilege, identity authentication, access auditing, vulnerability and supply-chain management, backup and recovery, employee confidentiality, and security-incident response, and will take technical and organizational measures appropriate to the processing risk.
- We will take reasonable measures such as identity verification, access control, protection in transit and at rest, log auditing, backup and recovery, and security-incident response, based on the nature of the personal information and the processing risk.
- We will periodically audit app dependencies, third-party services, permission use, and where data goes, and will carry out personal information protection impact assessments for high-risk processing.
- The internet and device environment are not absolutely secure. If a leak, alteration, or loss occurs or may occur, we will take remedial measures immediately, report to the competent authority as required by law, and notify affected individuals by push, SMS, email, phone, or announcement. If it is difficult to notify people one by one, we will publish a notice in a reasonable and effective way.
10. Personal Information of Minors
- Eigenteam is for enterprise sales teams and does not provide account services to minors under 18. Enterprise customers should not assign accounts to minors.
- If a recording happens to include a minor’s information, the enterprise customer and the person actually recording should process it only where there is a lawful basis and it is truly necessary. Personal information of a minor under 14 is sensitive personal information and requires consent from a parent or other guardian, and special rules apply.
- If you believe we have improperly processed a minor’s information, please contact us. After we verify it, we will stop processing, delete it, or take other necessary measures.
11. AI Services and Labels for Generated or Synthetic Content
- Transcripts, summaries, scores, and suggestions are generated by algorithms and may misrecognize, omit, be biased, or invent content. Please check them manually before using them for customer communication, contracts, performance, HR, or other important decisions.
- We currently use DeepSeek, Kimi, and Tongyi Qianwen. We will carry out algorithm filing, generative AI service filing, or registration duties that apply to us. A model provider’s filing does not replace duties that Eigenteam must perform under law.
- For AI-generated content that falls within rules requiring labels for generated or synthetic content, we will take labeling measures appropriate to the content type, how it is provided, and applicable law. For text output such as AI summaries, Q&A, sales analysis, sales reviews, and AI-generated CRM follow-up content, we will place a clear “AI-generated” or “AI-assisted” label, with reasonable type size and contrast, in an easy-to-notice place near the title, at the start, or at the end of the result page or content card, and may also use an icon. When copy, download, or export is provided, we will keep the corresponding text label in the exported content as required by applicable laws, regulations, and mandatory national standards, and, where the file format supports it and the law applies, add an implicit generated-content label in the file metadata. When users publish AI-generated content to the public that the law requires to be labeled, they must keep or add the required labels, and must not maliciously remove, alter, forge, or hide labels that the law requires.
12. Policy Updates
- We will update this Policy when features, data processing, service providers, or the law change, and will mark the version, publication date, and effective date.
- For material changes to purposes, methods, types of personal information, recipients, cross-border transfer, or user rights, we will explain them prominently, such as by an in-app dialog. Where consent or separate consent is required by law, we will obtain it again. We will not treat continued use as consent.
- You may view and save this Policy, and the personal information collection list, third-party information-sharing list, and system permission list it contains, at any time through the agreement entry in the app or the public page for this Policy.
13. Contact Us
Personal information protection contact: Eigenteam personal information protection contact
Contact email: business@eigenteam.ai
We will reply within fifteen business days after the necessary identity checks. If you are not satisfied with the result, you may complain to the cyberspace, telecommunications, public security, or market-regulation authorities as provided by law, or bring a lawsuit in a people’s court with jurisdiction.
14. Related Public Lists
To reduce extra page jumps and keep versions consistent, Section 3 of this Policy is also the Eigenteam Personal Information Collection List, Section 4 is also the Eigenteam System Permission List, and Section 6 is also the Eigenteam Third-Party Information Sharing List. Section 2 explains the personal information processing roles of Eigenteam, the enterprise customer, and third-party service providers.