Single purpose
xbsv does one thing. When you like a post on X, and you have turned Pay likes on, it asks Link to pay the @nexusnode.link paymail published in that author’s biography.
Link is a separate wallet that you install and run on your own computer. xbsv does not hold a wallet, a seed, or a private key. Link is described at https://dalais.org/link/.
Who is responsible
The developer is Joel Dalais, United Kingdom. The public site is https://dalais.org/.
xbsv does not create an account with the developer. The developer does not operate a server that receives the posts you like, the people you pay, or the text of a biography. There is no xbsv user database.
What xbsv does not collect
These categories are not collected. They match the categories left unticked on the Chrome Web Store data-use form.
- Personally identifiable information. xbsv does not ask for or store your name, postal address, personal email address, age, or any government identification number. It does not build a profile of you. A @nexusnode.link paymail read from a public biography is a payment name, used only to address one payment, and it is not kept. Your own paymail stays in Link. When Link pays, Link signs that payment with the paymail of the wallet you connected, as it does for its other payments. xbsv does not receive a copy of that wallet.
- Health information. None.
- Authentication information. xbsv does not ask for, see, or store your X password, your Link password, a seed phrase, a private key, a cookie, or a security code.
- Personal communications. xbsv does not read direct messages, emails, or private chats.
- Location. None. No region, IP address, or GPS data is read or stored by the extension.
- Web history. xbsv does not keep a list of the sites or pages you visit, their titles, or the times you visited them.
- User activity. xbsv does not record a history of clicks, mouse movement, scrolling, or keystrokes, and it does not monitor your network. It notices the Like control on X, including the L key when X uses that key as Like, so that a like can be paid. That event is not stored.
Website content
This is collected in the sense Chrome uses: the extension handles it in order to do its job. It is handled on your computer. It is not sent to the developer.
On x.com and twitter.com, from the post you like, xbsv reads the author’s handle and the link to that post. It does not store the post, and it does not keep a copy of your timeline.
It then requests that author’s public profile page. The request is sent without your X cookies. From the answer, xbsv reads the public description and looks for an @nexusnode.link paymail.
If that public page shows no paymail, xbsv looks at the biography text on the X page you already have open. If the biography is not already there, xbsv may ask X for that author’s public biography through the X session the browser already has, because that is how X returns the page. X receives that request as it would when you open a profile. xbsv keeps only the biography text, in the memory of that tab, long enough to look for one @nexusnode.link paymail. It does not read direct messages, follower lists, or other account fields for any further purpose. The biography is not written into the extension’s saved settings, and it is not sent to the developer.
A paymail counts only when it ends in @nexusnode.link. Any other address in the biography is ignored. One of those names can be paid. None, or more than one, and nothing is sent. xbsv does not contact other websites to check a name.
Financial and payment information
This is the other category disclosed on the Chrome Web Store form. xbsv handles a payment amount, and it asks Link to pay it. The developer does not receive the payment and does not keep a ledger of payments.
You set an amount in the extension, from 100 sats to 100,000 sats. That amount is saved on your computer. Pay likes stays off until you turn it on. While it is off, xbsv does not ask Link to pay.
When a like remains in place, xbsv asks Link, on your own computer at 127.0.0.1 port 21736, to pay that amount to the one @nexusnode.link paymail it found. The request contains the paymail, the amount, the path of the post, a short note in the form “Like @handle”, and a random nonce so that one attempt is one payment. It does not contain a seed, a key, or an X password.
Link decides whether the payment proceeds. Link may ask you to confirm it. If you have allowed Link to pay under a limit you set, and this payment is inside that limit, Link can pay without a second question. Above that limit, Link asks. You can refuse. A refused payment is not retried by itself, and no reply is posted.
When you accept, Link broadcasts one transaction on the BSV network. The transaction pays the amount you set, plus a house fee of 50 sats. The extension cannot change that fee, remove it, or send it somewhere else. The network fee is paid from your Link wallet in the same transaction. The transaction is public, because that is how a BSV payment works. Link signs it with the paymail of the wallet you connected. A transaction that has been broadcast is part of the public ledger. The developer cannot delete it, and xbsv does not keep a copy of it beyond the short status line in the popup.
xbsv does not collect card numbers, bank account numbers, credit scores, financial statements, or a history of your payments.
The optional public reply
Auto-reply is off until you turn it on. You can edit the sentence. The sentence supplied with the extension is: Sent you <n> sats with the like. The mark <n> is replaced with the amount you set.
A reply is posted only after Link has paid, only under the post you liked, and only as you, on X. It is a public reply on that post. It is not a direct message. It is not sent to the developer. If Auto-reply is off, or the payment does not complete, no reply is posted.
What stays on your computer
Chrome stores the following for this extension, on your computer, and nowhere else:
- whether Pay likes is on
- the amount
- whether Auto-reply is on
- the reply sentence
- whether you have connected Link
- the short status line shown in the popup
- if a newer version is published, the address of the product page
On startup, xbsv requests https://dalais.org/xbsv/ and reads the version number on that page. The request contains no name, no paymail, and no record of what you liked. If the page lists a newer version, the page address is saved on your computer so the popup can tell you.
Removing the extension removes these saved settings. Disconnect clears only the connected flag.
Who else receives something
The developer does not receive user data. The following transfers happen only because they are the payment, the biography check, or the optional reply.
- Link, on the same computer. The payment request described above. Link is your wallet. It is not a server run by the developer for xbsv.
- The BSV network, through Link. The one transaction, once you have allowed Link to send it. It is public. The person you paid receives the sats.
- X. The cookieless request for the author’s public profile. If needed, the biography request made with the X session already in the browser. If you turn Auto-reply on, the one public reply, posted as you.
- dalais.org. The version-page request, with no user data.
Data is not sold. It is not transferred to an advertiser, a data broker, or a credit agency. It is not transferred for any purpose other than the payment and the optional reply.
How long it is kept
Saved settings remain on your computer until you change them, disconnect, or remove the extension. Biography text is kept only in the memory of the open tab, and only until the check is finished. The developer keeps no account, no log of likes, and no payment history.
A transaction Link has broadcast remains on the public BSV ledger. That retention is a property of the ledger, not a copy held by xbsv.
Security
The extension’s scripts are inside the package you install. xbsv does not download scripts, and it does not run code fetched from the internet. That is the “remote code” question on the Chrome Web Store form: the answer is no.
Requests to X and to dalais.org use HTTPS. The request to Link stays on your computer. Wallet keys never enter the extension.
Limited use
The data described in this policy is used only to pay a like you chose to pay and, if you turn it on, to post the one reply you wrote. It is not used for advertising, retargeting, profiling, or market research. It is not used to decide creditworthiness or for lending.
The developer does not receive biographies, likes, or payments, so no person working for the developer reads them. There is no analytics package, and there is no crash report that includes what you did on X.
Your choices
Leave Pay likes off and xbsv will not pay. Leave Auto-reply off and it will not reply. Disconnect ends the connection to Link. You can change the amount and the reply sentence in the popup. You can remove the extension from Chrome at any time, which removes the settings it saved. Link’s own settings decide when a payment asks you first.
Because the developer holds no profile and no payment log, there is no developer copy to inspect, correct, or erase. Local settings are yours to change or delete as described above. A payment already broadcast cannot be removed from the public ledger.
Children
xbsv is not directed at children under 13, and it does not knowingly collect personal information from children.
Changes
If this policy changes, the new text will replace this page and the date at the top will change. The Chrome Web Store listing for xbsv uses this address: https://dalais.org/xbsv-privacy/.