Nexload Browser Integration — Privacy and data use
Publisher: Neo Software Services LTD
Effective date: September 14, 2026
Full published policy: https://nexloadapp.com/privacy

Nexload Browser Integration sends supported downloads and selected links from Chrome or Firefox to the Nexload desktop app on the same Mac. This policy describes the extension and its local handoff.

WHAT THE EXTENSION HANDLES
To identify downloadable links, the extension can read the current page URL and title, link labels and URLs, selected text or visible page text containing links, and direct media sources. Full page text is processed for link discovery in the browser; it is not sent as a whole to a server.
A capture can include its URL and final URL, suggested filename, page and referrer information, file size and type, and the capture action.
For a single HTTP(S) capture, cookies matching the source URL, including authentication cookies, and request headers such as Referer and User-Agent can be passed to the app to support the requested download.
Bulk captures include URLs and page details, but no cookies or request headers.
Browser and extension identifiers, versions, capabilities and User-Agent information may be included as operational data. Available controls vary by browser and extension version, as described below.
URLs, filenames and page details may themselves contain personal information or access tokens. The extension does not access the browser's saved-password store or target payment forms. It does not load remotely hosted JavaScript.

WHERE THE DATA GOES AND WHY
The extension uses the com.nexload.app.browser local native bridge to hand accepted captures to the desktop app's local broker. The app passes accepted items into its normal download queue and contacts the relevant download servers.
If you configure Cocoleech Premium in the app, supported provider downloads use Cocoleech. Data needed for those downloads can be sent to Cocoleech and the download servers.
Local handoff does not mean that no data leaves your Mac. URLs and the cookies or request headers needed for a requested download may be used when the app contacts the source. This is part of carrying out your download, not an extension advertising or analytics service.

LOCAL STORAGE AND RETENTION
The extension stores settings, recent URL keys for duplicate suppression, and pending capture state in local browser storage. Capture-state entries expire logically and are pruned on use or background startup, rather than guaranteeing immediate physical erasure.
Local desktop queue records can retain URLs and request headers for retry and resume. Removing the extension does not delete the desktop queue or downloaded files. Use the app's queue controls to manage those records and files.
Logging uses redaction for sensitive URL details, cookies, headers and tokens, but logs may still contain a hostname, filename or local diagnostic information. Do not treat logs or diagnostic bundles as anonymous; review them before sharing them with support.

YOUR CONTROLS
Turn off Capture browser downloads to keep automatic downloads in the browser. Manual send actions remain available.
Disable browser integration in the desktop app, or disable or remove the extension, to stop handoff.
Use your browser's extension settings to manage site access and permissions.
If Nexload does not accept automatic handoff, the extension keeps the browser download or attempts to resume it there. Resume can still depend on the browser and download source.
Firefox 140 and later support built-in data-permission prompts. The prompts and choices you see also depend on the installed extension version. In Firefox builds that offer an optional technical-data choice, that choice controls sharing of browser and extension identifiers, capabilities and User-Agent information; declining it keeps capture available. Older extension builds may include these operational fields without that separate choice. Chrome includes these operational fields.

WEB REMOTE AND DIAGNOSTICS ARE SEPARATE
Installing the extension does not enable the desktop app's optional Web Remote sharing or submit a diagnostic bundle. Web Remote has its own account, license and per-device permission controls. Diagnostics are shared through the app's separate user-submitted support flow.
If you separately enable Web Remote, information about downloads in the app may be shared through that feature, including downloads you originally sent from the extension. Use the app and account controls to manage Web Remote independently of browser capture.

HOW WE USE INFORMATION
Neo Software Services LTD does not sell extension data or use it for advertising, tracking, creditworthiness or purposes unrelated to download handoff.
Our use and transfer of information received through Nexload Browser Integration adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. These commitments also apply when the accompanying Nexload app and services handle data received through the extension.

CONTACT
Nexload Browser Integration is published by Neo Software Services LTD. For privacy questions or extension issues, contact us through https://nexloadapp.com/report-a-bug. Include only the information needed to explain your question; do not include passwords, authentication cookies or access tokens.

The full policy at https://nexloadapp.com/privacy also describes desktop announcements separately. Browser-extension data is not used for desktop announcement targeting or reporting.