This policy applies to the “Trade Translate – WhatsApp two-way auto translation” Chrome / Edge browser extension and its built-in features (including the trade documents feature).
Publisher: AiAppWorks · Effective date: October 9, 2026 · Last updated: November 11, 2026
Contact email: thomas.wang.86.021@gmail.com · 中文版
Trade Translate (the “extension”) is a WhatsApp Web translation extension built for foreign-trade workflows. It also includes auxiliary features such as quick replies, contact language labels, and trade documents (quotations / trade paperwork).
This policy explains in detail how the extension collects, uses, stores, and shares user data during your use, including the categories of data, the purposes of processing, retention periods, and the specific third-party recipients. “User data” means any data obtained from you or your usage environment through the extension, including message content generated in WhatsApp Web.
The extension does not use user data for advertising, does not sell or rent user data, and does not engage in cross-site tracking unrelated to the extension’s features.
| Item | Description |
|---|---|
| Data | The chat message text to be translated (source text), plus the language direction (source language, target language). |
| How it is obtained | The extension reads message text from the WhatsApp Web page. Triggers include:
|
| Transmitted? | Yes. The message text being translated is sent with the translation request to the third-party translation providers listed in Section 5, solely to produce the translation. |
| Local cache | Translation results and a text-hash-based translation memory are stored locally in chrome.storage.local (up to about 50,000 entries) to avoid re-translating the same text. This cache is not uploaded to our servers and is deleted when you clear browser data or uninstall the extension. |
| Purpose | Solely to generate translations; not used for advertising, marketing, or profiling. |
Below each machine-translated message you can optionally click the “Refine with AI” button to have a large language model polish the translation. This feature is entirely manual — nothing is uploaded unless you click the button.
| Item | Description |
|---|---|
| Data | The source text of the message being refined, the language direction, the chat type (private/group), and up to 4 recent context messages collected at the moment you click (the last ≤200 characters of each, with neutral speaker labels such as [me] / [peer] / group-member names). Context is used only to help the model resolve references; only the final message is refined. |
| How it is obtained | Collected only at the moment you manually click the “Refine with AI” button; not read continuously in the background and never triggered automatically. |
| Transmitted? | Yes. The above is sent to our server trade.aiappworks.cn and forwarded by us to the third-party large-language-model provider listed in Section 5, solely to produce the refined translation. |
| Sign-in required? | Yes. The AI refinement feature requires sign-in (it incurs real inference cost); if you are not signed in, clicking the button guides you to sign in and no request is sent. |
| Local cache | The refined translation is stored locally in chrome.storage.local (keyed by language + source text, up to about 2,000 entries) so it can be shown again when you scroll back; this cache is not uploaded to our servers. |
| Purpose | Solely to produce the refined translation for this message; not used for advertising, marketing, or profiling. |
If you report a poor translation, we upload: the source text, the translated text, the language direction, the translation engine used, your feedback reason and additional notes, whether the report is anonymous, an anonymous client identifier (client_id), the extension version, and the submission time.
trade.aiappworks.cn;| Item | Description |
|---|---|
| Sign in with Google | When you sign in with a Google account, the extension requests the openid, email, and profile scopes to obtain your Google email address, name, and avatar. The Google token is then sent to our server trade.aiappworks.cn for verification, and we issue a sign-in token. |
| Email + password sign-in | The trade documents feature supports email + password registration and sign-in. We store your email address and an irreversible hash of your password (never the plaintext password). |
| What we store | Our servers store: account ID, email, name, avatar, role, workspace (tenant), and creation time. Sign-in tokens (JWT) are valid for 7 days. |
To implement the daily translation quota and usage display, the extension records daily translation counts and character counts (split between incoming and outgoing messages) locally, and synchronizes them to our server trade.aiappworks.cn when you are signed in. Only aggregate numbers (counts, characters, date) are uploaded — no message text.
When you use the built-in trade documents (quotations, packing lists, and similar paperwork) feature, the data you actively enter or upload is stored on our server trade.aiappworks.cn, including:
This data is stored per workspace (tenant) and used only to provide the feature to you. You can delete it at any time within the feature, or contact us to delete your account and the related data.
To understand feature usage, diagnose issues, and improve the product, the extension reports usage events through Google Analytics 4 (GA4) Measurement Protocol. Reported data includes:
client_id (generated on first use and stored locally);user_id for signed-in users (only attached after sign-in);ip_override with each report so Google can derive approximate country/city location).Events are queued locally (up to 200) and sent in batches every 5 minutes, when the page goes to the background, or when the extension popup is opened. We do not use this analytics to obtain your cross-site browsing history, and we do not use it for advertising.
To support the geolocation described above, the extension queries the following public services for your current public IP (the result is cached locally for 24 hours):
https://icanhazip.com (Cloudflare)https://api.bigdatacloud.net/data/client-ip (BigDataCloud)https://www.cloudflare.com/cdn-cgi/trace (Cloudflare)These queries obtain only the IP address itself; no chat content is uploaded to them.
To perform translation, detect languages, and render labels, the extension reads information visible on the current WhatsApp Web page, such as: message text and timestamps, chat titles, chat type (private/group), the phone number or country dial code associated with a chat, and current language settings.
When you create a custom tab and add chats to it, the following data is synced to our servers (only after sign-in):
Purpose: restore your tabs across devices under the same account and WhatsApp number. When you are not signed in, this data stays on your device only. We do not upload the message bodies of those chats.
When you create a scheduled reminder, the following data is synced to our servers (only after sign-in):
When a reminder is due, the extension shows a notification on your device through Chrome’s system notification API; notification content does not pass through our push servers. Completed reminders are kept until you delete them. When you are not signed in, reminders stay on your device only.
To prevent someone from clearing extension data, pretending to be a new install, and repeatedly claiming free quota, the extension reads the currently signed-in WhatsApp number, computes a SHA-256 fingerprint on your device (first 32 hex characters), and reports it together with usage statistics.
Our servers then apply an HMAC-SHA256 salt and store only the salted fingerprint; we do not store your WhatsApp phone number in plaintext, nor the client-side raw hash, and the salted fingerprint cannot be reversed into the phone number. It is used for anti-abuse statistics, quota risk control, and a cross-device translation cache: translations of identical messages under the same WhatsApp account are cached under this fingerprint and reused for 30 days, so translating the same sentence on another device does not call the AI again or consume quota twice. The cache is scoped to your own WhatsApp account only and is never shared across users. It is not used for advertising or profiling.
The following data is stored in the extension storage of your browser; except for the synced data described in Sections 2.10–2.12, it is not uploaded to our servers:
Clearing browser data, clearing the extension’s data in the browser’s extension management page, or uninstalling the extension deletes all of the above local data.
The “Data Sync & Backup” page in the extension settings contains an Upload contact info switch, off by default. It requires you to be signed in; when you turn it on, the extension does the following:
| Item | Description |
|---|---|
| Data |
|
| How it is obtained | When you turn on the switch, the extension reads your WhatsApp Web chat list (private chats and groups) locally and uploads the entries in batches. Afterwards, contact info you edit in WhatsApp chats (country / language / currency / timezone overrides, and the CRM profile fields such as name, company, birthday, and notes) is also synced to our servers. |
| Transmitted? | Yes. Uploaded to our server trade.aiappworks.cn, so your contacts appear in the “My Customers” page and are restored when you sign in on another device. |
| Sign-in required? | Yes. The switch is disabled until you sign in. |
| Purpose | Display and cross-device sync of your customer list; it is not used for advertising, marketing, or profiling. |
| How to stop / delete | Turn the switch off at any time (uploading stops immediately; already-uploaded data is retained until you ask us to delete it). To delete your uploaded contact data, email thomas.wang.86.021@gmail.com. |
We do not use user data for advertising, behaviorally targeted advertising, data sales, or analytics unrelated to the extension’s features.
| Location | Data stored |
|---|---|
Your browser’s chrome.storage.local | All local settings and caches listed in Section 2.13 |
Our server trade.aiappworks.cn | Account information, translation usage statistics, translation feedback, trade documents data, custom tabs and scheduled reminders (including related chat identifiers), the salt-hashed WhatsApp account fingerprint, and uploaded contact info (private-chat names/phone numbers and group names/member counts) |
| Third-party providers’ servers | Message text in translation requests (Microsoft / Google); source text and context in AI refinement requests (third-party LLM provider, forwarded via our servers); analytics events (Google Analytics) |
| Data | Retention |
|---|---|
| Translation feedback (source and translated text, etc.) | Deleted automatically 7 days after submission; withdrawable at any time |
| Account information (email, name, avatar) | Kept until you close your account or ask us to delete it |
| Translation usage statistics | Kept until account closure; only daily totals of counts and characters |
| Trade documents data | Kept until you delete it in the feature or ask us to delete your account |
| AI refinement request logs (source, translation, languages, context, latency, status) | Stored in the ai_translate_logs table on our servers for diagnostics and statistics; contact us to delete |
| Custom tabs and scheduled reminders (including completed history) | Kept until you delete them in the feature or ask us to delete your account |
| Uploaded contact info (private-chat names/phone numbers, group names/member counts) | Kept until you ask us to delete it or close your account; turning the switch off stops further uploads |
| Salt-hashed WhatsApp account fingerprint | Retained with usage statistics for anti-abuse analysis and translation-cache attribution only |
| Cross-device translation cache (hashed source key and translation, isolated per salted fingerprint) | Automatically deleted after 30 days |
| Local settings and caches | Kept until you clear browser data or uninstall the extension |
| Analytics events | Queued locally (max 200) and removed after sending; retention on Google’s side follows their service settings |
For how translation providers process and retain the message text sent to them, please refer to their privacy policies listed in Section 5.
We do not sell or rent user data and do not share it with advertisers. To provide the extension’s features, data is shared with the following recipients:
| Recipient | Data shared | Purpose | Privacy policy |
|---|---|---|---|
| Microsoft Corporation (Edge translation endpoint edge.microsoft.com) |
Message text to be translated; source/target languages | Producing translations (primary engine) | Microsoft Privacy Statement |
| Google LLC ( translate-pa.googleapis.com, translate.googleapis.com) |
Message text to be translated; source/target languages | Producing translations (fallback engines) | Google Privacy Policy |
| Google LLC (Google Analytics 4, www.google-analytics.com) |
Analytics events and parameters, client_id, user_id after sign-in, public IP, version, market | Usage analytics | Google Privacy Policy |
| Google LLC (Google Sign-In) |
Google authorization token (used to obtain email, name, avatar) | Account sign-in and identity verification | Google Privacy Policy |
| Third-party large-language-model provider (OpenAI-compatible large-model APIs, forwarded via trade.aiappworks.cn; may change in the future — this table will be updated) |
Message source text in AI refinement requests, up to 4 context messages (with speaker labels), language direction, chat type | Producing the refined translation for the “Refine with AI” feature (only when the user manually clicks) | The specific provider’s official privacy policy applies; contact us if you need the current provider list |
| Cloudflare / BigDataCloud ( icanhazip.com, cloudflare.com, api.bigdatacloud.net) |
Only an IP lookup request | Obtaining the public IP for analytics geolocation | Cloudflare, BigDataCloud |
AiAppWorks (extension publisher)trade.aiappworks.cn |
Account information, translation usage statistics, translation feedback (including source and translated text), trade documents data, custom tabs and scheduled reminders (with related chat identifiers), the salt-hashed WhatsApp account fingerprint, and uploaded contact info (private-chat names/phone numbers and group names/member counts) | Providing sign-in, quotas, feedback handling, the trade documents feature, tab/reminder sync, anti-abuse analytics, and the “My Customers” contact sync | This policy |
| WhatsApp / Meta Platforms | None. Translated text is sent by you within the WhatsApp page; the extension does not upload any data to Meta | — | — |
Besides the cases listed above, we disclose data only when: (a) you consent; (b) required by law, regulation, or a lawful request from a judicial or administrative authority; or (c) necessary to protect the legitimate rights of users, the publisher, or the public.
No method of transmission or storage is completely secure, but we take reasonable technical and organizational measures to protect your data.
The extension is not directed at children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us at the email below and we will delete it promptly.
We may update this policy from time to time. For material changes, we will post the latest version on this page and update the “Last updated” date, and where necessary we will surface a notice in the extension. Please review this page periodically.
If you have any questions, comments, or requests about this privacy policy, our data practices, or your data rights, please contact us:
We will respond as soon as we can after receiving your request.