Browser extension
PipeLinker Desktop extension: privacy policy
The extension collects, stores and transmits no personal data. It only talks to the PipeLinker Desktop application, on the same computer, and does nothing without it. This page says what it does, what it keeps, and why it asks for each permission.
What the extension is
The PipeLinker Desktop browser extension (Chrome, Edge, Firefox) routes to the proxy (SOCKS5) opened by the PipeLinker Desktop application, on the same computer, only the addresses that the PipeLinker console has declared for that proxy. All other browser traffic goes out normally. It does nothing without the application.
Data collected: none
The extension collects, stores and transmits no personal data, no browsing history, no visited address. It has no account, uses no analytics or audience measurement service, and loads no remote code.
Who it talks to
Only the PipeLinker Desktop application installed on the same computer, through the browser's native messaging (no network), to learn the list of open proxies and their scope. Nothing is sent to Lootus Security or to any third party.
What it keeps locally
The list of open proxies and their scope, with the state of the session in the application and the name of the account that opened it, in the extension's local storage, to display them in its window. This information is cleared when the application closes or when the extension is removed.
Permissions requested from the browser, and why
- proxy: set the routing rule to the local proxy for the addresses in scope.
- nativeMessaging: talk to the application on the computer.
- storage: keep the list above.
On Firefox, the site permission is used to decide, request by request, whether the address is in scope; page content is neither read nor modified.
Publisher and contact
Lootus Security, www.lootus.net. For any question about data: contact@pipelinker.fr.
Page updated on 20 September 2026. Lire cette politique en français.