Privacy policy

1. Who processes the data

1.1. Data is processed by the Market Filter project team, which runs the market-filter.com website ("Market Filter", the "Operator", "we"). Market Filter is an independent information project run by a group of private individuals; the project is not a legal entity.

1.2. For any questions about the processing of personal data you can contact us through the Telegram bot @MarketFilterSupportBot or by email at marketfilter.team@gmail.com.

2. The essentials in two paragraphs

2.1. Market Filter is an open showcase of analytical materials. There is no registration, no personal accounts, no forms asking for personal details, and no comments or reviews from visitors. To read our materials you do not need to tell us anything about yourself.

2.2. We do not sell or share User data with ad networks or data brokers. We receive personal data in only two situations: when a User writes to us via the Telegram bot or by email, and in the form of standard technical information transmitted when a browser requests a page. In addition, the site keeps attendance statistics in two ways: the Cloudflare Web Analytics counter, which uses no cookies and does not track individual visitors, runs on every visit except for visitors from the European Union, and Google Analytics 4 is switched on only if the User has agreed to it; see clause 3.4.

3. What data we receive

3.1. Technical data when you visit the site

When a page is opened, the server receives and records in its logs a standard set of information: IP address, date and time of the request, the address of the requested page, the type and version of the browser and operating system, the browser language, and the address of the referring page.

The site runs through the Cloudflare network, which delivers the pages and protects them from attacks, so the same information also passes through Cloudflare.

This information is needed to keep the site running, to investigate failures and to fend off attacks and excessive automated load. We do not create individual user profiles from this data. Technical logs are kept for a limited period, set out in section 7.

3.2. Cookies and browser local storage

The site uses technical cookies: ours remember the selected interface language and colour theme, and a Cloudflare cookie protects the site from bots. Analytics cookies set by Google Analytics 4 are added only after you give consent, and they are deleted if you refuse. There are no advertising cookies, ad network pixels or social network widgets on the site. The Cloudflare Web Analytics counter uses no cookies (clause 3.4).

In the browser's local storage the site makes a single entry: it holds your answer about cookies, the date of that answer and the version number of the question. The entry stays in the browser, is not sent to our servers and is not stored by us.

Details are set out in the Cookie Policy.

3.3. Data you provide yourself

If you write to us via the Telegram bot, we receive what you tell us: your Telegram name or handle, your Telegram account identifier, the content of your request and any files attached to it.

If you write to us by email at marketfilter.team@gmail.com, we receive the sender's address, the name shown in your mailbox, the content of the email and any files attached to it. The mailbox runs on Google's Gmail service, so emails are stored by Google.

Correspondence about paid services is a separate case. The order, the price and the payment arrangements are agreed only in the Telegram bot @MarketFilterSupportBot, so we receive what the client tells us: a contact for replies, details about the channel and the terms agreed for the order. To account for payment, we record the amount, the date, the network and the transaction hash, and for a refund, the wallet address the client names. We never request bank card details, wallet keys or seed phrases, passwords or API keys, and we ask you not to send them to us (clause 3.5). The conditions of the services are set out in the Paid Services Terms.

This data is used only to consider your request and reply to it, and order details also to fulfil the order and keep account of payments. Requests related to publications (for example, a request for a correction or a status review) are kept longer than the rest: they serve as evidence that a decision was made on reasonable grounds and as a record of how a material was handled.

3.4. Analytics

The site keeps attendance statistics in two ways. The first way is the Cloudflare Web Analytics counter by Cloudflare, the network through which the site is delivered. It sets no cookies, stores nothing in the browser and does not track a person across visits or across websites. The counter receives the page address, the referring page, the type of browser and device, the country and page load speed measurements; according to Cloudflare, the IP address is discarded and not stored. We see only aggregate figures for the site. The counter runs on every visit regardless of the answer in the cookie banner. It is not switched on for visitors from the European Union. It can be switched off with a script blocker in the browser.

The second way is Google Analytics 4, a website attendance statistics service by Google. It helps us understand how many people come to the site, which pages they read and where they arrive from. It is switched on only with your consent: on the first visit a banner with a question about cookies appears at the bottom of the window, and while there is no answer the site does not contact Google at all and Google receives no information about the visit.

After consent is given, Google Analytics 4 sets its own cookies in the browser and receives details about the visit: the page address, the referring page, the type of device and browser, an approximate location derived from the IP address, and the time and order of page views. We do not build a profile of an individual person from this data and do not link it to the content of requests.

A refusal is remembered in the same way as consent, and the question is not asked again. The choice can be changed at any time: in the site footer, next to the legal documents, there is a "Cookie settings" link. When consent is withdrawn, the page reloads without the Google Analytics 4 script, and the Google Analytics cookies are deleted from the browser.

You can also opt out through your browser: block cookies in its settings, or install Google's official browser add-on that blocks Google Analytics. The site will keep working either way.

How Google processes the data on its side is described in Google's own privacy documents. If we connect a different analytics system or change what is collected, this Policy and the Cookie Policy will be updated and consent will be requested again.

3.5. What we do not collect

We do not request or collect identity documents, bank card numbers and bank details, cryptocurrency wallet keys or seed phrases, exchange passwords or API keys. Information about a transfer for a paid service (the network, the transaction hash and the wallet address for a refund, clause 3.3) is not data of that kind: it cannot be used to dispose of funds. No Market Filter employee is entitled to ask you for the data listed above. Any such request made in our name is not official and may be a sign of fraud.

4. Data about Telegram channels and their administrators

4.1. The main body of information on the site concerns Telegram channels, groups and chats: name, username, description, avatar, subscriber count, and the materials published in those channels.

4.2. This information comes from public Telegram data, the channels' own publications, open mentions online, external analytics services and other publicly available sources, as well as from the Editorial Team's own research.

4.3. Where such information relates to an identifiable individual (for example, a channel run by a public author), it is processed for journalistic and informational purposes: to prepare and distribute analytical materials of public interest, including warning the audience about fraudulent schemes.

4.4. We do not publish private-life details, home addresses, personal phone numbers, identity document data or payment data of channel administrators. Materials use only what relates to the object's public activity and to the circumstances we examine.

4.5. Anyone who believes that information published about them is inaccurate or unlawful may contact the Editorial Team in the manner set out in the Complaints and Appeals Policy.

5. Why we process data

• keeping the site running, secure and available;
• remembering interface preferences (language, theme);
• handling requests and replying to them;
• preparing, publishing and updating analytical and informational materials;
• protecting the rights of Market Filter and Users, including investigating abuse and complying with legal requirements;
• attendance and speed statistics for the development of the site: general figures through Cloudflare Web Analytics on every visit (except for visitors from the European Union), detailed ones through Google Analytics 4 with the User's consent.

Grounds for processing. Technical data and interface settings are processed on the basis of our legitimate interest in keeping the site working and secure. Correspondence is processed on the basis of the User's own request, that is on their own initiative and consent. Information used in publications is processed for journalistic and informational purposes, in the interest of public awareness of risks and fraudulent practices. Google Analytics 4 data is processed on the basis of the User's consent: nothing is collected before consent, and consent can be withdrawn at any time in the ways set out in clause 3.4. Cloudflare Web Analytics statistics are kept on the basis of our legitimate interest in understanding the site's attendance and speed: this counter uses no cookies and does not track individual visitors. Correspondence about paid services is processed in order to perform what was agreed with the client.

6. Who we share data with

6.1. We do not sell personal data and do not pass it to third parties for their own purposes.

6.2. External service providers take part in running the site: hosting and cloud storage, a network that delivers and protects the site and also keeps general visit statistics, Telegram, the Gmail email service used for email correspondence, an attendance statistics service (only where the User has consented to analytics), a translation service for editorial texts and a source of exchange quotes. Such services receive User data only to the extent technically necessary; some editorial services do not handle Users' personal data at all.

6.3. Some of these services are located outside the User's country, so technical processing of data may take place in other countries.

6.4. We may disclose information where required by law or by an official request from a competent authority, and where it is necessary to protect our rights and the rights of third parties.

7. How long we keep data

• server logs: for as long as technically necessary, normally no longer than 12 months;
• the User's answer about cookies: in their browser until they delete it themselves; we do not store this answer;
• correspondence on ordinary requests: up to 12 months after the request is closed;
• details of paid service orders and payments for them (the client and a contact for replies, the channel, the agreed terms, amounts and dates, the network and the transaction hash, the wallet address for a refund): for as long as they are needed to keep account of payments, confirm payment and resolve possible disputes. At the client's request, the client's name and contact are anonymised (clause 9.3);
• requests related to publications, appeals and status reviews, together with the supporting materials attached to them: for the whole period the relevant material is published and for as long as is necessary to defend the editorial position and to resolve possible disputes;
• editorial materials and their history: indefinitely, including cards of removed channels, which are kept for the sake of transparency and record-keeping.

8. How we protect data

8.1. Traffic to and from the site runs over the secure HTTPS protocol. Access to data is closed and open only to those who need it for their work.

8.2. No one can guarantee complete security of data transmission over the internet, and we do not give such a guarantee. We apply reasonable technical and organisational measures and keep improving them.

9. Your rights

9.1. Where applicable law provides for it, you may request access to your data, its correction or deletion, restrict or object to its processing, and withdraw consent previously given.

9.2. Requests are sent to @MarketFilterSupportBot or to marketfilter.team@gmail.com. We reply within the deadlines set by the Complaints and Appeals Policy and may ask clarifying questions to make sure the request comes from the person the data concerns.

9.3. A request for deletion does not automatically extend to editorial materials: information about a channel obtained from open sources and published for informational purposes is assessed separately, under the Complaints and Appeals Policy. A request from a client of a paid service to delete their data is fulfilled by anonymisation: the client's name and contact are removed from the record about them and from the order history, while amounts, dates and transfer details are kept, because they are needed to keep account of payments.

9.4. Consent to analytics cookies can be withdrawn at any time using the "Cookie settings" link in the site footer; details are in clause 3.4. Cookies can also be deleted and blocked in your browser settings. With technical cookies disabled the site will keep working, but it will stop remembering your language and theme.

9.5. If our reply does not satisfy you, you may complain to the data protection authority of your country. We ask you to write to us first: most questions are resolved faster directly.

10. Children

The site is not intended for persons under 18 and does not knowingly collect their data. If we learn that a child's data has reached us, we will delete it.

11. Changes to this Policy

We update this Policy as the service develops. The current version is always published on the site, with the update date shown in the header. We flag material changes on the site. Continued use of the site after a new version is published means acceptance of it.