Public beta notice
Wordex accounts and ticket services are enabled for public beta. The operating entity, actual service providers, processing regions, and fixed retention periods will continue to be added before the related processing begins.
1. Scope
This policy applies to the Wordex website, Microsoft Word and WPS Office add-ins, and support and ticket services operated by Wordex.
If you choose a third-party AI service or use a deployment supplied by your organization, that party may also process data under its own terms. Wordex shows the document scope before it is sent.
2. Data we process
Wordex separates data by use case instead of calling everything usage data.
Complete a document task
Your instruction and the selection, necessary paragraphs, or full document you authorize; model responses, edit suggestions, and before-and-after content.
Used to generate, locate, apply, and undo requested edits.
Operate and diagnose
Wordex version, operating system, Word or WPS host, feature state, latency, error codes, character or token counts, and action outcomes.
Used to maintain reliability, investigate issues, and understand whether features work.
Support and communications
Sender email, ticket type, issue description, diagnostics you choose to attach, and support replies.
Used to answer questions, track tickets, and handle privacy or security requests.
Account and security
Name, email, verification state, password hash, sessions, and the relationship between an account and its tickets.
Used to sign users in, protect accounts, restore access, and continue ticket history across pages. Wordex does not store plaintext passwords.
Local settings
Language, appearance, document-scope preference, selected AI service, and connection configuration may remain on the current device.
API keys and passwords are not product improvement data and are never attached to tickets or analytics events.
The current website
The current website has no website analytics or advertising tracker. When you open the support page through the same-origin service and submit a ticket, the ticket backend stores the issue, selected diagnostics, and later replies. Ticket submission remains disabled when the static file is opened directly. The public website provides email-and-password accounts, email verification, account-owned tickets, and a role-protected staff console.
3. How we use data
- Provide the service: understand tasks, generate suggestions, and perform document actions you confirm.
- Maintain reliability: verify locate and write outcomes, recover failed states, and diagnose compatibility issues.
- Improve Wordex: evaluate quality, performance, and feature use while the global improvement setting is on.
- Provide support: handle email, tickets, data rights requests, and security reports.
- Protect the service: detect abuse, secure the service, and meet applicable legal obligations.
Wordex does not sell personal data or use document content to build advertising profiles.
4. Product improvement data and the global setting
Participate in product improvement is enabled by default in account settings and controls all optional improvement collection. You can turn it off without repeated per-task prompts. Registration requires agreement to the Terms and Privacy Policy; the version and acceptance time are recorded.
When on, improvement data may include sampled instructions, relevant document excerpts, model responses, and before-and-after content used to evaluate suggestion quality. Turning it off stops future optional improvement collection without affecting core document features.
Failure diagnostics remain enabled independently of this setting and may include task instructions, relevant excerpts, model requests and responses, errors, versions, timings and usage. Diagnostic records are not automatically reused for product improvement. This setting does not affect processing required to complete the current document task or data you intentionally submit in a support ticket, privacy request, or security report. Those submissions are used only to provide the requested support, honor data rights, and protect the service, and are not automatically reused as product improvement samples.
Regardless of the setting, improvement data must not include passwords, API keys, unrelated clipboard content, full local paths, or other documents not read for the current task.
5. AI services, processors, and disclosure
To complete a task, Wordex sends the instruction and document scope you authorize to the currently selected AI service. Different services may have different processing regions, retention rules, and terms.
Wordex uses Langfuse Cloud in Japan (Tokyo) for server-side task traces: failure diagnostics and, when product improvement is enabled, evaluation of successful tasks. Records may contain task instructions, relevant document excerpts, model inputs and outputs, usage, timing, and verification results, and are transmitted to Japan. Credentials and local paths are filtered before export. Content capture is capped at 2 MiB per request and may be truncated. Access is restricted to authorized project members.
Outside instructed service providers, Wordex discloses relevant data only when required by law, necessary to protect users and the service, or required for a legitimate corporate transaction or service transfer.
6. Retention and deletion
Retention depends on the data type, purpose, user settings, security needs, and legal obligations. Wordex keeps data only for as long as needed for a defined purpose.
Task traces are retained for 30 days. Wordex checks for expired records hourly and submits deletion requests to Langfuse, retries failures, and records processing status. Platform deletion is asynchronous, so expiry and actual removal are separated by processing delay. This is a Wordex cleanup mechanism, not automatic deletion provided by the free plan's access window. Turning off product improvement stops optional content capture for subsequent successful tasks but does not immediately delete existing records. To request earlier deletion, submit the task request ID through support for verification and processing.
The server uses pseudonymous identifiers to associate requests with an account and document task; account email addresses and names are not used as tracing user identifiers. Test and production traffic are measured separately. Traces do not automatically become evaluation datasets; production examples require separate selection, redaction, and review before evaluation use.
Closing an account removes credentials and sessions and unlinks existing tickets from the account. Unlinking does not bypass the support-data retention, privacy-request, or security-investigation process.
7. Your controls and rights
Depending on applicable law, you may request access, a copy, correction, completion, or deletion of personal data managed by Wordex, withdraw relevant consent, restrict processing, or close an account.
You can turn off product improvement data in Wordex settings without affecting locate, apply, undo, or other core features. Submit privacy requests through the support page or email support@wordex.cn. We will verify the relationship between the requester and the data before acting.
8. Security
The public account service uses salted password hashes, HttpOnly session cookies, email verification, same-origin checks, rate limits, staff roles, and access auditing. It operates over HTTPS with real mail delivery, separate secrets, database backups, and a rollback-capable release process. No internet or email transmission is perfectly secure. Do not paste passwords, API keys, or complete confidential documents into ordinary support tickets.
9. Children
Wordex is not directed to children. Minors should use it only with permission and guidance from a parent, guardian, or their organization. Contact us if you believe a child supplied information that Wordex should not process.
10. Processing regions and international transfers
AI and cloud providers may process data outside your region. Before release, Wordex will identify processing regions based on the final deployment and use any notice, consent, contractual, or other transfer mechanism required by applicable law.
11. Changes to this policy
If data categories, purposes, providers, regions, or retention periods change materially, we will update this page and date and provide an in-product notice or another appropriate reminder.