Verla Clipper Privacy Policy

Verla Clipper stores text you explicitly select, the source URL, an available page title, and the capture time in Chrome extension local storage. It also temporarily stores import snapshots and request states. It keeps up to 50 recent clips, up to 10 unfinished imports, and a combined 5 MiB storage budget. Import requests expire after 24 hours. The extension does not sync clips between devices or bind local clips to a Verla account.

People sharing the same browser profile can view its saved clips. Editing changes the saved passage while keeping source metadata and capture time. Saving cancels unfilled old import snapshots; applying writes block editing, while filled or uncertain snapshots keep their original content. Deleting a recent clip does not delete an already-created import snapshot. There is no bulk-delete action. Removing the extension deletes its extension-local data. Clearing website cookies does not delete extension clips. Clearing extension data does not remove text already filled or submitted on the website.

When you start an import, the extension continues its existing request or automatically reuses an available supported page that it created earlier in this browser session. Otherwise it opens a new Verla page. It remembers up to 20 extension-created page IDs in session storage, which clears when the browser restarts or the extension reloads. It does not automatically choose separately opened website pages, existing tasks, other features, or Incognito pages. The extension does not enumerate browsing history. Saved source URLs, page titles and capture times relate only to pages you explicitly clip; the extension does not monitor general browsing activity. Search runs locally over existing clips and is not saved or transmitted.

The extension sends a clip to the selected Verla tab only when you initiate an import. A content script runs on https://verla.io/ to identify the supported Assignment composer and observe the visible input and attachment display for stability. It reads the current input to preserve existing text when appending. Only passage text is filled into the website, without appended source title, URL, or capture time. These details remain stored locally and are included only when you choose Copy with source in the popup. Your selected text is not placed into navigation URLs. Initiating Import authorizes one automatic append after conservative public DOM checks. These checks cannot prove that asynchronous saved-draft restoration has completed. Import never automatically opens an interface on the destination website. Failures are shown only in the extension badge and the clip manager, where clips remain available to copy. You decide whether to send the resulting draft using the website’s existing Send button.

The Privacy & help link asks the extension background to open its own bundled help page. It does not expose extension resources to arbitrary websites or transmit data. Verla website entry links include the fixed tags utm_source=verla_clipper and utm_medium=browser_extension, including the login URL and its dashboard return target. They contain no clip text, source URL/title, timestamps, request IDs, or account identifiers. Existing website analytics may use these standard tags for channel attribution; the extension adds no analytics SDK or separate telemetry requests. Reusing an existing page does not reload it or rewrite its URL to add attribution. These tags are never inserted into draft text.

The extension does not access passwords, authentication cookies or tokens, browsing history, or the website’s internal draft databases. It does not send text to an AI provider, run its own analytics collection, sell data, or add advertising. Website handling after filling or sending follows Verla’s existing website policies. This policy does not change the website’s own data practices.

Permission use: contextMenus provides explicit selection actions; storage retains clips and requests locally; activeTab gives temporary access to the page where you invoke the extension. Together with scripting, it opens a clip manager in that page’s upper-right corner only when you click the toolbar icon. This panel uses an isolated script and a closed shadow tree, with management messages bound to the clicked tab and document. It does not scrape the page. Browser-restricted pages keep the native toolbar popup. A static content script is limited to https://verla.io/*; the on-demand manager does not read the full content of source pages. The extension does not request all-site host access, cookies, history, or unlimited storage permissions.

Interface text follows Chrome’s UI language, with Simplified Chinese and English available and English as fallback. Language resolution is local; clip text and source metadata are not translated or sent to a translation service.

Data obtained through extension APIs is used only for the clip-management and user-initiated import purposes described here, in compliance with the Chrome Web Store User Data Policy, including its Limited Use restrictions.

Automatic filling depends on a compatible website input. Review your draft before sending. If a write is interrupted or the page changes, use copy/paste or check the current draft rather than repeating an uncertain operation. Clip source information is not a verified citation and does not imply the full source page has been fetched.

Contact: [email protected]. Please do not send private clip text or credentials in diagnostic reports.