This Privacy Policy ("Policy") describes how the browser extension Highlight ("Highlight," "the Extension," "we," "us," or "our") handles information in connection with your use of the Extension. This Policy is intended to comply with the Chrome Web Store Developer Program Policies and applicable data protection laws, including the EU General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA), to the extent they apply. By installing or using the Extension, you agree to the practices described in this Policy.

1. Summary
   Highlight is a local, client-side browser extension. It does not operate a backend server, does not collect Personal Data as defined below, and does not transmit any data to the developer or to any third party. All configuration data created by the user — including lists, folders, word rules, combination rules, and preferences — is stored exclusively within the user's own browser, using the browser vendor's built-in synchronization infrastructure, and is never accessible to the developer. Every feature of the Extension, including the right-click "Add to list" action, the scope quick-add controls described in Section 5, and any in-page notification, operates entirely on-device. Where this Policy states that "no data is collected," this refers to collection by the developer; it does not describe the technical capabilities of the underlying browser platform, which are governed by the applicable browser vendor's own privacy policy.
2. Definitions
   "Personal Data" means any information relating to an identified or identifiable natural person.
   "Extension Data" means the configuration data a user creates while using Highlight, including but not limited to word and phrase lists, folder names and structures, color and style assignments, tooltip text, word rules (per-word overrides of tooltip, link, or notification behavior within a list), combination rules, site-scoping entries (the domains and pages a list is restricted to or excluded from), notification and sound preferences, theme and density settings, and other in-extension settings.
   "Local Storage" means data storage that resides on the user's own device and/or within the user's browser vendor's account-sync infrastructure (chrome.storage.sync and/or chrome.storage.local), and that is not accessible by the developer. The Extension may automatically store a given list in either of these two browser-provided storage areas depending on its size, as described in Section 4; both remain entirely local to the user's browser and neither is accessible to the developer.
   "Page Content" means the text and visual content of a webpage as rendered in the user's browser, including any portion of that text the user manually selects.
   "Shared Configuration Code" means a portable block of text, generated entirely on-device, that represents a single list, word rule, or combination rule a user may choose to copy and share with another person (for example, by pasting it into an email or chat message of their own choosing) so that person can import the same configuration into their own installation of the Extension. The developer has no role in, and no visibility into, this exchange.
3. Information We Do Not Collect
   Highlight does not collect, and the developer does not have access to, any of the following categories of information, whether from users or from the webpages users visit:

Personally identifiable information (name, address, email address, age, or identification numbers).
Health information of any kind.
Financial or payment information.
Authentication credentials, passwords, or security PINs.
Personal communications, including emails, SMS, or chat messages.
Precise or approximate location data, including IP-derived location.
Web browsing history.
Keystrokes, mouse movement, or other user activity monitoring data.
The substantive content of the websites a user visits, beyond the transient, on-device text-matching described in Section 5, the specific, user-selected text involved in the "Add to list" action described in Section 5, or the current tab's URL/domain involved in the scope quick-add controls described in Section 5.
No information in the categories above is sold, rented, shared, transferred, or otherwise disclosed to any third party, because none of it is collected in the first place.

1. Extension Data We Store
   To provide its core functionality, Highlight stores the following Extension Data, created entirely by the user, in Local Storage:

Word and phrase lists the user defines, together with any assigned colors, formatting, and matching options.
Folder names and the organizational structure of the user's lists.
Tooltip text and link destinations the user attaches to highlighted terms, including any per-word overrides configured as a word rule.
Combination rules configured by the user, and word rules configured by the user, including any rule the user chooses to export as a Shared Configuration Code.
Site-scoping entries (the domains and specific pages a list applies to or is excluded from), including any entry added via the scope quick-add controls described in Section 5.
Notification, sound, theme, and density preferences, and other in-extension settings, including paused/active status of individual lists.
This Extension Data is stored using the chrome.storage.sync API provided by the browser, with one exception: if a single list grows too large for the browser's own per-item sync size limit, the Extension automatically stores that list in chrome.storage.local instead so that it is not lost, and moves it back to chrome.storage.sync automatically if it later shrinks back under that limit. Both storage areas are provided directly by the browser and are never accessible to the developer. As a result:

The data resides within the user's own browser profile.
If the user is signed into a browser account, sync-eligible data may sync across that same user's own devices via the browser vendor's account infrastructure, subject to the browser vendor's own privacy policy and terms.
The developer of Highlight has no mechanism to access, view, export, or retrieve this data, regardless of which of the two local storage areas it resides in. There is no developer-operated database, server, or analytics dashboard through which this data passes or is stored.
5. How Page Content Is Processed
Highlight's core function requires comparing the visible text of the webpage currently open in the user's browser against the user's configured word and phrase lists, in order to apply highlight formatting to matching terms. This comparison occurs entirely within the user's browser, in memory, at the moment the page is viewed. Page Content processed in this manner:

Is never transmitted off the user's device.
Is never logged, cached, or persisted by the Extension beyond the active browsing session.
Is never seen by, or made available to, the developer.
Right-click "Add to list." The Extension also allows a user to select a portion of Page Content, right-click, and choose to add that exact selected text to one of their existing word lists, or to a new list. When used, this action reads only the specific text the user has manually selected — not the surrounding page — and writes it directly into that list's Extension Data in Local Storage. This happens entirely within the user's browser at the moment they choose to invoke it; the selected text is never transmitted off the user's device or made available to the developer.

Scope quick-add controls. When configuring which sites a list applies to or is excluded from, the Extension offers optional "Add this page" and "Add this domain" controls that read the URL or domain of the browser tab the user is currently viewing and insert it into that list's site-scoping fields, so the user does not need to type or copy it manually. This reads only the current tab's own URL, occurs entirely on-device at the moment the user clicks the control, and the resulting value is stored exclusively as Extension Data described in Section 4. It is never transmitted off the user's device or made available to the developer.

The Extension requests broad host permissions (access to all websites) solely because the user cannot predict in advance which websites will contain terms they wish to highlight; this permission is used exclusively to run the local text-matching function, the right-click "Add to list" action, and the scope quick-add controls described above, and for no other purpose.

1. Notifications
   When enabled by the user, Highlight can alert the user when a configured term is detected on the page currently being viewed, or when text has been added to a list via the right-click action described in Section 5. Depending on the user's own preference, this alert is shown either as the browser's native notification, or as a custom, in-page notification ("toast") rendered directly within the webpage by the Extension itself, optionally accompanied by a short sound effect bundled with the Extension. These bundled sounds are static audio files included with the Extension; they are not downloaded, streamed, or fetched from any external source at any point. In all cases, notifications are generated and displayed entirely on the user's device. No notification content, and no information about what triggered a notification, is transmitted to the developer or to any third party.
2. Data Sharing and Third-Party Disclosure
   The developer does not share, sell, rent, lease, or otherwise disclose any Extension Data or Page Content to any third party, including advertisers, analytics providers, or data brokers, because this information never leaves the user's own browser through the Extension. The Extension does not integrate any third-party analytics, advertising, or tracking software development kits (SDKs).

The Extension does provide two optional, user-initiated ways for a user to move Extension Data outside their own browser: exporting some or all of their configuration to a file saved locally on their own device (which they may then transfer or store however they choose), and generating a Shared Configuration Code for a single list, word rule, or combination rule that they may choose to copy and send to another person. Both actions are performed entirely by the user, occur outside of the Extension's own operation once initiated, and are not transmitted through, processed by, or visible to the developer at any point.

Import review. When a user imports a previously exported configuration file, the Extension displays an on-device review screen before any data is applied, showing what will be added, changed, or (if the user has chosen to replace rather than merge their existing configuration) removed. This review, and the import file itself, are processed entirely within the user's browser and are never transmitted to the developer.

1. Legal Basis for Processing (GDPR)
   To the extent any processing described in this Policy constitutes "processing" of Personal Data under the GDPR, such processing is limited to on-device functionality necessary to perform the Extension's core service to the user, and is carried out on the basis of the user's affirmative act of installing and configuring the Extension (Article 6(1)(b), performance of a service requested by the user). Because the developer does not receive, store, or otherwise process any such data on developer-controlled infrastructure, the developer does not act as a data controller or data processor with respect to Extension Data or Page Content.
2. Data Retention and Deletion
   Extension Data persists in Local Storage until one of the following occurs:

The user deletes a specific list, folder, word rule, combination rule, or setting from within the Extension's interface.
The user clears the Extension's storage through their browser's site/extension data settings.
The user uninstalls the Extension, which removes its locally stored data from the browser in accordance with the browser vendor's standard uninstall behavior.
Because the developer never receives a copy of Extension Data, there is no developer-held copy to delete upon a deletion or uninstall request; deletion is immediate and total from the developer's perspective, as no such copy ever exists.

1. Your Rights
   Because Highlight does not collect or hold Personal Data on developer-controlled systems, most data-subject rights (access, rectification, erasure, portability, and objection) are exercised directly by the user within the Extension's own interface or through their browser's settings, rather than through a request to the developer. Users who believe the Extension is processing their data in a manner inconsistent with this Policy may contact the developer as described in Section 15.
2. Children's Privacy
   Highlight is not directed to children under the age of 13 (or the equivalent minimum age under applicable local law) and does not knowingly collect Personal Data from children, consistent with the fact that it does not knowingly collect Personal Data from any user, of any age.
3. International Users
   Because Extension Data is stored locally within the user's own browser and, where applicable, synced only through the user's browser vendor's account infrastructure, no cross-border transfer of Extension Data to the developer occurs. Users located outside of the developer's home jurisdiction may be subject to their browser vendor's own data-transfer practices, which are governed by that vendor's separate privacy policy.
4. Security
   The developer maintains reasonable administrative and technical safeguards appropriate to an extension that does not collect or transmit user data, including maintaining no developer-operated data stores for Extension Data or Page Content, and minimizing the Extension's requested permissions to those strictly necessary for its stated functionality. Users remain responsible for the security of their own browser profile and account credentials, which govern access to their synced Extension Data.
5. Changes to This Policy
   The developer may update this Policy from time to time to reflect changes in the Extension's functionality or in applicable law. Material changes will be reflected by an updated "Last Updated" date at the top of this Policy. Continued use of the Extension after any such update constitutes acceptance of the revised Policy.
6. Contact
   Questions, concerns, or requests regarding this Policy or the Extension's data practices may be directed to the developer through the support contact listed on the Extension's Chrome Web Store listing page.