Privacy Policy

Effective Date: October 3, 2026

1. Introduction

Verbatch is a Chrome extension that helps you copy text you can already see on a web page when the page interferes with normal copying, for example by disabling text selection, blocking the right-click menu, or changing what ends up on your clipboard.

This policy explains what information the extension and this website handle, where it is kept, and what controls you have. It applies to the Verbatch Chrome extension (version 1.0.1 at the time of writing) and, where stated, to this website.

The extension contains no code that sends information to the developer or to any server, and this policy describes only what the extension actually does.

2. Information We Collect

Information the extension collects

The extension does not transmit any information to the developer or to any other server. It contains no analytics, telemetry, crash or error reporting, advertising, or account system, and it does not make network requests.

The only information the extension records is kept on your own device and is described in Section 3: your settings and site rules, and, only if you turn on Copy History, the text you copied together with the site name, page title and time.

Information processed locally

To do its job, the extension processes the following inside your browser. None of it is transmitted by the extension, and none of it is stored unless Section 3 says so.

The text you have selected on a page, and the page markup for that selection, when you copy. The markup is used to build the Markdown, HTML or rich-text formats if you choose one of them.
Technical properties of the page that indicate copy restrictions, such as whether text selection is disabled with CSS, whether certain inline event attributes are present, and whether an invisible layer covers the page.
Selection, copy, right-click, keyboard and pointer events on the page, used to detect and undo attempts to block or alter copying.
The address of the tab you are viewing, when you open the extension’s popup. It is used to show the site name and to apply or save a per-site rule.

The extension writes to your clipboard but does not read what is already on it. It does not use Chrome’s cookies, identity, browsing-history or network-request APIs, and it does not read cookies or sign-in credentials. Editable areas such as text boxes and code editors are skipped by its copy handling.

Information the website collects

This is separate from the extension. See Section 7.

3. Information Stored on Your Device

The extension stores data using Chrome’s local extension storage (chrome.storage.local). It does not use Chrome’s synchronized storage area, so the extension does not itself sync this data across your devices.

Settings

What is stored: Your on/off choices (enable Verbatch, automatic detection, Force Copy, Force Copy on all sites, selection toolbar, Copy History) and your chosen copy format.
Why: So the extension behaves the way you configured it.

Site rules

What is stored: The domain names you add to the “Force Copy on these sites” and “Never run on these sites” lists, including a domain saved when you choose “Enable on this site” in the popup.
Why: To apply your per-site preferences.

Copy History (optional, off by default)

What is stored: For each saved copy: the selected text (up to 20,000 characters), the site’s domain name, the page title (up to 200 characters), a timestamp, and a random identifier. The full page address is not stored. Up to 300 entries are kept, newest first; repeating an identical copy replaces the older entry.
Why: So you can search your past copies and copy them again from the popup.

Deleting this data

You can delete a single history entry or clear all history from the popup. Turning off “Save copy history” stops new entries from being saved, but does not by itself delete entries that were already saved; use “Clear history” for that. You can edit or empty your site rules in Settings.

Uninstalling

When you uninstall the extension, Chrome removes the extension’s locally stored data from your browser.

Incognito windows

Chrome runs extensions in Incognito windows only if you allow it. If you do, Verbatch works the same way there and uses the same local extension storage, so settings, site rules and any Copy History saved during an Incognito session are kept with the rest and are not cleared when the Incognito window closes. Leave Incognito access off, or turn off Copy History, if you do not want that.

4. How We Use Information

Information is used only for the extension’s own functions:

Restoring normal selecting and copying on pages that interfere with it, and copying your selection to your clipboard in the format you chose.
Remembering your settings and per-site rules.
If you enable it, keeping a searchable list of your recent copies so you can copy them again.

The extension does not use this information for advertising, analytics or profiling, because it has no code that does so.

5. Data Sharing and Disclosure

Sold: No. The extension does not send data anywhere, so there is nothing for it to sell.
Shared with third parties or service providers: The extension does not share data with any.
Sent to analytics providers or external APIs: No. The extension contains none.
Sent to the developer: No. The developer receives no data from the extension.

This describes the extension itself. Once text is on your clipboard, other software on your device and any site or app you paste into can access it under their own practices, which Verbatch does not control. If you email the developer, the developer will receive your email address and message.

6. Third-Party Services

Extension

The extension uses no third-party services and loads no remote scripts or resources; all of its code ships in the extension package.

The extension’s welcome page has a button that, when you click it, opens the demonstration on this website (https://verbatch.vercel.app/#demo) in a new tab. This is an ordinary browser navigation that you initiate; the extension sends no data to that site. The extension’s Settings and Privacy pages also contain a plain link to this policy.

Website

Google Fonts

Purpose: Displays the Fraunces and Inter typefaces on this website.
What may be transmitted: When a page loads, your browser requests the fonts from fonts.googleapis.com and fonts.gstatic.com. As with any web request, that includes technical information such as your IP address and browser details.
Provider’s policy: Google Privacy Policy

Installing the extension through the Chrome Web Store is governed by Google’s own terms and policies, which are separate from this policy.

7. Website and Hosting

This website is a static site hosted on Vercel. Its own code contains no analytics, advertising or tracking scripts, and does not set cookies or use browser storage. The interactive demonstration on the home page is an illustration that runs entirely in your browser; what you select or copy there is not sent anywhere.

The only third-party resource the site loads is Google Fonts, described in Section 6. In addition, any web host necessarily receives the technical information your browser sends with a request, such as your IP address, the page requested and your browser type. That information is handled by the hosting provider under its own practices, and Verbatch does not use it for any other purpose.

8. Permissions

These are the permissions declared in the extension’s manifest. A permission name does not by itself describe what data is handled; the notes below describe how each one is actually used.

`storage`

Why it is required: To keep your settings, site rules and optional Copy History between browser sessions.
How it is used: Data is written to and read from Chrome’s local extension storage, as described in Section 3.

`contextMenus`

Why it is required: To add a “Copy with Verbatch” item to the right-click menu.
How it is used: The item appears when text is selected. Choosing it asks the page’s Verbatch script to copy the current selection.

`clipboardWrite`

Why it is required: To place the selected text on your clipboard.
How it is used: The extension writes to the clipboard when you copy with Verbatch, and when you click an entry in Copy History. It does not read the clipboard.

`activeTab`

Why it is required: To identify the tab you are using when you open the popup or use the keyboard shortcut or context menu.
How it is used: The extension reads the current tab’s address to show the site name and to apply or save a per-site rule, and sends that tab a message to copy the selection.

Access to all websites (`<all_urls>` content script)

Why it is required: Copy restrictions can only be detected and undone by code running inside the page, and the extension cannot know in advance which sites restrict copying. A content script therefore runs on every page you visit, including embedded frames, and starts as the page begins to load.
How it is used: The script reads your selection and page properties as described in Section 2. On pages where protection is active it also changes how the page behaves in your browser, for example by overriding CSS that blocks selection, removing certain inline event attributes, stopping the page’s copy-blocking handlers, and disabling pointer events on invisible covering layers. It can show a small confirmation message and, if you enable it, a selection toolbar. Chrome may describe this kind of access as the ability to read and change your data on the websites you visit. The extension does not transmit page content.

The manifest also defines keyboard shortcuts (Ctrl/Cmd+Shift+C to copy the selection, and an unassigned “copy clean” shortcut). Shortcuts are not a data permission.

9. Website Content and User-Selected Content

Verbatch works on text from the web pages you visit, so this section describes exactly how that content is handled.

Is selected text processed?: Yes, inside your browser, when you copy. The extension reads the selection and, for Markdown, HTML or rich-text formats, the markup of the selected part of the page, and converts it locally.
Is copied content stored?: Not by default. It is stored only if you turn on Copy History, and then only on your device.
Is copied content transmitted?: No. The extension has no code that sends content anywhere.
Does a copy history exist?: Yes, as an optional feature that is off by default. When it is on, it saves copies made with Verbatch’s buttons, shortcut, context-menu item and toolbar, and also ordinary Ctrl/Cmd+C copies of page text on sites where Verbatch is not turned off. Copies inside editable fields are not saved. The extension does not analyze or filter what you copy, so anything you copy from a page, including sensitive text, is saved as-is while history is on. If that is a concern, leave history off or clear it regularly.
Are page URLs stored?: No full page addresses are stored. The domain name of the page (or embedded frame) you copied from is stored with each history entry. Domains you add to your site rules are also stored.
Are page titles stored?: Only in Copy History entries, truncated to 200 characters.
Are timestamps stored?: Yes, one per Copy History entry, so you can see when you copied it.
Is content sent to an external service?: No.

Data categories used in Chrome Web Store disclosures

Personally identifiable, health, financial, authentication, location and personal-communications information: the extension does not look for, request or classify these. Because it copies whatever text you select, text of this kind could pass through the extension on your device, and would be stored only if Copy History is on. It is never transmitted by the extension.
Web history: the extension does not use Chrome’s history API and does not build a record of the pages you visit. If Copy History is on, the domain and title of pages you copied from are stored with those copies.
User activity: the extension listens to selection, copy, keyboard and pointer events on pages in order to detect and undo copy restrictions. It does not record these events; the only activity it saves is the Copy History described above, if enabled.
Website content: handled as described in this section.

10. Data Security

The main safeguard is architectural: the extension contains no code that transmits your data, and it loads no remote code. All of its scripts are included in the extension package.

Stored settings, site rules and Copy History are kept in Chrome’s extension storage inside your browser profile. The extension does not add its own encryption to them. They therefore depend on the security of your device, your operating-system account and your browser profile, and someone with access to those may be able to read them. No method of storing or transmitting data can be guaranteed to be completely secure.

11. Data Retention

Settings and site rules: kept until you change or remove them, or uninstall the extension.
Copy History: kept until you delete an entry, clear the history, or uninstall the extension. There is no time-based expiry. When more than 300 entries exist, the oldest are removed automatically.
Data held by the developer: none is received from the extension. Emails you send to the developer are kept for as long as the developer keeps that correspondence.

12. User Controls

Disable features: in Settings you can turn off Verbatch entirely, automatic detection, Force Copy, Force Copy on all sites, the selection toolbar and Copy History, and choose the copy format.
Per-site control: add domains to “Never run on these sites” or “Force Copy on these sites”, or use the popup to enable Verbatch on the current site or force it for the current page.
Delete stored data: delete single history entries or use “Clear history” in the popup; edit or empty site rules in Settings.
Uninstall: remove the extension from chrome://extensions.
Contact the developer: see Section 16.

13. Children’s Privacy

Verbatch is a general-purpose tool and is not directed at children. The extension does not send information to the developer, so the developer does not knowingly collect personal information from children through it. If you believe a child has sent personal information to the developer by email, please contact the developer at the address in Section 16 so it can be deleted.

14. International Users

The extension can be installed from anywhere Chrome is available. Its settings and any Copy History stay on the device where it runs. When you visit this website, your request is handled by web servers that may be located outside your country. This policy makes no statement about compliance with any specific national or regional privacy law.

15. Changes to This Privacy Policy

This policy may be updated when the extension’s data practices change. The updated policy will be published on this page with a revised effective date.

16. Contact

Questions about this policy or about how Verbatch handles information can be sent to jithinkrishnan42@gmail.com.