Privacy Policy

WEB // CRYPT Browser Extension

Effective Date: September 28, 2026

Plain-language summary. WEB // CRYPT sends exactly one piece of data off your device: the web address (URL) of a page you explicitly choose to seal, transmitted to the archive server you have configured. It sends that address only at the moment you click the toolbar button, choose the right-click menu item, or press the keyboard shortcut. The extension collects nothing in the background, does not read your browsing history, does not read the content of your pages, uses no analytics or tracking of any kind, and shares nothing with third parties.

This policy describes how the WEB // CRYPT browser extension handles information. It is written from what the software actually does, and every statement in it is meant to be checked against the extension's code and network traffic rather than taken on trust.

Operator. Net Works Lab LLC, a limited liability company organized under the laws of the State of Wyoming, United States, with its principal office at 30 N Gould St, Ste R, Sheridan, WY 82801.

Scope. This policy applies to the WEB // CRYPT extension for Chromium browsers (Chrome Web Store item pgmakibjlgoldolakfidghkghoankicp). It is a separate document from the general Net Works privacy policy that covers the company website and our other services. Where the two differ as to the extension, this document governs.

1. What the Extension Collects and Transmits

When, and only when, you invoke a seal, the extension sends a single request to the crypt server configured in its options. That request contains:

DataSent ToWhen
The URL of the page or link you chose to sealYour configured crypt server (default: https://networks-corp.com/crypt)Only at the moment you invoke a seal
Your capture options ("wait for completion", "include outlinks")Same request, same serverOnly with a seal request
Your API key, if you have set one in the options pageYour configured crypt server only, as a request headerWith each request to that server
Session cookies for the crypt server, if you have signed in to itAttached by the browser to requests to that same serverWith each request to that server

That is the complete list. The seal request is the only data-bearing transmission the extension makes; the extension also calls the same server's status endpoint to show you whether your crypt is reachable, and that call carries no page data.

2. What the Extension Does Not Collect

3. How the Data Is Used

The transmitted URL is used for exactly one purpose: to create the archival snapshot you requested. This is the extension's single purpose, and the data collected is limited to what that purpose requires. The URL is not used for advertising, is not sold, is not used to build profiles, and is not transferred to anyone except the crypt server you addressed the request to. This use complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

4. Where Captures Are Stored

WEB // CRYPT works like a "Save Page Now" service. After receiving the URL, the crypt server fetches the page itself, from its own network position, and stores the resulting WARC record, screenshot, PDF, and SHA-256 catalog entry in its archive. The rendered page travels from the website to the crypt server directly; it does not pass through your browser or this extension.

The archive belongs to the operator of the crypt server you use. If you point the extension at your own self-hosted crypt, your sealed pages are stored on your own infrastructure and never touch ours. If you use the default NET // WORKS crypt, snapshots are stored on Net Works Lab LLC servers under the account you sign in with, and the general Net Works privacy policy applies to that hosted service.

5. Data Stored in Your Browser

(a) Settings (the crypt server address and your optional API key) are kept in the browser's extension sync storage. If you are signed in to Chrome with sync enabled, Chrome replicates this storage across your own browsers through your Google account; that replication is performed by Chrome, not by the extension.

(b) The last seal record (snapshot ID, status, URL, and timestamp of your most recent seal) is kept in local extension storage on your device so the toolbar tooltip can show it. It is overwritten by the next seal and is never transmitted.

Uninstalling the extension removes both.

6. Consent and Control

(a) Nothing happens without you. The extension transmits data only in response to your explicit action: the toolbar button, the right-click menu item, or the Alt+Shift+S shortcut. There is no automatic or scheduled collection to opt out of.

(b) You choose the server. The options page lets you replace the default crypt with any server you control. Pointing the extension at a new host triggers a browser permission prompt, and no request is made to that host unless you grant it.

(c) Self-hosting keeps everything local. Configured against a crypt on your own machine or network, the extension sends the sealed URL only to that address, and no data of any kind reaches Net Works Lab LLC.

(d) Deleting your data. Snapshot deletion is handled in the crypt's own interface by whoever operates it. For snapshots on the hosted NET // WORKS crypt, you may also use the contact address in section 12.

7. Browser Permissions Explained

PermissionWhy the Extension Needs It
activeTab, tabsRead the address and title of the current tab, locally, so the popup and tooltip can show what would be sealed and label the result
storageKeep your settings and the last seal record, as described in section 5
contextMenusProvide the right-click "Seal this page" menu item
notificationsShow a local desktop notification when a seal completes, queues, or fails
Host access to networks-corp.comCall the default crypt API
Host access to 10.0.0.244Reach a self-hosted crypt at its standard address on a private lab network; this address is not routable on the public internet
Optional host access (any site)Requested only if and when you configure your own crypt server, limited to that server's origin, and only after you approve the browser's permission prompt

8. Third Parties

The extension embeds no third-party code, calls no third-party services, and sells or shares no data with anyone. The only network endpoint it contacts is the crypt server you configure. The default hosted crypt at networks-corp.com is served through Cloudflare, which acts as network infrastructure for that site in the same way it does for any visit to it.

9. Retention

On your device, the last seal record persists until your next seal overwrites it or you uninstall the extension, and settings persist until you change them or uninstall. On the server side, snapshots persist in the archive of the crypt that captured them until removed by that crypt's operator or account holder; the extension itself retains nothing.

10. Children

The extension is a general-audience archival tool. It is not directed at children under 13, and it collects no personal information from anyone, including children.

11. Changes to This Policy

Material changes will be posted on this page with a new effective date. Because the extension has no messaging channel to you, this page is the single place to check; the Chrome Web Store listing links to it.

12. Contact

Questions about this policy and requests regarding your data may be sent to privacy@net-works-lab.com.

Net Works Lab LLC
30 N Gould St, Ste R, Sheridan, WY 82801
net-works-lab.com

Net Works Lab LLC | 30 N Gould St, Ste R, Sheridan, WY 82801 | net-works-lab.com