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 and for CNXT addresses written out in full (#://, @://, $://), rewrites the ones not already inside a link into CNXT links, and draws the CNXT mark at the bottom center of the window. An address is linked only. It is never counted as a tag and never sent. 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.

Hovering over a linx the extension drew, or reaching it with the keyboard, opens a small CNXT card beside it: the linx's address, a link to open it, a #://FiNDR link that searches it on CNXT and, for a tag, a link to the tag's page at its #://XPLR map and a Look up button (section 4). An address's card offers opening it and #://FiNDR only. Opening a card sends nothing: its links are ordinary links that lead nowhere until you follow one. The switch in the popup turns the cards off, and every open tab follows it at once.

A tag that the downloaded cnxtd-tag list (section 5) shows has no verified cnxt yet is drawn with a dashed blue underline instead of the solid red one, its card says "no verified cnxt yet" with the time the list was read, and the mark says how many of the page's tags are in that state. The comparison runs in your browser, against the list already on your device; nothing about the page is sent for it. When the list is missing, more than three hours old, or flagged by CNXT as not covering every cnxtd tag, no tag is drawn that way: a tag whose standing is unknown is never shown as never-cnxtd.

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 32 distinct tags found on the page, each with the number of times it occurs.
• On a search, hashtag, profile or feed page of X, YouTube, TikTok, Reddit, Instagram, Facebook or LinkedIn, or a Google results page, less than that: for each post or result on screen that carries tags, at most 32 per press, sent one after another, only its own address, the tags found inside it with their counts, and the page's declared language. The listing page's own address, title and text are not sent.
• 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 leaves your browser when you press Look up

• Look up is on a tag's card only, and only a real press sends anything: a click the browser marks as user-generated. Hovering over a linx, focusing it or opening its card sends nothing, and a script on the page cannot press Look up for you.
• What is sent: the tag itself — its sigil and its name. Not the page's address or anything else about the page, not your sign-in, no cookies and no referrer. Like any request, it arrives from your connection's IP address, which CNXT uses to cap how many look ups one connection can make in a minute.
• What comes back is the tag's public standing, the same figures its public tag page shows: its status, its verified cnxts and miners, when it was last verified, the operator's storefront when there is one, and its verified cnxts per platform. The card shows them as plain text. A read that fails says so, and nothing is shown in its place.
• The extension keeps an answer in memory for a minute, so pressing Look up on the same tag again does not ask again. It is not written to your disk.

5. 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.
• About once an hour, and when the browser starts or the extension is installed or updated, it downloads the public cnxtd-tag list from CNXT: every tag with at least one verified cnxt, and the time the list was read. The request carries no cookies, no sign-in, no referrer and nothing about you or the pages you are on; like any request, it arrives from your connection's IP address, which CNXT uses to cap how often one connection can ask. When the list has not changed since the last download, CNXT says so and the list is not sent again. The list is kept on your device for the marks described in section 2.
• When you open the popup it reads your own mining position: your tag count, capture count and accrued earnings.
• Requests that act for you — reading your position, sending a capture, disconnecting — say who you are. Once you have connected your account they carry the extension's own sign-in token, with cookies left off; until then they 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 allocation read is sent with credentials too. The cnxtd-tag list download and Look up carry neither a token nor a cookie.
• The sign-in token is issued by the CNXT site when you connect your account. It works only on the extension's own requests, is sent only to the CNXT origin, and is deleted from your device when you disconnect or when CNXT stops accepting it; CNXT keeps only a one-way hash of it. The extension never reads or stores a cookie or a password, and contacts no host but the CNXT origin it was built against.
• What the extension stores on your device. In session storage, which the browser clears when it closes: the cached allocation figure, whether this browser is connected to an account together with your wallet's address and balance as last read, and, while you are connecting, the one-time code that pairs the connect tab with the extension. In local storage, which stays until you remove the extension: the sign-in token once you connect, the cnxtd-tag list with when it was read and last checked, and the setting of the card switch once you change it. None of it is about the pages you visit: no page content and no list of pages is ever written to extension storage.

6. 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.

When a capture verifies, the server also keeps what that same anonymous read says about the post on the page — its post facts. They come only from the server's own read, never from anything your browser sent: the creator as the page itself shows them (a display name, a handle, or both), when the post was published, what kind of page it is (a video, post, article, image, listing or page), a video's length, its views, likes or score, and comments as the page showed them when it was read, the page's language, and how many times the tag appears in what the server read. A fact the read does not return is left empty; it is never guessed, and an unknown count is never shown as zero.

Captures that verified before post facts were kept are read again in the background, the same anonymous way and at a slow pace, to fill their facts in. That read writes the facts and nothing else: whether the capture verified, what it paid, and its title and excerpt stay exactly as they were. A page that can no longer be read is tried a few more times over the following days and then left without facts. Only the latest read is kept; CNXT keeps no history of a post's counts.

• Stored per capture: the address, a SHA-256 hash of it used to recognise a repeat, the host, the site the page belongs to (its registrable domain, such as youtube.com), the title, the text excerpt, the HTML length, the language, the tag occurrence count, the amount paid and its state for each of the two halves (network and owner), whether it verified, and when it was mined.
• Stored per verified capture: its post facts as described above, the time the server read them, and how many reads to fill them in have been tried.
• 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.

7. What becomes public

A verified capture is published on the public page for the tag linx it belongs to: the host and the site, the page title, the text excerpt, the time it was mined, and its post facts — the creator as the page shows them, when the post was published, its type, a video's length, its views, likes or score, and comments with the time they were read, the page's language, and the tag's mention count. That is the point of the rail — a linx is worth something because it carries real pages.

Every verified capture of a tag can be listed, newest first, a page at a time — and so can every verified capture of a word, its #, @ and $ tags together — narrowed by platform, site or sigil. Each tag and each word also has public activity figures: its verified cnxts per day and per week, its total mentions, the languages of its pages, and its top sites.

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, and no list, figure or activity count says which miner made a capture.

A creator appears only as their own page shows them: the name or handle the page itself publishes, on the capture of that page. CNXT does not rank creators, list them, or publish figures about them.

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

A capture that verifies pays up to 12¢, in two halves judged on their own. The network half, the per-capture amount set on the network's mining allocation, is credited to your CNXT wallet as issued network capital — spendable across CNXT, not withdrawable. The owner half comes from the tag tranche the owner-operator of the edition operating the tag funds with legal tender, and arrives in your CNXT wallet as settled money, withdrawable after the 10-day cash-out hold; a tag no owner-operator funds pays only the network half. No miner is paid more than a tenth of any one tag tranche; past that share, a capture's owner half is 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.

9. 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. A post's creator and its counts are kept only as the page itself shows them (section 6); CNXT does not score or rank pages or creators by them, 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.

10. 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 — Session storage, which the browser clears when it closes, holds the network's currently cnxtable $://USD allocation, so the toolbar badge and the popup can show it without re-reading it on every open, along with whether this browser is connected to an account and the one-time code of a connect in progress. Local storage holds three things. First, once you connect your account, the extension's own sign-in: an extension-only token issued by the CNXT site, kept so the extension stays signed in, and deleted when you disconnect or when CNXT stops accepting it. Second, the public cnxtd-tag list (every tag with a verified capture, and when the list was read), downloaded about hourly so the content script can mark the tags no verified capture has reached yet without sending anything about the page. Third, the popup's on/off setting for linx cards, which every open tab follows. No page content and no list of pages is ever written to extension storage.
• alarms — Keeps two public reads 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, and the same alarm checks whether the public cnxtd-tag list is due its hourly download. Each run sends at most those two requests to the CNXT origin 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 its requests only there — the public allocation read, the public cnxtd-tag list download, the signed-in miner's own position for the popup, the capture the user triggers by pressing the CNXT mark, the Look up the user triggers by pressing it on a tag's linx card (that one tag, sent with no cookies, no sign-in and no referrer), and disconnecting its own sign-in when you ask. 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 and CNXT addresses written out in full (#://, @://, $://), rewrites the ones not already inside a link into CNXT links, and draws the CNXT mark. Hovering over or keyboard-focusing a linx opens a small card beside it with links to open the linx, search it in #://FiNDR and open the tag's #://XPLR map, and tags the downloaded public cnxtd-tag list shows no verified capture has reached yet are drawn in a distinct style; both are worked out in the browser. 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. A click on Look up in a tag's card sends that one tag, and nothing about the page, to read the tag's public standing. A click on the mark sends the capture: 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 32 distinct tags with their occurrence counts. On a search, hashtag, profile or feed page of X, YouTube, TikTok, Reddit, Instagram, Facebook or LinkedIn, or a Google results page, the press sends the tagged posts or results on screen instead, at most 32 per press and one after another: for each, only its own address, the tags found inside it with their counts, and the document language, and nothing about the listing page itself. 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 to draw their cards and marks, and that reading stays in the browser. Pressing Look up on a tag's card sends only that tag. Pressing the CNXT mark sends only the fields described for the http match: the page's own, or on a platform's listing page, those of the tagged posts on screen.
• 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.

11. 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. Once connected, the requests that act for the user carry its own extension-only token and no cookies; until then, and for the public allocation read, requests to the CNXT origin are sent with credentials so the browser attaches the CNXT session the user is already signed in with, which the extension cannot see. The public cnxtd-tag list download and Look up are sent with no credentials at all.
• webRequest — No traffic is observed, intercepted, or modified.
• downloads — No file is ever saved to the user's downloads, so the chrome.downloads API is never used. The public cnxtd-tag list is fetched into extension storage, which needs no such permission.

12. 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. Opening a linx card sends nothing, and the marks on tags with no verified capture yet come from comparing the page's tags, in your browser, with a public list the extension downloads. Pressing Look up on a tag's card sends that one tag, without the page's address, your sign-in or a cookie, to read its public standing; it is not stored against your account. 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 32 distinct tags with their occurrence counts. On a search, hashtag, profile or feed page of X, YouTube, TikTok, Reddit, Instagram, Facebook or LinkedIn, or a Google results page, it is less: for each tagged post or result on screen, at most 32 per press, sent one after another, only its own address, the tags found inside it with their counts, and the document language. Nothing about the listing page itself is sent. The HTML itself is never sent.
• Web history — collected. Disclosed because the address of each page, post or result 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 — collected. Disclosed because, when you connect your account, the CNXT site issues the extension its own sign-in token. The extension stores it locally and sends it only to the CNXT origin it was built against, to read your position and send the captures you make; Look up and the cnxtd-tag list download never carry it. It works only on the extension's own requests, it is deleted when you disconnect, and CNXT keeps only a one-way hash of it. The extension never reads, stores, or transmits a password or cookie.
• 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. Hovering over a linx opens its card inside the page and is neither recorded nor sent, and a press of Look up sends only the tag. The one interaction that is ever recorded is your deliberate press of the CNXT mark, and it is recorded as the captures 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.

13. How you stop

• Do not press the mark. Nothing is captured without a deliberate press, and pages you read are never reported.
• Do not press Look up. A tag is looked up only when you press it, and the switch in the popup turns the linx cards off altogether.
• Disconnect this browser from the popup, and sign out of CNXT. Disconnecting deletes the extension's sign-in token from your device and asks CNXT to revoke it; with neither that token nor a CNXT session, the capture endpoint refuses the request outright, and nothing is recorded.
• Disable or remove the extension from chrome://extensions. Removing it also clears everything it keeps on your device, the sign-in token and the cnxtd-tag list included.

14. 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.

15. Installing, changes and contact

The extension's Chrome Web Store listing is linked from /thextension. Installs and updates come only from the Chrome Web Store.

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.