Extension Privacy Disclosure — $://THeXTeNSioN

1. Single purpose

Turn the #, @ and $ tags already written on a page into CNXT linx, and let the reader cnxt the page they are on to the linx that owns its tag — once, deliberately, by pressing the CNXT mark.

Everything below follows from that one purpose. Anything the extension does not need for it, it does not do.

2. What runs on every page, and what it reads

The content script runs on http and https pages at document idle, and from that moment it does read the page. It walks the page's text looking for #, @ and $ tags, rewrites the ones it finds into CNXT links, and draws the CNXT mark in the bottom-right corner. A page that keeps loading content keeps being re-read the same way, because tags arrive with the new content.

That reading is local, and reading is not the same as reporting. Nothing is sent, nothing is written to your disk, and no record of the page is created — at CNXT or on your own device — by the extension being present on it. The extension does not keep a list of the pages it has scanned, and does not tell CNXT it was there.

Sending is a separate, deliberate step. Nothing about the page goes to CNXT until you press the mark, and the press has to be a real one: a click the browser marks as user-generated. A script on the page cannot trigger a capture.

3. What leaves your browser when you press the mark

• The page's address, and its title.
• An excerpt of the page's visible text, whitespace-collapsed and cut at 2,000 characters. Only text that is visible — nothing hidden, no form fields, no values you have typed.
• One number: the length of the page's HTML source. The HTML itself is never sent.
• The document's declared language, when the page declares one.
• Up to 24 distinct tags found on the page, each with the number of times it occurs.
• Nothing else. No cookies, no passwords, no storage belonging to the site, no keystrokes, no scroll or mouse activity, no other tab, and no page you did not press the mark on.

4. What the extension does on its own

• Every five minutes it reads one public figure from CNXT — how much of the network's mining allocation is still cnxtable — and caches it for the toolbar badge. That request carries no information about you or the pages you are on.
• When you open the popup it reads your own mining position: your tag count, capture count and accrued earnings.
• Requests to CNXT are sent with credentials, so your browser attaches the CNXT session you are already signed in with. That is how a capture reaches your wallet and not someone else's. The extension itself never reads or stores a cookie, token or password, and contacts no host but the CNXT origin it was built against.
• The only thing the extension stores on your device is that cached allocation figure, in session storage, which the browser clears when it closes.

5. What CNXT keeps when you cnxt a page

A capture is not taken on trust. The CNXT server fetches the address you sent, anonymously and without your session, and checks that the tags really do appear on the page. When the server can read the page, the title and excerpt it read itself replace the ones your browser sent, and the capture is recorded against the address the server actually reached.

On X, TikTok, YouTube and Reddit the page itself answers an anonymous reader with a login wall or an empty shell, so for an individual post there the server reads the platform's own public record of that post instead — the same keyless record an embed reads (X's and TikTok's oEmbed, the description on the YouTube watch page, Reddit's public post listing) — still anonymously and still without your session, and checks the tags against the post's own text. The title and excerpt kept, and the address the capture is recorded against, are then the ones that record served; profile pages, feeds and search pages on those platforms have no such record and are read like any other page.

When the server cannot reach the page — it is private, behind a login, or blocked to it — the title and excerpt from your browser are kept instead, and that capture stays unverified. Unverified captures are never published and are never paid; they are visible only to CNXT and to you.

• Stored per capture: the address, a SHA-256 hash of it used to recognise a repeat, the host, the title, the text excerpt, the HTML length, the language, the tag occurrence count, the amount paid and its state, whether it verified, and when it was mined.
• Stored alongside it: your CNXT account identifier, because a payment has to have a payee.
• Not stored: any page you did not cnxt, and any content beyond the fields listed above.

6. What becomes public

A verified capture is published on the public page for the tag linx it belongs to: the host, the page title, the text excerpt and the time it was mined. That is the point of the rail — a linx is worth something because it carries real pages.

Your identity is not part of that. The public tag page shows how many captures a linx holds and how many distinct miners contributed, and never who they are. No CNXT account identifier is exposed on any public extension surface.

7. Why you are paid, and what the payment is for

A capture that verifies pays the per-capture amount set on the network's mining allocation, credited to your CNXT wallet as issued network capital — spendable across CNXT, not withdrawable. Paid captures are capped per hour, both per miner and per source domain; captures beyond a cap are still recorded, marked as such, and paid nothing.

The payment buys one thing: the 1-of-1 tag linx and the page attached to it. It is not a rating of the page, its owner, or its author.

8. What is never measured

• No browsing history. A page you visit and do not cnxt leaves no record.
• No traffic measurement. The extension does not count visits, sessions, or time on a page.
• No reputation or authorship scoring. CNXT does not measure who wrote a page or how well it is regarded, and pays no attention to either when it pays for a capture.
• No profiling, no advertising, no analytics vendor, and no model provider anywhere in the capture path. A capture goes to the CNXT origin and nowhere else.
• CNXT's own web pages — the mining console at /xtension/, the /thextension landing page and this page among them — carry the site analytics described in the Privacy Policy. That tag lives in the web page, never in the extension, and never sees a capture.
• No use of anything captured for creditworthiness, underwriting, or lending.

9. Every access the extension asks for, and why

These are the justifications filed with the Chrome Web Store listing, rendered here from the same module the extension build validates the manifest against — so the listing, the manifest and this page move together or the build fails. The list covers more than the store's form asks about: anything in the manifest that widens what the extension can reach, or what a page can reach in it, is justified here too.

• storage — Caches one number. The service worker keeps the network's currently cnxtable $://USD allocation in chrome.storage.session so the toolbar badge and the popup can show it without re-reading it on every open. Session storage is cleared when the browser closes. No page content, no list of pages, and no account data is ever written to extension storage.
• alarms — Keeps that one number from going stale. A Manifest V3 service worker is shut down when idle, so a five-minute chrome.alarms schedule is the only way to re-read the public allocation figure. The alarm fires one request to the CNXT allocation endpoint and touches no tab and no page.
• Host permission — the CNXT API origin (substituted at build time) — The extension talks to exactly one host: the CNXT API origin this build was made against. It makes three requests — the public allocation read, the signed-in miner's own position for the popup, and the capture the user triggers by pressing the CNXT mark. Sending the capture from the service worker rather than the page keeps it clear of the visited site's content security policy and keeps the visited site from ever reading the response. No other host is contacted.
• Content script on http://*/* — Tags are written on any site, and which sites carry them cannot be known in advance, so the content script has to be able to run anywhere. What it does everywhere is local: on load, and again as a page streams in new content, it reads the page's text in the browser to find #, @ and $ tags, rewrites them into CNXT links, and draws the CNXT mark. That reading never leaves the page — nothing is sent anywhere, and no record of the page exists, until the user makes a real (isTrusted) click on the mark. Only then does the current page's address, title, a visible-text excerpt capped at 2,000 characters, a single number for the length of the page's HTML source, the document language, and up to 24 distinct tags with their occurrence counts go to CNXT. The HTML itself is never sent.
• Content script on https://*/* — Same single purpose and same behaviour as the http match: tags appear on sites of every kind, so the script must be able to run on any page. It reads the page's text locally to link the tags it finds, and that reading stays in the browser until the user presses the CNXT mark on the page they want to cnxt.
• Web-accessible resource — icons/* — The CNXT mark the content script draws on the page renders the extension's own icon, so the icon files have to be loadable by the page. Only the icons are exposed. Nothing else in the bundle is reachable from a page, and exposing a file to a page grants the page nothing except the ability to display it.
• Web-accessible resource scope — http://*/* — The mark is drawn on the same pages the content script runs on, so its icon has to be loadable there. The scope of the exposure matches the content-script scope exactly and covers nothing the script does not already run on.
• Web-accessible resource scope — https://*/* — Same as the http scope, for the same reason: the mark's icon must load on any page the content script draws the mark on, and the exposure reaches no further than that.

10. Permissions deliberately not requested

A permission the extension does not need is a permission it does not ask for. Each of these is fenced by the same build check: re-adding one fails the build until it is justified, whether it is added as a required permission or an optional one.

• activeTab — Nothing in the extension reads a tab. The content script is declared statically against its match patterns, and the only tab call is chrome.tabs.create, which opens the console and needs no permission.
• tabs — The extension never enumerates tabs or reads their URLs; it only ever sees the page whose mark was pressed.
• scripting — No code is injected at runtime — the content script is declared in the manifest.
• history — Browsing history is never read.
• cookies — The extension never reads a cookie. Requests to the CNXT origin are sent with credentials so the browser attaches the CNXT session the user is already signed in with; the extension cannot see it.
• webRequest — No traffic is observed, intercepted, or modified.
• downloads — Nothing is downloaded.

11. Chrome Web Store data-use disclosure

The store's categories, answered in its own vocabulary. Where an answer is yes, the detail behind it is stated rather than summarised.

• Website content — collected. The content script reads the page's text locally, in your browser, to find and link the tags on it; that reading is never transmitted and never recorded. What is collected is what you send by pressing the CNXT mark, and only then: the page's address and title, a visible-text excerpt capped at 2,000 characters, a single number for the length of the page's HTML source, the document language, and up to 24 distinct tags with their occurrence counts. The HTML itself is never sent.
• Web history — collected. Disclosed because the address of a page you cnxt is stored against your account. The extension does not read, collect, or report the pages you merely visit — a page leaves no record unless you press the mark on it.
• Personally identifiable information — collected. Disclosed because each capture is stored against your CNXT account identifier — that is how the per-capture payout reaches your wallet and no one else's. No name, address, email, age, or any other identifier is read from the page or from the browser.
• Authentication information — not collected. Requests to CNXT are sent with credentials, so the browser attaches the CNXT session you are already signed in with. The extension never reads, stores, or transmits a password, token, or cookie itself, and never sends credentials anywhere but the CNXT origin it was built against.
• Financial and payment information — not collected. The payout is credited inside CNXT to the account you are signed in as. No card, bank, or payment data is read by the extension.
• User activity — not collected. No clicks, keystrokes, scrolling, mouse position, or network monitoring. The one interaction that is ever recorded is your deliberate press of the CNXT mark, and it is recorded as the capture it creates.
• Personal communications — not collected. Nothing is read from mail, messaging, or any other communication surface beyond the visible text of a page you choose to cnxt.
• Location — not collected. No geolocation, and no location inference from the browser.
• Health information — not collected. Never requested and never derived.
• The data is not sold or transferred to third parties, outside of the approved use cases. Captures go to the CNXT origin and nowhere else. There is no analytics vendor, no advertising network, and no model provider in the capture path. Captures the CNXT server could verify by reading the page itself are published on the public tag linx page — host, title, excerpt, and time — which is the point of the rail and is disclosed in full on the privacy page. The identity of the miner is never published with them.
• The data is not used or transferred for purposes unrelated to the extension's single purpose. A capture exists to attach a page to the tag linx that owns its tag and to pay the miner for it. It is not used to build a profile, score a site, or measure traffic, reputation, or authorship — the network measures none of those things.
• The data is not used or transferred to determine creditworthiness or for lending purposes. No capture field reaches any lending, underwriting, or credit-scoring surface on the network.

12. How you stop

• Do not press the mark. Nothing is captured without a deliberate press, and pages you read are never reported.
• Sign out of CNXT. The capture endpoint refuses an unauthenticated request outright, and nothing is recorded.
• Disable or remove the extension from chrome://extensions. Removing it also clears the one value it keeps on your device, the cached allocation figure.

13. How you delete what you have already cnxtd

There is no self-service delete control in the extension today, so deletion is handled as a request: raise it through Your Account and the privacy team at $://THeCeNTRaLDesK will action it. Say whether you want particular captures removed or all of them.

What is removed: your capture records and the page content stored with them — the address, title, excerpt and language — including anything of yours published on a public tag page.

What survives, and why: the tag linx itself, which is a network entity rather than a record about you and carries none of your content once your captures are gone; and the settlement entries recording that a payment was made to your wallet, which are financial records CNXT has to keep and which carry no page content.

14. Changes and contact

Material changes to what the extension reads or sends will change this page and the version of the extension that does it, together. The date at the top of this page is the date of the last change.

Privacy requests and questions about this disclosure can be raised through Your Account and are handled by the privacy team at $://THeCeNTRaLDesK. This disclosure covers the browser extension specifically and sits under the network Privacy Policy; it is provided for transparency and is not a substitute for independent legal advice.