LLaforM Chrome Extensions — Privacy Policy

Scope

This policy applies to all LLaforM Chrome extensions published by Signovus Insights (LLaforM), including current and future extensions distributed via the Chrome Web Store or enterprise policy. Each extension's store listing describes its specific features; this page covers shared data practices across the LLaforM extension family.

These extensions are for authorized users of a LLaforM organization account. They are not directed at children under 13.

For the LLaforM web platform, see our main privacy policy.

What our extensions do

LLaforM extensions connect your browser to the LLaforM platform at llaform.com and api.llaform.com. Features vary by extension (for example: screenshot analysis or drafting an open form field), but all require you to sign in with your organization's LLaforM account unless stated otherwise in the extension listing.

Extensions only access the current tab or page content when you take an explicit action in the extension (such as clicking a button in the popup). We do not run hidden background collection of browsing history or page content, and we do not inject persistent content scripts.

Screenshot Assistant

LLaforM Screenshot Assistant lets a signed-in user capture the active browser tab and ask LLaforM for copy and layout suggestions.

• A screenshot is taken only after you click a capture mode (visible part, full page, or selected area). For full page, the extension briefly injects a helper to measure and scroll the tab so it can stitch the page. For a selected area, it briefly shows an overlay so you can draw a rectangle. Those helpers do not read form fields or send page HTML.
• The screenshot stays on your device until you click Analyze. Analyze sends the screenshot and your prompt to api.llaform.com. Follow-up questions in the same chat are also sent to api.llaform.com.
• After Analyze, the prompt, screenshot, and suggestions are stored in your organization's LLaforM chat history. History in the popup is loaded from the server. Delete chat removes that conversation from LLaforM chat history. It does not retract data already processed by your organization's configured LLM provider.
• Signing out removes the authentication token stored on this device. It does not delete server History.

A screenshot of the current tab may include whatever is visible on that page, including personal or confidential information. Only capture tabs you are authorized to share with LLaforM.

Note Assistant

LLaforM Note Assistant lets a signed-in user draft text into the Form Rich Text Area that is already open on the active tab.

• After you click the toolbar icon, the extension may read visible note text on that tab (section headings, checked options, the open field prompt, and nearby labels). It does not inject a persistent content script. If Form Rich Text Area is not open, it does not change the page.
• That text is sent to api.llaform.com to generate a draft. The draft is inserted into the open editor. The extension does not click Continue, Save, or otherwise submit the note.
• Signing out removes the authentication token stored on this device.

Note text may include personal or confidential information. Only use Note Assistant on notes you are authorized to share with LLaforM.

Data we collect and process

Depending on the extension you use, we may process:

• Authentication information — a session token, plus your LLaforM user ID, display name, and organization (company) ID, stored locally in Chrome extension storage after you sign in at llaform.com. Used to call LLaforM APIs on your behalf and to enforce organization access.
• User-provided content — text, prompts, images (such as visible-area, full-page, or selected-area tab screenshots), and visible form text from an open Form Rich Text Area that you explicitly submit by using the extension.
• Short-lived local capture data — for selected-area capture, a temporary copy of the cropped screenshot (and the prompt you had typed) may be stored in Chrome extension storage until you reopen the popup or cancel. This is not sent to LLaforM unless you click Analyze.
• Technical data — standard request metadata (e.g. timestamps, API errors) needed to operate and secure the service.

We do not collect your general browsing history. We do not sell personal data.

How we use data

Data is used only to operate the extension and the LLaforM service you requested: sign you in, capture and analyze a screenshot you asked for, draft text into an open Form Rich Text Area you asked to fill, show History, and delete a conversation you asked to delete. We do not use extension data for advertising, unrelated profiling, or creditworthiness decisions.

Third parties

Content you submit through an extension may be processed by LLM or other providers configured for your organization (for example OpenAI, Anthropic, or Google) through the LLaforM platform. Processing is governed by your organization's LLaforM agreement and applicable provider terms. Google Chrome hosts extension distribution; see Google's privacy policy for browser and store-related processing.

Data retention

The authentication token stored locally remains until you sign out, clear extension data, or uninstall. Temporary selected-area capture data is removed when the popup consumes it, you cancel the selection, you clear extension data, or you uninstall. Retention of content sent to LLaforM APIs (including Screenshot Assistant chat history) depends on your organization's LLaforM settings. You can delete an individual Screenshot Assistant conversation from History in the extension.

Your choices

• In Screenshot Assistant, open History and choose Delete chat to remove that conversation from LLaforM chat history.
• In Note Assistant, sign out to remove the locally stored authentication token. The extension does not keep a chat History list.
• Sign out of an extension (where offered) to remove the locally stored auth token. This does not delete server History.
• Revoke permissions or uninstall any extension from Chrome at any time to stop all extension activity and remove locally stored extension data.
• Contact your organization administrator for account-level access or data questions.