1. Qui sommes-nous
Responsable du traitement des informations personnelles : (), code d'identification sociale unifié .
Pour toute question relative à la protection des informations personnelles, contactez . La même adresse permet de joindre la personne responsable de la protection des informations personnelles.
La présente politique couvre le site web AI WorkDeck, l'application de bureau, les compléments Office et les services associés. Elle existe en chinois et en anglais ; en cas de divergence, la version chinoise prévaut.
2. Ce que nous collectons
Nous collectons selon le principe du « strict nécessaire ». Le tableau précise ce que nous collectons, pourquoi, et sur quelle base.
| Contexte | Information | Finalité | Base |
|---|---|---|---|
| Inscription | Nom d'utilisateur, adresse e-mail, mot de passe, nom affiché, biographie (facultatif) | Create and identify your account, account recovery, public profile | Necessary to enter into and perform the contract |
| Staying signed in | Session token (in the awd_session cookie) | Maintain your session | Necessary to perform the contract |
| Password storage | Salted scrypt hash only | Verify your password | Necessary to perform the contract |
| Top-ups and payments | Order number, WeChat Pay transaction ID, payer WeChat openid, amount, status, timestamps | Take payment, reconcile, handle refunds and disputes | Contract + legal obligation (tax and bookkeeping) |
| Wallet and transactions | Balance, ledger entries, purchases, entitlements, creator earnings | Accounting, entitlement checks, settlement | Necessary to perform the contract |
| Account keys | SHA-256 hash and prefix only; no plaintext retained | Authenticate the desktop application | Necessary to perform the contract |
| AI credit | Runtime key issued by the upstream model provider (stored encrypted), quota limit and usage | Provision and meter your AI credit | Nécessaire à l'exécution du contrat |
| Soumissions sur la Plaza | La Skill ou le plugin que vous soumettez et votre identité d'auteur | Examen, publication, distribution, règlement | Nécessaire à l'exécution du contrat |
| Télémétrie de l'application de bureau | Identifiant d'installation aléatoire (UUID), version de l'application, noms d'événements sur liste blanche, une clé de séquence de conversation, un petit ensemble d'attributs non sensibles | Mesurer l'activité et l'utilisation des fonctionnalités, diagnostiquer les plantages | Votre consentement (peut être désactivé) |
| Services externes provenant de la plateforme | Le contenu requis par chaque appel (l'image à reconnaître, une requête de recherche, un nom d'entreprise, un ticker, un terme de recherche, l'audio d'une réunion), ainsi qu'une entrée de registre ne contenant aucun contenu (service, quantité, montant, horodatage) | Appeler le fournisseur en votre nom et mesurer l'utilisation | Nécessaire à l'exécution du contrat (votre appel constitue la demande) |
| Journaux du serveur | Horodatage, chemin de la requête, code d'état, adresse IP | Sécurité, dépannage, atténuation des attaques | Maintenance de sécurité raisonnablement nécessaire + obligation légale |
À propos de la télémétrie : l'adresse IP d'une requête de télémétrie est utilisée en mémoire uniquement pour la limitation de débit et n'est jamais écrite dans la base de données. Rien n'enregistre de lien entre l'identifiant d'installation aléatoire et votre compte, nous ne pouvons donc pas retracer la télémétrie jusqu'à une personne.
3. Ce que nous ne collectons pas
Les déclarations ci-dessous concernant les documents et les conversations AI portent sur l'utilisation locale de l'application de bureau. Le module complémentaire Office/WPS traite les documents et les conversations via notre backend hébergé, comme expliqué dans les clauses 6 et 8. Hormis cela, nous ne collectons pas activement les éléments suivants :
- Vos documents, dossiers ou fichiers de projet et leur contenu — l'application de bureau est d'abord locale et ceux-ci restent sur votre appareil. Lorsque vous confiez un contenu spécifique à un service externe spécifique (une image pour la reconnaissance de texte, un enregistrement pour la transcription) : nous transmettons alors au fournisseur la partie requise par l'appel. À l'exception de l'audio de réunion conservé brièvement, nous n'en retenons rien (voir les clauses 6 et 8) ;
- Vos conversations AI sur l'application de bureau — l'application de bureau communique directement avec le fournisseur du modèle ; le traitement hébergé et la rétention pour le module complémentaire Office/WPS sont traités séparément dans les clauses 6 et 8 ;
- Les informations personnelles sensibles telles que les numéros de téléphone, les numéros d'identification, les images faciales ou les empreintes digitales ;
- La localisation, les contacts, les journaux d'appels, les messages ou les bibliothèques photo ;
- Votre navigation en dehors de ce service — nous n'utilisons aucun SDK tiers d'analyse ou de publicité.
Nous n'utilisons aucun de vos contenus pour entraîner des modèles et nous ne vendons pas d'informations personnelles.
5. Comment nous l'utilisons
- Exploitation du service : identification des comptes, vérification des droits, règlement des frais, livraison de ce que vous avez acheté ;
- Sécurité : détection des connexions anormales et des abus, limitation du débit des requêtes, atténuation des attaques, diagnostic des pannes ;
- Amélioration du produit : statistiques agrégées issues de la télémétrie anonyme indiquant quelles fonctionnalités sont utilisées et où les utilisateurs abandonnent ;
- Obligations légales : conservation des registres exigés par les règles fiscales, comptables et de cybersécurité ;
- Communication avec vous : changements de service, incidents de sécurité, modifications des conditions.
Nous n'utilisons pas les informations à d'autres fins. Si nous avions un jour besoin de le faire, nous vous demanderions votre consentement séparément. Nous ne pratiquons pas de prise de décision automatisée et n'utilisons pas les informations personnelles à des fins de messagerie ciblée ou de tarification différenciée.
6. Divulgation et tiers
Destinataires des requêtes IA du module complémentaire. Les requêtes officielles du module complémentaire atteignent le backend cloud d'AI WorkDeck, puis OpenRouter, puis le fournisseur d'inférence desservant le modèle sélectionné. Les développeurs de modèles disponibles incluent DeepSeek, Z.ai, Moonshot AI, Alibaba/Qwen, Anthropic, Google, OpenAI et xAI. Le développeur d'un modèle et son hébergeur d'inférence peuvent différer selon le routage. Les requêtes incluent la question en cours, l'historique de conversation nécessaire, le document actuel et les références sélectionnées par l'utilisateur. OpenRouter et chaque fournisseur d'inférence ont leurs propres politiques de conservation, d'entraînement et de lieu de traitement ; notre règle de traitement transitoire ne garantit pas une rétention nulle chez les tiers. Consultez la liste des fournisseurs OpenRouter (https://openrouter.ai/providers/) et la politique de confidentialité d'OpenRouter (https://openrouter.ai/privacy/).
Nous ne communiquons pas vos informations personnelles à des tiers, sauf dans les cas suivants :
| Destinataire | Information | Purpose | Location |
|---|---|---|---|
| Tenpay Payment Technology Co., Ltd. (WeChat Pay) | Order number, amount, item description | Collect payment, refunds, reconciliation | Mainland China |
| OpenRouter, Inc. | Content you send to the AI; the quota key issued for you | Route model calls, meter usage | United States |
| GitHub, Inc. | Network request data when downloading installers | Host installers and open-source code | United States |
| Alibaba Cloud Computing Ltd. | Server and network-level technical data | Hosting and network acceleration | Mainland China + Singapore node |
| Alibaba Cloud (Tingwu) | Your meeting audio and its transcript | Speech transcription and speaker separation | Mainland China |
| Alibaba Cloud (OCR) | The image you submit for recognition | Image text recognition | Mainland China |
| Bocha (web search) | Your search query | Return web search results | Mainland China |
| Qichacha | The company name or unified social credit code you look up | Return company registry data | Mainland China |
| Tushare | The ticker and fields you query | Return securities and financial data | Mainland China |
| PKULaw | Your statute and case law search term | Return statute and case law results | Mainland China |
How the six platform-sourced services flow. The last six rows are the vendors behind the "platform-sourced" tier: we buy from them on your behalf, so you need no key of your own, and the content each call requires is relayed to the vendor through our servers and metered against your balance. All six are inside mainland China, so this tier involves no cross-border transfer. We do not log, store or train on what we relay; the sole exception is meeting audio, which is held briefly in our object storage so the transcription service can read it and is deleted once that finishes (see clause 8). Any of them can be switched, under Settings → Platform Services in the desktop app, to your own key (the app then talks to that vendor directly, bypassing us) or turned off entirely.
Where AI content actually goes deserves a note. The direct desktop connection described below does not apply to the Office/WPS add-in, which uses the hosted route set out in this clause. When you use the platform AI channel in the desktop application, your content goes directly from your machine to OpenRouter and never passes through our servers — we only issue the quota key and cannot see your conversations. When you use the website's "AI-assisted Skill drafting", the brief you type is relayed to OpenRouter by our server. Either way, the content leaves mainland China.
We may also disclose information where the law requires: cooperating with judicial or administrative authorities, where necessary to protect the public interest or someone's vital interests, or where you have made the information public yourself. In a merger, division or transfer of assets we will transfer personal information along with the business, telling you the recipient's name and contact details beforehand; the recipient must continue to honour this policy or seek your consent afresh.
7. Transfers outside mainland China
Given the architecture described above, your information is transferred outside mainland China in the following cases:
- Content sent through the platform AI channel, the Office/WPS add-in or the website's AI-assisted Skill drafting goes to OpenRouter, Inc. in the United States for inference and metering;
- Downloading a desktop installer sends your request to GitHub, Inc. in the United States;
- Visitors outside mainland China are served by a cache node in Singapore, which fetches from the origin server in Beijing.
The six platform-sourced services do not leave the country. The vendors behind text recognition, web search, company registry data, securities and financial data, statute and case law search and meeting transcription are all inside mainland China (see clause 6). Content in that tier never leaves the mainland, and no separate cross-border consent is required for it. The three cases listed above are the complete set of transfers.
AI content need not leave the country. The desktop application lets you configure your own model provider, including mainland providers and fully local models; once you do, AI content no longer passes through OpenRouter. Installers are currently distributed only via GitHub, which cannot be avoided.
As required by the Personal Information Protection Law, we tell you separately the name and contact details of each overseas recipient, the purpose and method of processing, the categories of information involved and how to exercise your rights against that recipient, and we obtain your separate consent. You may withdraw that consent at any time; we will then stop the corresponding transfer, though the related features will no longer work.
8. How long we keep it
Add-in document and conversation retention. Inline document bodies and raw tool arguments/results are used for the current turn and transient memory caches, not stored in the request queue or conversation history. The add-in does not automatically create durable conversation summaries. Queued input bodies expire after at most 30 minutes and may be evicted earlier or lost on restart; a new upload is then required. User messages, AI replies and reasoning remain as conversation history until the user deletes the conversation, with no separate automatic expiry. This includes document text pasted by the user or quoted by the AI. Conversation deletion also removes queue requests and derived summaries and clears document caches; billing usage records remain. Copies already mirrored to a desktop project follow that project's rules and are not remotely erased by deleting the cloud conversation. Earlier versions stored inline bodies in the queue and tool excerpts and summaries in conversation storage. This update removes historical inline bodies from the live request queue. It also removes raw tool excerpts and derived summaries from conversations still identifiable as Office/WPS add-in conversations through their request-source records. Historical conversations without those source records cannot be reliably classified and are not covered by this Office-specific cleanup. Operational backups and material already sent to third parties are separate; this is not a promise of retrospective erasure of every copy.
| Category | Retention |
|---|---|
| Account information | While the account exists; deleted or anonymised within 30 days of closure |
| Session tokens | 30 days, then expire automatically |
| Account key hashes | Deleted on revocation or account closure |
| Orders, ledger and invoicing records | At least 10 years from completion of the transaction (Article 29 of the Detailed Rules for the Implementation of the Tax Collection and Administration Law); closing your account does not shorten this |
| Plaza submissions | Deleted within 90 days of removal; copies already distributed are unaffected |
| Content relayed for platform-sourced calls | Not retained. It passes through our servers only while that call is being made |
| Meeting audio files | Deleted by the program as soon as transcription finishes or the task fails; a 24-hour lifecycle rule on the object storage clears anything missed. The transcript is not kept on our side once returned to the desktop app |
| Anonymous telemetry | 24 months, then deleted on a rolling basis |
| Server logs | 6 months (Article 21 of the Cybersecurity Law requires no less than 6 months) |
Beyond these periods we delete or anonymise. Where the law requires longer, the law governs.
9. How we protect it
- In transit: HTTPS is enforced site-wide;
- Passwords: stored as salted scrypt hashes — we cannot recover your original password;
- Account keys: only the hash and prefix are stored; the plaintext is shown to you once at generation and then exists nowhere in our systems;
- Model keys: stored encrypted;
- Access control: production access is limited to those who need it;
- Durability: financial data is written transactionally and backed up regularly.
No system is perfectly secure. If personal information is leaked, altered or lost in a way that may harm you, we will take remedial action immediately and notify you and the competent authorities as the law requires.
10. Your rights
Under the Personal Information Protection Law you have the following rights over the personal information we handle:
- Access and copy — find out what we hold about you and obtain a copy;
- Correct and supplement — have inaccurate or incomplete information fixed; account details can also be edited yourself;
- Delete — where the purpose is fulfilled, you withdraw consent, or we have processed unlawfully;
- Portability — have your information transferred to another handler you designate, where it meets the conditions set by the national cyberspace authority;
- Withdraw consent — for anything processed on the basis of consent, such as telemetry and cross-border transfers;
- Restrict or object — ask us to limit or refuse particular processing;
- Explanation — ask us to explain this policy and our processing rules;
- Close your account — at any time, after which we handle your information as set out in clause 8.
How to exercise them: edit your details and revoke account keys yourself in your account; for anything else, write to identifying your account and what you want. We may ask you to verify your identity first. We respond within fifteen working days, and will explain if a complex request needs longer.
A close relative of a deceased user may exercise rights of access, copying, correction and deletion over that user's relevant personal information, unless the user arranged otherwise during their lifetime.
11. Minors
The Service is aimed at professionals and is not offered to children under 14. We do not knowingly collect children's personal information. If we find we have collected it without prior guardian consent, we will delete it promptly.
Guardians who become aware of such a case can reach us at .
12. Changes to this policy
We may revise this policy. For substantive changes to purposes, methods or categories of information, we will notify you by website announcement or email before they take effect, and will seek fresh consent where the law requires it.
Earlier versions are available on request by email.
13. Contact and complaints
For any question, comment or complaint about this policy or our handling of personal information, write to . We reply within fifteen working days.
If you believe our processing has harmed your rights and our reply does not resolve it, you may also complain to the local cyberspace, telecommunications, public security or market regulation authorities, or pursue the dispute resolution route set out in the Terms of Service.
