LinguaLayer Privacy Policy.

This policy describes how LinguaLayer, operated by scq, handles data in the LinguaLayer Chrome extension, website, optional account synchronization, and Pro subscription service. The core extension can be used without creating an account.

Privacy questions and data requests can be sent to hjyshjys@gmail.com.

After you explicitly enable a site, LinguaLayer reads eligible visible page text in browser memory to match vocabulary and render the learning layer. Form fields, editable content, code blocks, navigation, headers, and footers are excluded. The text is processed on your device and is not sent to LinguaLayer, an AI provider, or any other third party. By default, it is not retained after processing and is not made available for human review. If you explicitly choose Save article, LinguaLayer keeps the article title, sanitized site origin and path, and short contexts surrounding up to 20 LinguaLayer expressions in local Chrome storage so you can return to the article and review those expressions.

Enabled website origins are stored only in Chrome extension storage to remember where you activated the extension and to manage Chrome permissions. LinguaLayer does not automatically create a browsing-history log or store full page URLs. A saved article address excludes usernames, passwords, query parameters, and fragments. Enabled origins, saved articles, page URLs, and page text are never included in cloud synchronization.

LinguaLayer stores the following data in chrome.storage.local on your device:

• Learning direction, languages, levels, goals, intensity, daily goal, Chinese script, pinyin, activation, and pronunciation preferences.
• Enabled website origins and granted-access state.
• Expression text, language, meaning, pronunciation, first/last seen times, review due time, seen count, and learning status.
• For articles you explicitly save: article title, sanitized site origin and path, save/update times, and short contexts for up to 20 LinguaLayer expressions. Saved article addresses exclude query parameters and fragments.
• Account, synchronization, entitlement, and cached vocabulary-pack status.

This data powers personalization, progress, offline vocabulary, and permission controls. It remains on the device until you use Delete learning data, clear extension storage, or uninstall LinguaLayer. Pronunciation uses the browser's speech-synthesis capability; LinguaLayer does not record microphone audio.

If you choose to sign in, Clerk provides LinguaLayer with a Clerk user identifier, verified email address, optional display name and profile image, and authentication session state. LinguaLayer uses the session token only to authenticate account, synchronization, entitlement, billing, and vocabulary-pack requests.

Signed-in synchronization sends your learning profile and expression progress described above to LinguaLayer so it can be restored in another signed-in Chrome profile. Synced records are associated with your Clerk user identifier and stored in LinguaLayer's PostgreSQL database on its Tencent Cloud server. Page text, enabled origins, saved article records, browsing history, and page URLs are expressly excluded.

Pro pack downloads send the authenticated account request and requested pack identifier. LinguaLayer returns inert vocabulary JSON and stores entitlement-check timestamps locally. No article content or article address is sent with a pack request.

When you start Pro checkout, LinguaLayer sends Creem your account email, LinguaLayer account identifier, selected plan, and checkout metadata needed to create and link the subscription. Creem collects and processes payment method, billing, tax, and transaction information on its checkout page. LinguaLayer does not receive or store a complete card number, security code, or payment credential.

Creem returns customer, subscription, product, checkout, and order identifiers; subscription status and billing period dates; cancellation state; and relevant refund or dispute state. LinguaLayer stores those fields to grant Pro access, prevent duplicate processing, support cancellation and billing management, and respond to payment issues. Only the event identifier, event type, processing status, and processing timestamps are retained for Webhook auditing; the complete Creem Webhook body is not retained.

Like most Internet services, the LinguaLayer server receives limited request data such as IP address, request time, requested LinguaLayer path, response status, and browser user-agent. This is used only to deliver the service, diagnose failures, prevent abuse, and protect accounts. Extension API requests do not contain the URL or text of the article you are reading.

LinguaLayer does not use advertising SDKs, cross-site analytics, fingerprinting, data brokers, or remote code in the extension. User data is not used for personalized advertising, credit decisions, or unrelated profiling.

Data is disclosed only as necessary to the following recipients:

• Clerk processes sign-in, account identity, sessions, and any identity provider you select, such as Google.
• Creem processes checkout, payment, subscription management, refunds, and disputes.
• Tencent Cloud hosts the LinguaLayer application, PostgreSQL data, and operational request logs.
• Public authorities or professional advisers receive data only when required by applicable law or necessary to protect users, rights, and service security.

LinguaLayer does not sell or rent user data, share it with data brokers, or disclose it for advertising. Website content and enabled-site origins are never disclosed to these service providers by LinguaLayer. Each provider may process the limited data it receives in the countries where it operates under its own privacy terms.

LinguaLayer's use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Chrome permissions and user data are used only to provide or improve the extension's disclosed language-learning purpose and related security, reliability, account synchronization, and support functions.

LinguaLayer transfers user data only when necessary to provide that purpose through the service providers named above, to comply with applicable law, or to protect against fraud, abuse, and security threats. It does not use or transfer user data for personalized advertising, credit decisions, or sale to data brokers, and does not permit humans to read user data except with the user's explicit consent for support, when necessary for security, or when required by law.

• Local extension data remains until you delete it, clear extension storage, or uninstall the extension.
• Cloud learning profile and expression progress remain while synchronization is active and are deleted when you use Delete learning data while signed in.
• Account identity and subscription records remain while the account or subscription is active, then only as long as needed for support, fraud prevention, disputes, accounting, or legal obligations.
• Operational logs are retained only for the period reasonably necessary for security, reliability, and abuse prevention.

Delete learning data removes the local profile, vocabulary progress, saved article library, enabled-site list, granted website access, and signed-in cloud learning records, then pauses synchronization. Account settings lets you manage Clerk identity and sessions. To request access, correction, export, or deletion of remaining LinguaLayer account or billing records, contact the support address above. Records that must be retained for an unresolved transaction or legal obligation will be isolated and deleted when that obligation ends.

LinguaLayer uses HTTPS in transit, authenticated API requests, restricted server access, and a PostgreSQL service that is not exposed directly to the public Internet. No system is perfectly secure, so please do not send passwords, session tokens, or other secrets to support.

Material policy changes will be published on this page with a new effective date. If a future feature would send page content to an AI or another remote processor, LinguaLayer will first update this policy and provide a clear in-product choice before that processing begins.