冷气水 · Lengqishui
Privacy Policy / 隐私政策
How the current PTE Core product handles account, recording and learning data.
Publication status / 发布状态
Draft / 准备中 — the marked operational and policy items are not yet finalized. This is not a claim that the native apps are available or ready for store review.
Operator and scope
Operated by LENGQISHUI INC. Registered office: 499 Preston Street, Ottawa, Ontario, K1S 4N7, Canada Support: support@lengqishui.com Privacy/legal: legal@lengqishui.com This notice covers the current website and the app code being prepared for release. Availability and data handling of the final native build must be verified before publication.
Account information
Email registration uses an email address, nickname, password and verification codes. The backend stores password hashes and account/session records. The latest public website check found email/password and email-verification login enabled, with WeChat web sign-in disabled. If enabled later, the optional WeChat integration can provide identifiers (OpenID/UnionID) and nickname/avatar information; the notice must be reviewed for that change. The ordinary user sign-up flow audited here does not ask for a phone number.
Support and privacy correspondence
If you email our support or privacy/legal addresses, Zoho Mail processes your sender address, message content and any attachments as our company mailbox provider. We use this correspondence to respond to your enquiry. Do not send passwords, verification codes or unnecessary sensitive information. Company correspondence is separate from the product service used to deliver sign-in verification emails. TODO — confirm mailbox storage locations, correspondence retention and the handling of privacy requests.
Microphone, recordings and automated feedback
Speaking practice asks for microphone access when recording. A recorded answer can be uploaded for scoring, together with the question/reference content and attempt information. The backend stores the recording file, recognized transcripts, scores and attempt/audit records. Cleanup of temporary scoring files does not remove these stored records. The checked deployment sends audio to our configured speech-scoring service, which uses a locally hosted whisper.cpp model and scoring logic. Local processing on that server is not on-device processing. TODO — confirm secondary use, human review and retention across processor copies before final publication. Do not include sensitive personal information in practice recordings.
Answers, learning records and community content
Practice answers, writing text, scores, progress, review items, saved vocabulary, mock sessions and learning events support study history and feedback. Some guest data and preferences are kept on the device/browser; signing in and using synchronization can associate supported records with an account. Community posts, comments, profile display information and leaderboard entries can be visible to others. Moderation and report records are stored by the service.
Technical data and first-party analytics
The code includes guest identifiers, page and learning events, referring pages/campaign parameters, browser User-Agent and IP-related records. Login IP records can contain raw IP addresses. When a local GeoIP database is configured, IP addresses can be used to infer and store an approximate region/city, latitude/longitude and accuracy radius; this is not GPS permission. These records support service operation, security and usage analysis. No Sentry, Firebase analytics or advertising SDK integration was identified in the audited app code; the final packaged SDK inventory still needs review.
Learning credits and order history
The internal learning-credit store keeps account-linked balances, credit transactions, virtual-item orders and entitlements. The audited flows do not collect payment-card or bank-account details. TODO — reassess this notice and store disclosures before introducing real-money payments.
Storage, retention and deletion
Data is stored in backend databases, server recording storage and device/browser storage as applicable. The code does not define a complete production retention schedule or an end-to-end account deletion service. The checked production backend has not deployed the new deletion-request intake. Deleting a community post can change its status while retaining its content in the database. Clearing browser/app storage does not delete server records. TODO — establish and verify backup handling, retention periods, deletion exceptions and a complete deletion workflow. No fixed deletion deadline or complete erasure promise is made here.
Hosting locations
Production checks on 27 September 2026 located the main website/API, account database and recording storage on Alibaba Cloud in Hangzhou, mainland China, and the speech-scoring and verification-relay services on Tencent Cloud in Shanghai, mainland China. These services therefore process data outside Canada. This does not establish where every other provider or subprocessor keeps its copies.
Service providers and transfers
The deployed service uses Brevo to deliver verification emails and Cloudflare Turnstile for abuse prevention. Requests pass through a relay on the speech-scoring host, which can process recipient addresses and message content, including verification codes, as well as challenge tokens and remote IP addresses. Company support mail uses a separate mailbox provider. WeChat web sign-in is disabled in the checked deployment; its optional integration remains in the code. MaxMind data can be used locally for IP lookup without sending each lookup to MaxMind. TODO — confirm other providers' and subprocessors' locations, contractual terms and applicable international-transfer safeguards before final publication. We do not claim Canadian-only storage.
Controls and contact
You can deny or revoke microphone permission in device/browser settings; recording features then cannot function. You can choose not to upload an answer or post publicly. Support: support@lengqishui.com Privacy/legal: legal@lengqishui.com TODO — establish a monitored process for access, correction and deletion requests and any applicable consent/objection controls. No automated privacy-request service is currently represented as available.
Audience and updates
The planned first native release permits accounts from age 16. Users aged 16–17 will be asked to confirm permission from a parent or guardian. The prepared registration control records an age band and acknowledgements rather than a full date of birth or a parent's identity. This is a self-declaration, not verified parental consent. The control remains disabled while the policy is a draft; existing accounts have not been assigned an age by assumption. TODO — complete the youth privacy and age-assurance assessment, controls for existing accounts, and store audience declarations before enabling this rule. Store age/content ratings are separate from account eligibility. Material changes in data processing require this notice and the store disclosures to be reviewed together.