LingoOK Privacy Policy
> Draft for operational review: [Operator legal name — confirmation required], [registration number — confirmation required], [registered/contact address — confirmation required], and [support/privacy email — confirmation required] must be completed and verified before publication. Manual request handling times remain subject to applicable requirements; no unverified fixed deadline is promised here.
- Effective / last updated: October 29, 2026
- Operator: [Operator legal name — confirmation required]; [registration number — confirmation required]; [registered/contact address — confirmation required]
- Website: https://www.lingook.com
- Contact: [support/privacy email — confirmation required]
- Product: LingoOK — the website https://www.lingook.com and the LingoOK apps for Android and iOS (AI English conversation, reading, dictation, picture description, number dictation and AI tutoring)
This Privacy Policy explains who operates LingoOK, what information we collect (including Google account information used for Sign in with Google), how we use and store it, when we share it, how long we keep it, and how you can access or delete it.
You can delete your account at any time: sign in and go to Account → Delete account to immediately and permanently delete your Google profile data and all learning data. See section 8.1.
By using LingoOK you agree to this policy. If you do not agree, please do not use the service or sign in.
Summary: what we collect and why
| Data | When we collect it | What we use it for | Who else processes it | How long we keep it |
|---|---|---|---|---|
| Google account data: email address, name, profile photo URL, Google account ID | When you choose Sign in with Google | To sign you in, create your account and show your name and photo | Vercel and Neon (hosting and database) only | Until you delete your account |
| Learning records: progress, scores, answers, practice history, preferences | While you learn signed in | To save your progress and adapt lessons to your level | Vercel and Neon | Until you delete your account |
| AI Chat content: your messages, what you choose to tell the AI, your voice while you speak | When you use AI Chat | To answer you and remember the conversation | OpenAI, only to produce the AI's replies and speech recognition | History retention varies by feature; see sections 7 and 8 |
| Membership and payments: plan, renewal and end dates, payment status | When you buy a membership | To give you member features | Stripe (payments) and RevenueCat (membership status). We never see or store card numbers | As long as tax and accounting law requires |
| Usage and technical data: requests, errors, AI conversation minutes, IP address | When you use the service | Security, fixing problems, daily limits | Vercel | A limited operational period |
| Website analytics: pages viewed, device and browser | When you visit the website | Visit statistics | Google Analytics (never linked to your Google sign-in) | Per Google Analytics settings |
Google user data is used only to sign you in and run your account. It is never sold, never used for advertising, never sent to AI providers, and never used to train AI models.
1. Who we are
LingoOK is an AI English conversation and learning service. It provides a voice and text AI chat partner, level-matched reading, listening/dictation, exercises, picture description writing, number dictation, leaderboards, and an AI tutor.
Operator and data controller: LingoOK is operated by [Operator legal name — confirmation required] ("we", "us"); registration number and registered/contact address: [confirmation required]. Contact us by email at [support/privacy email — confirmation required], or through the in-product Feedback widget on https://www.lingook.com. Please mark privacy or data-deletion requests clearly in your message.
This policy applies to the website https://www.lingook.com (all locales, for example /en and /zh) and to the LingoOK mobile apps for Android and iOS. The website and the apps use the same account, the same Sign in with Google, and the same servers, so everything below applies to both.
2. Google Sign-In and Google user data
Signing in is optional. You can browse articles, practice dictation, look up words, and try many features without an account.
If you choose Sign in with Google, we use Google OAuth 2.0 / OpenID Connect with the scopes:
openidemailprofile
2.1 What Google user data we access
From Google we receive only the basic profile information needed to create or recognize your LingoOK account:
- Your Google account email address
- Your display name
- Your profile photo URL (if Google provides one)
- A stable Google user identifier (
sub) used for authentication
We do not request access to your Gmail, Google Drive, Google Contacts, Google Calendar, YouTube, or other Google services. We do not read your emails or files on Google.
2.2 How we use Google user data
We use Google account data only to provide and improve user-facing LingoOK features that you choose:
- Authenticate you and keep you signed in
- Create and maintain your LingoOK user profile
- Save learning progress, scores, practice records, and preferences to your account
- Show your display name and avatar where the product needs identity (for example account area, comments you post, or leaderboard display when applicable)
- Contact you about account or feedback matters when you write to us using that email
- Protect the service (security, abuse prevention, debugging authentication issues)
2.3 What we do not do with Google user data
- We do not sell Google user data
- We do not use Google user data for advertising or ad targeting
- We do not share Google user data with data brokers
- We do not use Google user data to develop, improve or train any AI or machine-learning models, and we do not send it to AI providers
- We do not use Google user data for any purpose other than providing or improving LingoOK's user-facing features described above
- We do not transfer Google user data to third parties except as described in this policy (infrastructure providers that process data on our behalf to run LingoOK)
Limited Use disclosure: LingoOK's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
2.4 Google user data at a glance
| Question | Answer |
|---|---|
| What we access | Your Google account email address, display name, profile photo URL and Google account ID (sub), through the openid, email and profile scopes only. Nothing else in your Google account. |
| How we use it | Only to sign you in, create and show your LingoOK account, and save your learning progress to it. Never for advertising, never sold, and never used to train AI models. |
| Where we store it | In LingoOK's user database (Neon Postgres) and application servers (Vercel), both hosted in Singapore. The profile photo is stored as a link to Google; we do not copy the image. Your session is kept in a signed, HTTP-only cookie. |
| How we protect it | All traffic uses HTTPS (TLS). The database encrypts stored data at rest. Only the LingoOK operator can access production systems, and database credentials are kept in the hosting provider's encrypted environment settings, not in source code. |
| Who we share it with | Only the infrastructure providers that run LingoOK for us (Vercel for hosting, Neon for the database), under their data-processing terms. We do not send your Google profile data to AI providers, advertisers or data brokers. |
| How long we keep it | For as long as your LingoOK account exists. |
| How to delete it | Go to Account → Delete account at https://www.lingook.com/en/account. Your Google profile data and all learning data are deleted immediately and permanently. If you cannot sign in, email [support/privacy email — confirmation required] from your account email to request deletion of your Google profile data, learning records, answers and comments; we review the request and communicate the result. You can also remove LingoOK's access at any time at https://myaccount.google.com/permissions; this stops Google sharing data with us in future. |
3. Other information we collect
3.1 Account and authentication (non-Google)
You may also register or sign in with email and password when that option is enabled. In that case we store your email, a securely hashed password, and profile fields you provide.
3.2 Learning and product data (after sign-in)
When you are signed in, we may store on our servers:
- Reading / lesson progress and completion status
- Dictation attempts, scores, and related practice records
- Exercise answers and grades
- Picture-description writings and AI review results you submit
- Number-dictation session results and adaptive progress
- Learning events / activity logs used for progress and personalization
- Preferences (for example learner level, sharing settings for exercises when you enable them)
- Optional community content you choose to publish (for example article comments or shared tutor questions)
- AI Chat memory: a preferred name, age band, city, first language, coarse work or study background, learning goals and interests you voluntarily provide may form a personal profile and memories for conversation continuity, material recommendations and practice. Profiles and memories should exclude precise addresses, contact details, identity or banking information, named employers or schools, health or financial circumstances, religion, political affiliation, sexual orientation and identifying details about other people. Program filters cannot recognize every expression; please avoid submitting such information in chat. Stored conversation text and profiles are separate records: forgetting a profile fact or memory through the available personal-data controls prevents its old evidence from being used for future personalization and review, but does not erase the original History. Resuming learning accepts newly provided information going forward. Mobile history is stored by session for your own cross-history review, rather than under a universal 200-message limit. Legacy Web chat has a separate recent-message window; New topic on the Web clears that chat window and may retain a short previous-context excerpt for continuity; it does not forget personal information or erase mobile history, profiles or all personal data.
During signed-in realtime voice sessions, a stable, randomly generated account safety identifier may accompany requests to OpenAI for abuse monitoring. This pseudonym is not generated from your email, name, photo or Google account identifier. Its local account mapping is removed when the account is deleted; it is not an anonymous identifier and does not prove that provider-side records have been erased.
3.3 Device / browser storage (local)
Some preferences and temporary learning state stay in your browser (for example via localStorage), such as:
- Selected learner / reading / dictation / tutor level settings
- Local dictation progress checkpoints
- Local tutor chat history for a session context
- Local dictionary lookup cache on the device
These local items are not automatically uploaded as a full dump of your browser storage. Clearing site data in your browser removes them.
3.4 Content you send to AI features
When you use AI tutoring, correction, grading, translation helpers, speech transcription, or similar features, we process the text or audio you submit together with relevant lesson context (for example the current sentence or article excerpt) so the model can respond. That content may be transmitted to our configured model providers (see Third parties).
Voice in AI Chat: when you speak, your recording is sent to our speech provider to turn it into text. If you are signed in, the recording is also saved with that chat message so you can replay it and hear your progress. Recordings are stored privately in our file storage (Vercel Blob, Singapore) under random file names, and only you can play them while signed in. Audio retention differs from text history, and long-term replay is not guaranteed. Server recordings have a separate short-term cleanup mechanism (the program default is 3 days, configurable from 1 to 30 days; actual deletion also depends on cleanup execution). Trimming or clearing legacy Web messages requests deletion of their associated recordings. This does not delete all mobile history recordings; account deletion requests deletion of your saved recordings. When you are not signed in, a recording stays only in the open browser tab. When the AI reads a reply aloud, only the reply text is sent to the speech provider. Your Google profile data is never sent to AI providers.
3.5 Feedback
If you use Feedback, we store your message, the page path, locale, and a reply email. Signed-in users typically use the account email; guests may enter an email.
3.6 Technical and security logs
Servers and hosting providers may process standard technical data such as IP address, browser type, request timestamps, and error diagnostics necessary to operate, secure, and debug the website. We do not use third-party advertising pixels. See 3.8 for website analytics.
3.7 Cookies and session tokens
Authentication uses session cookies / tokens (for example JWT-based session cookies via our auth library) so we can keep you signed in. These are required for account features, not for ads. In the mobile apps, your sign-in token is kept in the device's secure storage (iOS Keychain / Android Keystore).
Necessary session cookies support sign-in and account security, not advertising. The current website also has the analytics cookies described below, so it does not use necessary cookies only.
3.8 Website analytics
The website uses Google Analytics to count visits and see which pages are used (for example pages viewed, approximate location from IP address, device and browser type). Google Analytics sets its own cookies. We do not send your email address, name, Google account ID or learning content to Google Analytics, we do not combine analytics data with your Google Sign-In data, and we do not use it for advertising. You can block these cookies in your browser or use Google's opt-out add-on (https://tools.google.com/dlpage/gaoptout). The mobile apps do not include Google Analytics or any advertising SDK.
The website also stores a first-party visitor identifier (lingook_funnel_visitor) in browser local storage, which is separate from cookies. Selected product events, the visitor identifier, interaction mode and content identifier are sent to our own analytics endpoint; when signed in, the server can associate these events with the account email. These first-party records are distinct from Google Analytics. Clearing site storage removes the browser identifier but does not itself delete server records.
Google lists _ga and _ga_<container-id> as GA4 cookies. Their behavior depends on browser restrictions and Analytics configuration; we have not verified live cookie lifetimes or deployment settings in preparing this draft.
3.9 Mobile app permissions
The apps ask for device permissions only when you use the feature that needs them, and you can refuse or withdraw them in your device settings:
- Microphone — to talk with the AI in voice chat and to record practice answers. Audio is handled as described in 3.4.
- Camera — only when you choose to take a photo to discuss with the AI.
- Photos — only when you pick a photo to discuss with the AI or to set your profile picture. Only the photo you choose is uploaded.
The apps do not access your contacts, location, calendar or other files.
3.10 Membership and payments
When you buy a membership on the website, payment is handled by Stripe. You enter card, Alipay or WeChat Pay details on Stripe's checkout page; LingoOK never receives or stores full card numbers or wallet credentials. We store your plan, its renewal or end date, your Stripe customer ID and payment status, so we can give you member features. RevenueCat receives an anonymous account ID and your membership status so the same membership works on the website and in the apps. Stripe and RevenueCat process this data under their own privacy policies and data-processing terms. We keep payment records as long as tax and accounting law requires.
4. How we use information (summary)
We use collected information to:
- Provide LingoOK’s learning features and sync progress across sessions when you are signed in
- Personalize difficulty / recommendations based on your learning activity
- Operate leaderboards and account-linked displays you opt into by using those features
- Improve reliability, security, and customer support
- Comply with legal obligations when required
We do not sell personal information.
5. Where we store data and how we protect it
- Application data is stored in databases and object storage operated for LingoOK (currently including cloud Postgres and file/blob storage hosted by our infrastructure providers).
- Access to production systems is limited to operators who need it to run the service.
- Passwords (when used) are stored hashed, not in plain text.
- We use HTTPS for traffic to https://www.lingook.com.
- No method of transmission or storage is 100% secure; we take reasonable measures appropriate to a small consumer learning app.
Hosting and processing may occur on servers located outside your country (for example cloud regions used by Vercel, Neon, or similar providers). By using LingoOK you understand your information may be processed in those locations under this policy.
6. Sharing and third parties
We share personal data only as needed to operate LingoOK:
| Party | Role | Typical data |
|---|---|---|
| Optional Sign in with Google | You authorize Google to share name, email, profile photo with us | |
| Hosting / database / storage providers (for example Vercel, Neon, Vercel Blob) | Run the website and store app data | Account and learning records, media files needed for lessons |
| OpenAI (directly or through Vercel AI Gateway) | Generate AI chat and tutor replies, corrections, grades and translations; speech recognition and speech synthesis | Text and voice you submit plus necessary lesson context. Never your Google profile data. Under OpenAI's API terms this data is not used to train their models. |
| Stripe and RevenueCat | Take membership payments; keep membership status in sync between the website and the apps | Plan, dates and payment status; an anonymous account ID for RevenueCat. Card and wallet details stay with Stripe |
| Google Analytics (website only) | Visit statistics | Pages viewed, device/browser type, approximate location; no account or Google Sign-In data |
| Email delivery (for example Resend, when configured) | Send replies to feedback | Feedback content and reply address |
| Public dictionary / content sources | Lookups and study materials | Word queries or public educational content; not sold as your identity profile |
We do not sell your personal information to third parties for their marketing.
We may disclose information if required by law, to protect rights and safety, or in connection with a merger or transfer of the service, in which case this policy or a successor notice will continue to apply or you will be notified.
7. Retention
- Account profile and learning records: kept while your account exists; deleted immediately when you delete your account.
- Chat history and derived information: mobile conversation text and learning reviews are stored by session; profiles, interests and personal memories support future personalization. Forgetting an item invalidates its old evidence, rather than deleting the original conversation. Account deletion removes associated data. Legacy Web chat separately trims to the latest 200 messages; this is not a universal mobile retention limit.
- Recordings: use separate short-term cleanup; retained text or reviews do not guarantee that the original audio remains playable.
- Conversation history and valid learning evidence: retained until you actively delete the relevant data through available controls or delete your account. Forgetting a profile fact prevents reuse of its old evidence without deleting the original History.
- AI diagnostic Prompt records: records do not automatically expire or get deleted after a fixed number of days. Cleanup will be considered when the data volume becomes excessive; capacity thresholds are not yet enabled. Necessary runtime receipts must be preserved before diagnostic text is removed. User-requested deletion and account closure follow their respective rules.
- Feedback: kept as needed to respond and maintain support history.
- Security / server logs: kept for a limited operational period.
- Browser local data: until you clear it.
If you request deletion by emailing [support/privacy email — confirmation required], we review the request and arrange deletion of account-linked personal data, including Google profile data, except where limited records need to be retained for legal, security or abuse-prevention reasons.
8. Your choices and rights
You can:
- Use most learning features without signing in with Google
- Sign out at any time
- Clear this site’s browser local storage in your browser settings
- Adjust sharing preferences in Account settings when those controls are available (for example whether certain exercise answers are public)
- Delete your account yourself at any time under Account → Delete account; this immediately removes your Google profile data and all learning data
- Request access, correction, or deletion of account-linked personal data by emailing [support/privacy email — confirmation required] or sending a privacy request through the Feedback widget on https://www.lingook.com. We review requests and communicate the outcome under applicable requirements.
To delete Google’s authorization for this app, you can also visit your Google Account permissions page and remove LingoOK / the OAuth client access. That stops future Google Sign-In sharing; you may still need to ask us to delete data already stored in LingoOK.
8.1 Deleting your account
You can delete your LingoOK account yourself at any time, without contacting us:
- Sign in to LingoOK and open the Account page (https://www.lingook.com/en/account).
- In the Delete account section at the bottom of the page, click Delete my account.
- Type
DELETEto confirm, then click Permanently delete.
Once you confirm, we immediately and permanently delete all data linked to your account, including:
- The email address, name, profile photo link and account ID received from Google
- Learning progress, scores, points, dictation and exercise records, and your learning profile
- Comments you posted, questions you asked the AI tutor, picture-description answers and feedback messages
- Everything AI Chat remembers about you, your stored AI Chat conversation, and your voice recordings
Deletion cannot be undone. You are signed out, and learning data saved in this browser is cleared. Sessions on other devices end within 5 minutes.
Deleting your account does not remove LingoOK's access from your Google account. To stop Google sharing data with us, also remove LingoOK at https://myaccount.google.com/permissions.
If you cannot sign in, or for admin accounts (which cannot be deleted from the Account page), email [support/privacy email — confirmation required] from your account email. We review the request, arrange the applicable deletion and communicate the outcome.
9. Adults-only service
This release of LingoOK is intended only for adults and does not offer services to minors. Do not use the service if you are a minor. We do not request a date of birth, identity document or guardian details in conversation. If you believe a minor has provided personal data, contact [support/privacy email — confirmation required] so we can investigate and arrange appropriate deletion.
10. International users
LingoOK is offered from infrastructure that may be located in multiple countries. If you access the service from outside the country where servers are located, you consent to transfer and processing as described here.
11. Changes to this policy
When we change this policy in a material way, we will update the Effective / last updated date at the top of this page and of the policy file. For significant changes affecting Google user data use, we will provide additional notice and obtain consent where required before using data in a new way.
Continued use of LingoOK after an update means you acknowledge the revised policy.
12. Contact
Email: [support/privacy email — confirmation required]
Privacy / data requests: email [support/privacy email — confirmation required], or use the Feedback widget on https://www.lingook.com, and clearly state that your message is a privacy request (access, correction, or deletion). We review requests and communicate the outcome under applicable requirements.
Policy URL for Google OAuth verification: https://www.lingook.com/en/privacy
A downloadable / raw markdown copy is also available at https://www.lingook.com/legal/privacy.en.md