Dolix Extension Privacy Policy

The data operator is the Dolix Administration (hereinafter "we", "the service"). For data-processing matters and requests concerning records in the database, contact us via the Dolix Telegram bot and extension support.

This document covers the Dolix browser extension running on www.bybit.com pages and its requests to the service's server. It does not cover the Bybit platform itself: its website, apps and the data processing the exchange carries out on its own are governed by its own documents. The service is not an affiliate of Bybit and does not act on its behalf.

Understanding the scope of processing requires understanding the mechanics, so we describe them plainly.

3.1 Reading the page. The extension reads the content of open Bybit pages: the rows of the ad list (order book), the order list, the order window and the profile page.

3.2 Reading the platform's responses. On www.bybit.com pages the extension reads the responses that the exchange already sends to your browser in the P2P sections; other traffic is not parsed. This approach was chosen deliberately: the labels in the ad list and in the order list are produced without a single request to the exchange. What the page does not load (the merchant card, the merchant's contacts, reviews of the merchant) is requested separately and within narrow limits — see 3.3 and 3.3.1. The parsed fields are passed into the page by a standard browser mechanism and read from there by the extension; technically, at that moment they are also available to other scripts running on www.bybit.com — this is the same data the exchange page has already loaded for itself.

3.3 The extension's own requests to Bybit. The extension makes requests to the exchange only for the features you see: it fetches the chat messages of your order, downloads an attachment from that chat to check a receipt, collects public information about the counterparty from their storefront — the merchant card, the email and phone number as masked by the exchange, reviews of them — and also reads, page by page, the list of your own completed and cancelled orders (remembering where it stopped) and the cards of some of them, in order to pass the outcomes of these deals to the shared statistics (Section 6). These requests are sent on behalf of your exchange session — just as if you had opened the merchant's storefront yourself; the extension does not read, store or transmit cookies anywhere, the browser attaches them.

3.3.1 Collection limits. You do not start the collection of counterparty information manually: it runs when you open an order window and, less often, when you browse the ad list. That is why the extension keeps it within narrow limits: a pause of 0.6–1.3 seconds between requests, no more than one at a time, no more than 60 counterparties per hour while the ad list is browsed in the background (collection for an order you opened yourself does not count towards this ceiling), the same person no more than once every 6 hours, and in an open order window no more than once every 30 minutes; the limits apply in each tab separately. If the exchange refuses (403/429), collection stops for at least 10 minutes. The extension never makes requests that change the state of an account or an order — leaving a review, blocking, reporting, cancelling or paying for an order. Collection is an integral part of how the extension works (Section 6): it runs while the extension is enabled and a key is set in it; there is no separate setting to turn it off.

3.4 Access key. The key is held only in the extension's background (service) process and in the browser's local storage. Neither the Bybit page nor the extension's script embedded in it can see the key: they send a command to the background process and receive a ready response. The key is not returned even to the extension's own settings page.

3.5 The extension makes no other network requests: not to analytics systems, not to advertising networks, not to other domains.

4.1 The identifier of the counterparty being checked — the Bybit user ID, the profile mask and/or the nickname. This is what the extension exists for: based on them, the server answers whether there are complaints about the person.

4.2 The value being checked — a card number, phone number, bank account number (IBAN) or Telegram tag, when you check a payment detail or when the extension verifies the recipient's payment details in the order window.

4.3 The receipt file — when a PDF receipt from the order chat is checked automatically, the entire file is sent to the server for forensic analysis and matching against a database of known forgeries.

4.4 The text of a review or a blacklist request, and your nickname on the exchange — when you press the corresponding button. The nickname is needed so that it, rather than a service label, appears in the signature.

4.5 The outcomes of your deals (the composition is set out in Section 6) — always while the extension is running with a key set.

4.5.1 Public information about the counterparty — on the same terms. This is what Bybit shows to any visitor of the merchant's storefront: the nickname and profile link, the number and amounts of deals, the completion rate, the payout time, the account age, the country of identity verification, the email and phone number as masked by the exchange itself, the texts of reviews of the merchant and the nicknames of their authors. This information is stored by the service and shown to other users: Bybit deletes reviews after 180 days, but we keep them.

4.5.2 Information about ads from the ad list — what the page has already loaded by itself, without requests to the exchange: the ad ID, the maker's mask and nickname, the price, volumes and limits, payment methods, the text of the ad terms, deal counters and completion rate, exchange labels, and the online indicator. Together they form the overall picture of offers; this data contains no payment details or chat messages.

4.5.3 The "Order issue" request — only when you press this button in the order window and confirm sending. The request includes: the reason you selected and your description; the order card (number, amount, currency, coin, price, side, order and appeal status, cancellation code); public information about the counterparty and about you from the Bybit storefront (ID, nickname, ratings, number and amounts of deals, payout time, country of identity verification, email and phone number as masked by the exchange, dates of registration and of the first deal), as well as the information about the counterparty from the service's database that the panel has already shown you (blacklist verdict, labels, violations, reviews, deal history, linked accounts, previous nicknames); if the checkbox is ticked, the chat of this order (message text, sender, time; for attachments, only the file name). The request is stored by the service and forwarded to a private support channel for dispute review; the chat is used for nothing other than reviewing this request and is not shown to other users.

4.6 The access key and the device identifier — in the headers of every request. The device identifier is a random value the extension generates for itself on first launch; you neither enter nor see it. It is needed to limit the number of browsers using one key.

Passwords, confirmation codes and API keys of your Bybit account; cookies and the contents of the exchange session; browsing history and the addresses of tabs not related to www.bybit.com; the content of pages on other websites; your private messages outside order chats. The extension is not granted permission to view the addresses of all tabs: it sees the address only of Bybit tabs.

The extension sends the outcomes of your P2P deals: the order number, the counterparty's ID and nickname, the side of the deal, the status, the appeal flag and appeal status, who cancelled the order and why, the amount, price, quantity, currency, coin and date, as well as the counterparty's name as displayed on the Bybit order card — the name is used only as a search attribute for linking accounts and is not shown to users. Your names, payment details and chat messages are not included in this submission — the receiving form does not contain them. This data forms the counterparties' deal history, available to all users of the extension: you see the deals you submitted in the card immediately; other users see them after several independent users have submitted data about the counterparty.

Together with the outcomes, the list of identifiers of your own Bybit accounts that you have logged into in this browser is sent (clause 7). Without it, the service cannot distinguish your transfer between two of your own accounts from a deal with a stranger and would count it in someone else's statistics. The list contains identifiers only: no nicknames, names or other information about these accounts.

Participation in the shared statistics, like the collection of information about counterparties and ads (3.3.1, 4.5.1, 4.5.2), is an integral part of how the extension works: without mutual contribution this feature works for no one, so there is no separate setting to turn them off; the "Shared statistics" setting from previous editions no longer applies, and sending is carried out on the terms of this Section. Sending takes place only while the extension is enabled and an access key is set in it; to stop it, disable or remove the extension or delete the key from the settings. Records already sent remain in the shared statistics; upon a request to support, we will stop counting records sent from your key in further aggregation — we may ask for confirmation that the key belongs to you. Records about you sent by other users are processed on the terms of Section 8; an objection to them is filed in the same manner.

In the browser's local storage the extension keeps: the access key, the device identifier, the selected language and theme, your chat message templates, service collection marks (when each counterparty was collected and where parsing of your order history stopped), the time of the last check for extension updates, and the list of identifiers of your own Bybit accounts (up to 50) that you have logged into in this browser. An identifier is added to the list only after two independent confirmations and is removed from it if it has not been confirmed for 90 days.

This data does not leave your browser, except for the key and the device identifier, which are sent in request headers (clause 4.6), and the list of your own accounts, which is sent together with deal outcomes (Section 6). Removing the extension deletes all of the above along with it.

The extension shows information about the counterparty: status in the complaint database, community reviews, deal statistics and, for some counterparties, contact details and previous nicknames from our observations. This information comes from user complaints, public sources and data collected by the service; some of it the exchange does not show in its interface. Processing is carried out in the legitimate interest of protecting users from fraud. Section 9 of the general Privacy Policy applies to such records in full, including the procedure for filing an objection, a correction or a request to delete a record about oneself.

A separate note on the "Linked accounts" section. It reports the FACT of a match: two accounts share a name verified by the exchange, or the account to which money was sent in deals. This is not a statement that the accounts belong to the same person: there are people with identical full names, shared accounts of relatives and the cash accounts of exchange offices, and it is impossible to tell them apart from the available data. The conclusion from a match is drawn by the user.

The key works in a limited number of browsers at the same time. For this purpose the service stores the device identifiers linked to the key owner and the time of the last request. The device identifier is not tied to hardware and does not allow you to be identified on other websites; it exists only inside the extension. Devices can be disconnected in the bot.

The retention periods described in Section 14 of the general Policy apply to the extension's data. In addition: check records and uploaded receipts are kept for as long as necessary for security and fraud-detection purposes, including matching new checks against historical ones; device identifiers stop occupying a slot after a period of inactivity and are deleted when the device is disconnected in the bot.

The rights and the procedure for exercising them are described in Section 15 of the general Policy. Requests are accepted via the Telegram bot and extension support.

The extension is intended for persons aged 18 or older. We notify you of changes to this document in the extension or the bot, stating the edition date. Changes that expand the scope of transmitted data or cancel previously available settings take effect no earlier than 14 calendar days after notice; continued use after that date means acceptance of the updated edition. If you do not agree with the changes, disable or remove the extension or delete the key (Section 6). This edition supersedes all previous editions of the extension privacy policy.

This document describes the actual practices of the extension and does not provide guarantees beyond the requirements of applicable law. The provisions of the Extension Terms of Use on the informational nature of results and on limitation of liability apply to data processing under this document. The invalidity of any individual provision does not affect the rest.