Privacy Policy

Last updated: 5 November 2026

Leraix is a browser automation assistant that runs in Chrome's side panel and works with a compatible AI service you configure. This policy describes what is stored on your device, what is sent to that service, and what is sent to the services that handle licences, payments and support.

1. The short version

Leraix operates no server for your tasks. It sends each request directly from your browser to the AI service you selected. That service, not Leraix, receives and processes the data described below.

• Your provider settings, API key and conversation history are stored locally in chrome.storage.local on this device.
• Each request contains your current message, relevant earlier parts of the conversation, the page information needed for the task, and the record of actions already taken. It goes directly to the compatible AI service configured in Settings, with your API key for authentication.
• Task data is not routed through, or stored on, a Leraix server.
• The AI service handles what it receives under its own privacy policy and data-retention practices. We do not control what it keeps or for how long.
• Leraix does not monitor browsing in the background. Page and tab access happens only while you are running a task.
• Changing the provider or its endpoint requires a fresh acknowledgement before existing page information can be sent to the new recipient.
• A paid licence key is sent to Dodo Payments' licence validation endpoint; payments are handled by Dodo Payments; messages sent through the feedback form on this site are delivered by Web3Forms.

2. What a request may contain

Depending on the task, the following may be sent to the selected AI service:

• your current message and relevant earlier parts of this conversation, including page information captured earlier in it;
• visible page text, form field values, element labels and roles, link destinations, and the URL and title of a page;
• the titles and URLs of tabs open in the current window when a task lists them;
• the record of the assistant's actions and their results — clicks, text entry, scrolling, navigation, opening, switching and closing tabs, and other tool calls — because the service needs each result to choose the next step;
• screenshots of the visible page when the configured service supports images;
• images you attach and the text extracted from documents you attach.

The page reader is general. Page content can therefore incidentally contain names, addresses, email addresses, messages, health information, financial information or other sensitive material that happens to be visible on the page. Leraix does not seek out those categories, but it cannot exclude them from arbitrary page text. Do not run a task on a page whose contents you are not willing to share with the service you selected.

Fields that a page marks as password, one-time-code or payment fields are refused: Leraix does not read their values and does not type into them. That protection applies to marked fields, not to every value on a page — ordinary text fields and visible page text are still read. If a page displays sensitive information as ordinary text, it may be included.

3. Where the data goes

Requests go from your browser straight to the AI service you configured. Remote endpoints must use HTTPS; plain HTTP is accepted only for local model servers on localhost or 127.0.0.1. The service's own privacy policy and data-retention practices govern what happens to the information after it arrives.

If you install a skill from a URL, the extension fetches that file from the address you provided. Nothing about your pages or history is included in that request. A skill is markdown instructions, never executable code.

4. Chrome Web Store Limited Use

Leraix's use and transfer of user data complies with the Chrome Web Store Limited Use requirements.

• The extension uses and transfers user data only to provide and improve its single disclosed purpose: reading and operating the pages and tabs of the current browser window in response to the tasks you start, by sending your selected task, page information and attachments to the AI service you configure.
• Leraix does not use or transfer user data for any purpose unrelated to that single purpose.
• Leraix does not sell user data, and does not use or transfer it to determine creditworthiness, for lending, or for insurance underwriting.
• All task data is transmitted directly to the AI service you configured and is not routed through or stored on any Leraix server.

5. Data stored on your device

The extension stores the following locally in chrome.storage.local:

• provider settings, base URL, model choice, temperature, step limit and API key;
• conversation history, including the text extracted from documents you attach, and the step labels shown in the panel;
• your licence key status, daily task counter, and the record that you acknowledged the data-sharing notice;
• installed skills.

Images you attach are sent with that request but are not written to stored history; they are replaced by a placeholder. Values of fields the extension identifies as password, one-time-code or payment fields are refused, so they are never read or stored — but text that merely looks like a password in an ordinary message, an attached document, or visible page content may still be transmitted to the service and retained in conversation history. There is no account and no sync: this data exists only on this device until you delete the conversation, withdraw consent, or remove the extension. Removing the extension deletes it, so export anything you want to keep first.

6. Tabs, pages and permissions

Leraix can work across the tabs of the current browser window, not only a single active tab. A task can list the tabs open in that window and receive their titles and URLs, open a new tab at a URL, switch to another tab, and close a tab. All of these are actions the assistant takes only in response to a task you started; the extension does not watch tabs in the background and does not read a tab's contents unless that tab is the one being worked on. Current-window tab titles and URLs are declared as web history in the Chrome Web Store data disclosures, even though Leraix keeps no log of pages you visited in the past.

The permissions declared in the manifest are used as follows:

• activeTab / host permissions — to read and act on the page a task is working on, across whichever site that happens to be;
• scripting — to inject the automation layer into that tab;
• storage — to keep settings, keys and conversations locally;
• sidePanel — to provide the chat interface;
• clipboardWrite — only when a task asks the assistant to copy text to your clipboard.

Chrome's own pages, the Chrome Web Store and other extensions' pages cannot be read or controlled.

7. Licence validation

If you activate a paid licence, the extension sends the licence key to Dodo Payments' licence validation endpoint, which checks it against the purchase record created at checkout to confirm validity and fetch the expiry date. That request contains the key and standard request metadata, and nothing else. The result is cached locally, so validation is not continuous.

That endpoint may log standard request metadata (timestamp, IP address, response status) for security and abuse prevention. It does not receive page content, prompts, or model responses.

8. Payments

Purchases are processed by Dodo Payments as merchant of record. We never see or store your card details. Billing information you provide at checkout is handled under Dodo Payments's privacy policy.

9. Website and support

The site is a static page. It sets no tracking cookies and includes no advertising or analytics scripts. If you send feedback through the form, your message and any name or email you enter are submitted through Web3Forms, a third-party form service, and delivered to our support inbox; the site itself does not store them. If you email us directly, we receive what you choose to send. If the site is hosted on a third-party platform, that provider may keep standard server logs under its own policy.

Leraix does not use the Geolocation API, does not request location permission, and does not infer your location from IP address. Any location-like text visible on a page is simply page content, covered by section 2.

10. Children

The Service is not directed to children under 13, and we do not knowingly collect data from them.

11. Your rights

Most requests can be satisfied by clearing the extension's storage, deleting a conversation, or withdrawing consent in Settings. For purchase records held by Dodo Payments, contact them or us and we will help. You may also request deletion of any support correspondence we hold.

12. Changes

If this policy changes materially, we will update this page and its date, and a new in-product acknowledgement may be required. Continued use of the Service after an update means you accept the revised policy.

13. Contact

Privacy questions: leraix.support@gmail.com.