Last updated:November 14, 2026
Loqalit is a Chrome extension for localization QA professionals that scans web pages and analyzes translation quality using AI. This privacy policy describes how the Extension collects, uses, and protects your information. It also covers Loqalit Translate (translate.loqalit.com), our website translation service, the Loqalit platform (app.loqalit.com), the Loqalit connector for AI assistants (such as Claude and ChatGPT), and our website (www.loqalit.com), each in its own section below.
When you click "Scan Page," we extract text content from the active webpage:
We intentionally do not collect DOM locators such as CSS selectors or element positions — scan payloads contain text content and the metadata above only.
Storage: Scan data is stored locally in your browser (IndexedDB for history, chrome.storage.session for active scans). Data is sent to our servers in exactly two cases: when you run the AI analysis feature, and — for signed-in users who have opted in — through the scan-history sync described below.
Purpose: To display scan results, perform quality checks, enable highlighting, and persist scan history locally.
If you are signed in and explicitly enable scan-history sync (one-time dashboard prompt, changeable later in Settings → Account), the dashboard uploads your local scan history to your Loqalit workspace:
Sync is off until you enable it; no scan history is uploaded before that. Disabling sync stops future uploads but does not delete entries already uploaded — clearing local data (Reset) or uninstalling the extension also does not delete server-side copies. You can request deletion of synced data at any time (see Contact below).
When a signed-in scan is associated with a workspace or project, its captured workspace/project context may also be stored with the analysis so the dashboard can distinguish where the scan originated from its later project assignment.
If you use AI analysis with a signed-in account:
For signed-in workspace features, our backend stores the data needed to provide the selected workspace and its access controls:
each user's selected workspace/project context
invitation reference used by the invitation landing page
checkout/portal/cancellation intent metadata such as action, plan, provider reference, status, and timestamps
Hosted payment details are entered directly with Dodo Payments. Loqalit does not receive or store full card details. Opening checkout, a portal, an email draft, or a return URL is not treated as proof that payment or delivery completed; verified provider/backend state remains authoritative.
Our backend logs AI analysis requests including:
For signed-in analyses, the backend also stores the finding contents returned by the AI (message, rationale, and suggestion text — which may quote text from the analyzed page) in our backend database so your analysis results are available in the dashboard. It may also store the immutable originating workspace/project context separately from the analysis's current project assignment. When R2 storage is configured, the backend may additionally store the full request payload including system/user prompts and raw text blocks.
This helps us monitor service health, enforce usage limits, and improve analysis quality.
Guest users (not signed in) can use AI analysis with limited quota:
If you configure the optional Crowdin integration with your own Crowdin Personal Access Token:
chrome.storage.local on your device and is sent only to Crowdin's API (api.crowdin.com) to act on your behalfapi.crowdin.com is an optional browser permission, requested only when you set up the integrationCrowdin data goes directly from your browser to Crowdin — Loqalit servers do not receive or store your Crowdin token or pushed content.
If you configure the optional Phrase Strings integration with your own Phrase API token:
chrome.storage.local on your device and is sent only to Phrase's API (api.phrase.com) to act on your behalfapi.phrase.com is an optional browser permission, requested only when you set up the integrationPhrase data goes directly from your browser to Phrase — Loqalit servers do not receive or store your Phrase token or pushed content.
The Extension can save operational diagnostic entries locally when expected product operations partially fail, such as skipped screenshot evidence capture. Backend upload is disabled by default and controlled by release configuration. When enabled, uploaded product diagnostics are limited to:
error code
severity, and error code
Uploaded product diagnostics do not include screenshots, DOM snapshots, full page text, raw AI payloads, cookies, authorization headers, Clerk tokens, raw request headers, or raw query strings.
Vendor crash monitoring is currently disabled. If enabled later, it will be a separate exception-reporting lane for sanitized crashes only; session replay is not part of the current product.
Configuration preferences stored in Chrome storage:
(unset, deferred, enabled, or explicitly declined)
Storage: Most preferences use chrome.storage.sync. Onboarding state, sync consent, and a few local-only UX flags use chrome.storage.local.
Loqalit Translate is a separate product: website owners add a small script to their site, and their visitors can read the site in other languages. Because it runs on our customers' websites, it handles data from two groups of people.
We collect your account information (through Clerk, as above), your site configuration (domain, chosen languages, switcher appearance, glossary rules, and translation style settings), an optional site key that identifies your site to our service, and billing information (through Dodo Payments, as above; we never receive card data). Text content from your website's pages and its translations are stored in your site's translation memory (see below) for as long as your site is registered. When you remove a site, its translation memory and configuration are deleted.
When you view a page on a site that has installed Loqalit Translate and choose a language:
Personalized content is deliberately kept out of storage. A piece of text is only written to a site's shared translation memory after it has been seen from two independent browsing sessions. Text that appears only in your session — your name, an order number, private account details — may be translated for your screen but is never stored.
Translation memories (source text and translations) are stored at the network edge on Cloudflare infrastructure. When new text needs translating, it is sent from our service to an AI translation provider (see the third-party table) as text only, wrapped so that it is treated strictly as content to translate. Site owners' glossary rules and style settings are applied during translation.
The demo on our landing page translates a page you point it at without storing anything: demo translations are shown to you and then discarded, and demo access expires automatically. Site previews (used during onboarding) fetch the customer's page the way a normal visitor would, forward no cookies in either direction, and are marked non-indexable for search engines.
For visitor data processed on a customer's website, the website owner decides to use Loqalit Translate on their site and is responsible for informing their visitors; Loqalit processes this data on the owner's behalf, only to provide the translation service described here. If you are a visitor with questions or requests about a specific website's data, contact that website's owner; you can also reach us at info@loqalit.com.
The Loqalit platform is the service your team uses at app.loqalit.com. You choose the pages of your product (and, where enabled for your workspace, your mobile apps) and the languages to check; Loqalit checks them on a schedule or when you ask, keeps the findings, and helps you fix them. Your workspace's administrators decide what is checked and who has access. For the pages, apps, and content you point us at, we process data on your behalf.
If you set up a sign-in for scans, you give us a login page, a test account and, if that account uses an authenticator app, its two-factor seed. We store these encrypted and open them only inside the scan worker that signs in for a run. They are never shown again in the app or returned by any API. Please use a dedicated test account, not a person's own account. Our workers never solve CAPTCHAs.
qa.loqalit.com. We receive the confirmation emails sent to those addresses and keep only their subject, text, links, and one-time codes, for that sign-up.Platform data is stored in our backend database and file storage. Scans run on servers and build runners we rent (see Third-Party Services), and analysis runs at our AI provider. These providers may process data outside the European Economic Area, including in the United States. We do not currently offer EU-only data storage.
You can connect Loqalit to an AI assistant that supports the Model Context Protocol (MCP), such as Claude, ChatGPT, Cursor, or Codex. The assistant can then call Loqalit's tools on your behalf: list your projects, read their findings, start scans of public web pages, and check text you provide.
openai-mcp), used to count usage per assistant.Tool results are sent to the AI assistant you connected: project names, findings (which may quote text from the analyzed pages), scan status, and links to the Loqalit app. Once delivered, that content is processed by the assistant's provider under its own privacy policy, not ours. Page text in results is labeled as untrusted content from third-party websites.
This section covers visits to our website, www.loqalit.com. The sections above cover the Extension, your Loqalit account, Loqalit Translate, and the AI-assistant connector.
The website is hosted on Cloudflare Pages. Cloudflare processes standard web request data, such as your IP address, browser, and the page requested, to deliver the site and protect it from abuse.
If you choose "Allow analytics" in the cookie banner, we load Google Analytics 4 to understand which pages are useful and how visitors find us. Until you do, or if you choose "Reject", the Google Analytics script is not loaded and no analytics cookies are set.
_ga and _ga_<ID>, which tell one visitor from another.You can change your choice at any time with "Cookie settings" at the bottom of every page. If you withdraw consent, Google Analytics stops loading and its cookies are removed. Your choice is saved in your browser's local storage so we don't ask again.
When you send the free QA report form or the demo request form, we receive what you enter: your work email, your company website and, depending on the form, your name, the languages and pages you name, what you want Loqalit to check, how you check translations today, and any notes.
With the request we also receive two details about how your visit started: the first page you opened on our website and the site that referred you (for example a search engine or an AI assistant), plus the campaign source if the link you followed had one. The website keeps these two details in your browser for the current tab only (session storage) and sends them only when you submit a form. Cloudflare also tells us the country the request came from.
The request is emailed to our team through Resend and used to prepare your report or demo, to contact you about it, and to understand which pages bring requests. We keep these requests until you ask us to delete them (see Contact).
After sending the demo request form you can choose "Pick a time now". Only then does our scheduling page from Cal.com load on the page, with your name, email, and answers filled in. If you book a time, Cal.com processes the booking under its own privacy policy and adds the meeting to our calendar. Cal.com is not loaded unless you choose to pick a time.
The website serves its fonts from our own servers; no request goes to Google Fonts. The website is translated with Loqalit Translate, as described in the Loqalit Translate section above.
When you click "Analyze with AI":
Note: When R2 storage is configured, full request payloads (prompts and raw text blocks) may additionally be stored for quality review. Request metadata (page URL, domain, block count, token usage) is always logged.
| Service | Purpose | Data received | Privacy Policy |
|---|---|---|---|
| Clerk | Authentication | Email, sign-in session data | clerk.com/legal/privacy |
| Convex | Backend infrastructure | AI analysis payloads, request logs, synced scan history, workspace/project context, invitations, and billing records | convex.dev/legal/privacy |
| Cloudflare Pages | Auth UI and website hosting, website forms | Standard web request data; website form submissions on their way to us | cloudflare.com/privacypolicy |
| Google Gemini | AI analysis, the platform assistant, and dictation | Extracted page text and screenshots, text submitted through the AI-assistant connector, assistant questions and the project data needed to answer them, and dictation recordings (via our backend) | ai.google.dev/terms |
| OpenRouter | Machine translation (Loqalit Translate) | Website text strings to be translated (via our service; no visitor identifiers) | openrouter.ai/privacy |
| Crowdin | Optional issue handoff (user-run) | Finding text, page URL/title, page-text excerpt, screenshots — sent to your own project | crowdin.com/page/privacy-policy |
| Phrase Strings | Optional key-comment handoff (user-run) | Finding text, page URL/title, page-text excerpt, screenshots — sent to your own project | phrase.com/legal/privacy |
| Dodo Payments | Payment processing (merchant of record) | Name, email, billing address, and payment details you enter on Dodo's hosted checkout; Loqalit never receives card data | dodopayments.com/privacy |
| OneSignal | Transactional email delivery | Recipient email address and the content of workspace/billing notification emails | onesignal.com/privacy_policy |
| Hetzner | Servers that run platform scans and agents | The pages being scanned and what the workers read from them | hetzner.com/legal/privacy-policy |
| GitHub Actions and Blacksmith | Build runners that run platform scans and mobile app checks | The pages and app screens being checked and what the workers read from them | GitHub privacy statement, blacksmith.sh/privacy |
| Cloudflare R2 | File storage | Screenshots and stored analysis payloads | cloudflare.com/privacypolicy |
| Slack | Optional assistant in your Slack workspace (connected by your admin) | Questions asked of the Loqalit app and its answers, which may include findings | slack.com/trust/privacy/privacy-policy |
| Google Analytics 4 | Website analytics, only if you allow it in the cookie banner | Pages viewed, referring site, approximate location, device/browser, interactions; _ga cookies | policies.google.com/privacy |
| Resend | Delivery of website form requests to our team | The contents of the free QA report and demo request forms, first page visited, referring site | resend.com/legal/privacy-policy |
| Cal.com | Demo scheduling, only if you choose to pick a time | Name, email, form answers, and the booking you make | cal.com/privacy |
| AI assistant you connect (e.g. Claude by Anthropic, ChatGPT by OpenAI) | Runs Loqalit tools you ask it to use (your choice, not our service provider) | The results of the Loqalit tools it calls: project names, findings, scan status, links | Your assistant provider's policy, e.g. anthropic.com/legal/privacy, openai.com/policies/privacy-policy |
We do not sell user data. The Extension does not include analytics or ad tracking libraries, and its production manifest allowlists no telemetry endpoints (Clerk SDK telemetry is disabled). Our website uses Google Analytics only if you allow it (see "Our Website").
The Extension requests the following permissions:
| Permission | Purpose |
|---|---|
scripting, activeTab | Inject the content script to scan the current page |
storage | Save preferences and scan state locally |
sidePanel | Display results in Chrome's side panel |
cookies | Required by the Clerk authentication SDK for session synchronization (not used to read site cookies) |
| Loqalit backend/auth hosts | Host permissions for our Convex backend and Clerk auth domains (AI analysis, sign-in) |
api.crowdin.com (optional) | Requested only when you set up the Crowdin integration |
<all_urls> (optional) | Requested only when you grant site access for scanning, or when you click "Allow screenshot access" in the export dialog to make screenshot evidence capture reliable. Revocable anytime in Chrome's extension settings |
You can:
In the Extension, Loqalit Translate, and the AI-assistant connector, we do not:
Our website uses Google Analytics only after you allow it in the cookie banner, shows no advertisements, and has advertising features of Google Analytics turned off in its consent settings.
This extension is not intended for users under 13 years of age.
We may update this privacy policy. Changes will be reflected in the "Last Updated" date above.
For privacy questions or data deletion requests: