JW Web Add-on Privacy Policy

How the Add-on handles information

The Add-on uses information only to provide enabled features and actions you choose. In this policy:

• Processed locally means that the Add-on uses information on your device without including it in a server request.
• Stored locally means that information remains in browser extension storage or storage belonging to a supported JW website.
• Server request means an Internet request made by the Add-on or browser to obtain or open content. Information included in a server request is sent to the receiving server.

Local access to webpage information does not by itself send that information to JW PubMedia One or another server. The sections below identify what can be accessed, stored, or included in server requests.

Supported JW services and webpage access

The Add-on's persistent page features can access webpage information only on these three supported JW websites:

• JW.ORG® at www.jw.org
• Watchtower ONLINE LIBRARY™ (WOL) at wol.jw.org
• JW Stream at stream.jw.org

In this policy, supported JW services means these websites, servers used to provide their content and functionality, and the JW Library® app where relevant. Page access remains limited to the three websites listed above.

This Privacy Policy covers only the Add-on's handling of information. The privacy practices of supported JW services, browsers, extension stores, content-delivery providers, and other receiving applications apply to their own handling of information.

Information the Add-on uses

Depending on the page, enabled feature, and action, the Add-on can access and use:

• the current supported-page URL, route, language, and page state;
• publication, document, issue, media, track, and language identifiers;
• visible text, headings, links, tables, images, alternative text, and page structure;
• selected text and related links;
• search terms, dates, paragraph numbers, timestamps, and identifiers that you enter or select;
• media titles, source and subtitle URLs, duration, playback position, and play or pause state;
• transcript and subtitle text for the current media;
• display, appearance, width, subtitle, table, and feature preferences;
• temporary browser or operating-system family, touch capability, color-scheme preference, viewport, screen, and window dimensions or position needed for an enabled feature; and
• temporary interaction signals such as scrolling, pointer or layout position, clicks on Add-on controls, page focus or visibility, and media keys used while the player is focused.

Unless described under Information stored on your device or Server requests, this information is temporary. Browser, device, and interaction signals remain local and are not retained or sent as an activity log. The Add-on does not read the browser's global history database or clipboard contents.

Why this information is used

• Page and interface enhancements. Relevant page information and preferences are used to change presentation or provide enabled controls.
• Searches, citations, and links. URLs, language, identifiers, selected text, search input, paragraphs, and timestamps are used to prepare searches, citations, navigation, and JW.ORG or WOL links.
• Publication, transcript, and media tools. Content and media identifiers are used to check availability and provide media, transcript, subtitle, and related tools. Transcript text and transcript searches are processed locally and are not placed in persistent Add-on storage.
• Playback-resume history. Eligible media identifiers, language, playback position, and update information are used to resume playback and are stored as described below.
• User-directed outputs and displays. Selected text, generated links, QR codes, transcripts, images, media sources, and player state are used to prepare clipboard content, files, JW Library links, or separate-display output.

Limited browser-context checks

• When you open the toolbar Control Panel, the browser can provide the active tab's full URL, including on an unsupported website. The Add-on uses it only to determine the hostname and applicable controls; it does not store or include the URL in a server request, read the unsupported page's content, or activate page features there.
• During a Control Panel feature change or one-time settings migration, the background process can temporarily read the tab IDs and full URLs of open tabs matching the three supported JW websites. It uses them only to revalidate or reload affected tabs and does not store or include them in a server request.
• For internal message validation, the background process can temporarily receive the sender page URL and extension ID. It can also receive a WOL tab's private- or incognito-context status so that enabled appearance controls do not use their persistent label cache. That status is neither stored nor included in the label request.

Other organization services and authenticated information

Outside the three supported JW websites, the Add-on has no persistent page access and no feature designed to read page content, credentials, account records, congregation or Bethel records, documents, or files from JW Hub, JW Documents, JW Drive, JW Event, Bethel Service, HuB, Builder's Assistant, and all other services by the organization. The limited Control Panel URL and hostname check described above can still occur when one of those services is the active tab.

JW Stream may operate with an existing browser session. Enabled JW Stream features can process media and player information on that supported page, but the Add-on does not deliberately read usernames, passwords, authentication codes, or website session-cookie values.

Functional-consent cookie

The Add-on does not request the browser cookies permission or create, change, or delete website cookies. For consent-dependent features, it checks whether the current supported JW website has set its functional-consent marker.

A browser fallback can momentarily make other script-readable cookie values from the same website available during that check. The Add-on tests only for the functional-consent value and does not deliberately select, store, log, or include other cookie values in a server request.

Information stored on your device

Browser extension storage

The Add-on stores feature switches, state needed to apply those switches reliably, and a cache of public interface labels used by WOL appearance controls. When the appearance setting follows the system appearance, its mode and extension-local label cache can operate without website functional consent while those controls are enabled. These settings remain until you change them or the browser removes the Add-on's extension data.

Temporary recovery information is removed after the related operation completes, although it can survive a browser background-worker restart long enough to finish recovery.

Supported JW website storage

The browser keeps JW.ORG and WOL website-origin storage separate. The Add-on can store:

• Interface preferences: appearance, layout, content-display, subtitle, and other interface choices. They have no fixed expiry, and a later choice can overwrite an earlier value.
• Public interface labels: localized labels used by Add-on controls. They can be refreshed periodically; old cached bytes can remain until later cleanup.
• Playback-resume history: when a related feature is enabled, eligible, and allowed by JW.ORG functional consent, the media ID, language or locale, playback position, update time, and technical management information. Progress can update approximately once per second while eligible media plays.

This history does not store general browser history, an account ID, transcripts, or selected text, and it has no automatic age, completion, or item-count expiry. Use the available watch-history clearing control while the related feature is available or clear JW.ORG site data to remove it.

Storage on a supported JW website is not private extension storage. Scripts with access to that website's storage can technically access the same area, but that possibility does not establish that the website reads or transmits Add-on-created values.

Temporary and user-managed information

Page-working information, selected text, metadata, transcripts, subtitle cues, server responses, generated links, and temporary access tokens for supported JW services remain in memory only as needed unless this policy states otherwise. Clipboard contents, downloaded files, browser download records, and browser-managed caches remain under the control of you, your browser, operating system, and applications.

Local browser coordination

Playback-resume history uses temporary browser-only messages to coordinate open JW.ORG tabs. They can contain an action, temporary random tab identifier, media identifier, timestamp, and, when progress is saved, locale and play state. WOL appearance controls use a local event in the current page for their mode, effective appearance, save availability, and feature state. These communications stay in browser memory and are not server requests, but scripts on the supported page may technically be able to observe them.

Functional consent and feature controls

Features may be enabled or disabled by default, and their defaults can change between Add-on versions. The Control Panel shows each feature's current setting and lets you change it. An enabled feature can operate on eligible supported pages as described in this policy.

The Control Panel switch and a supported JW website's functional-consent setting serve different purposes:

• Feature switch: turning a feature off makes it dormant but does not delete its stored information.
• Website-specific consent: JW.ORG and WOL consent are evaluated separately. JW Stream currently has no whole-feature functional-consent gate.
• Page-load decision: consent is evaluated for the current page. After a website consent change, refresh the page or open a new one before relying on the change. Until then, an already-running feature can continue its local processing, server requests, and storage updates, including playback-progress updates. After refresh, a feature that depends entirely on functional consent becomes dormant, but its stored information remains.

Some enabled features require the current website's functional-consent marker before they operate. Other enabled features can operate without that marker as disclosed in this policy.

The narrower exceptions are:

• A system-following WOL appearance mode and its extension-local label cache can operate without website functional consent while the related controls are enabled.
• After consent is denied and the page is refreshed, a saved manual WOL appearance choice remains stored but is not read or updated by those controls.
• For features that do not depend entirely on functional consent, some public labels can be requested temporarily without consent, but reading or writing their website label cache requires allowed consent.

The Add-on does not create an account-linked consent record, consent timestamp, policy receipt, or Add-on user ID.

Server requests

A server request can ordinarily reveal the requested path or content together with transport information such as your IP address, date and time, and browser characteristics. The receiving server may retain logs or otherwise handle the request under its own privacy practices.

Supported JW services. Requests can go to supported JW services, including servers under jw-cdn.org, to obtain public labels, links, publication or media availability, media metadata, transcripts, subtitles, fonts, or an image selected for download.

These requests can include a language or locale, publication, document, or media identifier, requested format or path, supported origin, and a temporary access token when required. Label, availability, duration, metadata, or transcript requests can occur automatically on an eligible page when the relevant feature is enabled. Image downloads and some link requests follow your action.

User-directed navigation. The Add-on can open Add-on product or legal pages, as well as search, article, paragraph, date-based item, publication, library, media, or finder destinations, after you choose the action. A destination URL can contain a submitted search, selected date, language, paragraph, timestamp, or content identifier. Opening an Add-on product or legal page sends ordinary navigation information to the JW PubMedia One website.

Browser-managed content. An enabled feature can cause the browser to load an image, poster, media source, placeholder, or content in a separate-display window from a supported JW service. Browser-managed requests and navigation can use cookies, session state, referrers, caches, or other browser-controlled information.

Google Fonts. When the Control Panel opens, it can request a fixed stylesheet and related font files from Google Fonts if browser security rules permit. The Add-on does not add settings or content identifiers to these requests, but Google can receive ordinary request information and apply its own cookie, caching, and retention practices.

Server requests made directly by the Add-on generally omit browser credentials. A temporary access token remains in memory and is sent only to the supported JW service that requires it. The Add-on does not deliberately send a JW username, password, or website session cookie in those direct requests.

Selected text, transcript text, locally stored playback-resume history, Add-on preferences, clipboard content, and generated files are not included in server requests unless you choose an action that sends an output or places information in a destination URL.

Clipboard, files, links, and other applications

When you choose the relevant action, the Add-on can:

• write selected text, rich text, a citation, transcript content, or a JW.ORG or WOL link to the clipboard;
• create a QR-code image, transcript text or PDF file, or watermarked image file on your device;
• open a generated JW.ORG or WOL link; or
• give a JW Library link to your operating system so it can open the app.

Writing to the clipboard or creating a file is not a server request. If you later paste, upload, send, open, or share an output, that action can disclose it to the recipient you choose.

When a separate-display feature is enabled and you select its control, it opens a local browser window, coordinates the selected media, and can load the current media, image, poster, or fallback content from a supported JW service.

Analytics, advertising, sale, profiling, and tracking

The Add-on does not contain a client mechanism that:

• sends Add-on activity to JW PubMedia One for analytics, telemetry, or remote crash reporting;
• displays or measures advertising;
• sells Add-on information or provides it to data brokers;
• creates an advertising or behavioral profile;
• tracks activity across unrelated websites; or
• uploads locally stored playback history as an analytics feed.

The Add-on does not create a JW PubMedia One account, another Add-on account, or a persistent Add-on user identifier. Errors or manually enabled debugging information can appear in the browser's local developer console. These statements do not prevent receiving servers from keeping the ordinary logs described above.

Your choices and deletion

You can:

• turn individual features off in the Control Panel;
• disable or uninstall the Add-on through browser settings;
• use an available watch-history clearing control while the related feature is available;
• clear JW.ORG or WOL site data to remove Add-on-created preferences, label caches, and playback-resume records in that website's storage;
• clear the Add-on's extension data through browser extension or profile controls where available;
• clear browser caches and download history; and
• delete downloaded files or overwrite or clear clipboard contents.

Turning a feature off or withdrawing functional consent does not automatically delete stored information. There is no single Add-on control that clears every local, browser-managed, and user-managed category.

Your browser controls when extension storage is removed after uninstall. Uninstalling does not guarantee deletion of storage belonging to a supported JW website, browser caches, clipboard contents, download records, downloaded files, or information already given to another application; clear those categories separately if desired.

Browser permissions and data security

The Add-on uses:

• storage for feature settings, feature-control state, and public interface labels;
• activeTab for the temporary Control Panel URL and hostname check;
• scripting to enable or disable packaged scripts used by certain early-page appearance and layout features according to their saved settings; and
• clipboardWrite for user-invoked copy actions.

Page-feature host access is limited to the three supported JW websites listed above. The Add-on also has browser permission for cms-imgp.jw-cdn.org only so its background image-download fallback can retrieve an image you select; that host is not a page-feature target.

The Add-on does not request permissions to read the clipboard, manage website cookies or browser downloads, or read global browser history.

The Add-on relies on browser security controls, limited host access, HTTPS, and browser-managed storage. It does not separately encrypt browser storage, and security also depends on your browser, device, and each receiving server.

Children's privacy

The Add-on does not ask for a user's age or for information identifying a user as a child. JW PubMedia One does not knowingly collect or use children's personal information through the Add-on and does not need that information to provide the Add-on's features.

Changes to this policy

We may update this Privacy Policy when the Add-on's information handling, recipients, or privacy practices change. The revised policy will show its effective and last-updated dates. Applicable law or platform requirements may require additional notice or consent.