Privacy Policy

1. Who is responsible for your data

The personal data controller is [controller's name — fill in the admin panel: Settings], [address — fill in the admin panel]. For data-related matters, write to: [contact email — fill in the admin panel].

2. What data we process and why

Visit statistics (no cookies)

We want to know which articles are read and where readers come from. With each page view we record:

• the address of the page opened and the date and time,
• the country — determined from the IP address at the moment of the page view,
• the type of device (computer, phone, tablet), the browser, the operating system, the screen size and the browser language,
• the domain of the site from which you came to us (e.g. google.com),
• an anonymous hash created from the IP address and the browser name with the addition of a random key that changes every 24 hours.

We do not store the IP address. The hash only makes it possible to count how many different people visited the blog on a given day. After the key changes, the hash cannot be linked either to the next day or to a specific person. We do not store anything on your device for this purpose.

Legal basis: our legitimate interest (Article 6(1)(f) GDPR) — developing the blog and looking after its security. We keep statistical data for a maximum of 13 months.

Post likes

When you click the heart, your browser receives a random identifier, thanks to which one like counts once. The identifier does not contain any information about you. Together with the like we store the daily hash described above — only so that no one inflates the counters. Legal basis: Article 6(1)(f) GDPR.

Comments

When you add a comment, we store the name you enter yourself (it can be a nickname), the content of the comment, the date and time, and the post under which you leave it. We do not ask for an email address or any other contact details. The name and the content are publicly visible under the post — usually right after submission — so do not include in them any data you do not want to disclose.

Together with the comment we store the daily hash described above — only to limit spam (e.g. the number of comments sent in a short time from one device). We delete the hash after two days.

We also store a second anonymous hash, created from the IP address alone and a secret key, which does not change every 24 hours. It is used solely to block a person who abuses the comments from adding them. We delete this hash after two days as well — unless the commenter has been blocked: in that case we keep the hash and the blocked name until the block is lifted. We do not store the IP address itself.

You can attach one image to a comment, e.g. a screenshot. Before it is sent, your browser scales it down and saves it again as a JPG file — this removes the metadata stored in the image (e.g. location or camera model). The image is publicly visible together with the comment, so before adding it, cover any data you do not want to disclose (e.g. your balance, account ID, wallet address, full name). We keep the image in the database for as long as the comment and delete it together with the comment — or earlier, separately, at your request. To limit the number of images sent from one device, we also store the daily hash with the image and delete it after two days.

Legal basis: Article 6(1)(b) GDPR — the publication of the comment that you request, and Article 6(1)(f) GDPR — protecting the blog against abuse. We keep a comment until we delete it (on our own or at your request). You can ask for it to be deleted by writing to the address in section 1 — state the post, the name and the approximate date.

Investor Zone

Some posts are available only after entering a password. After you enter the correct password, the database issues your browser a random session key, valid for 30 days; in the database we keep only its hash and its expiry date. We record failed password attempts together with the daily hash (for no more than 24 hours) in order to block password guessing. We do not record who has entered the zone. Legal basis: Article 6(1)(b) and (f) GDPR.

Trading group

The Trading group is a closed part of the blog that you enter after confirming the risk warning and entering a separate password. After you enter the correct password, the database issues your browser a random session key, valid for 30 days; in the database we keep only its hash, its expiry date and the date on which the risk warning was confirmed — as proof that the warning was read before entry. We record failed password attempts together with the daily hash (for no more than 24 hours) in order to block password guessing. We do not record who has entered the group.

When you publish a post or a comment in the group, we store the name you enter yourself (it can be a nickname), the content, the position details you provide (instrument, direction, price levels, leverage, result), the attached screenshot, and the date and time. They are visible to all group members (people who know the password) and to the blog administrator. So that you can close, correct or delete your own post without creating an account, your browser keeps a random author key — in the database we store only its hash. As with comments, we also store the daily hash and the connection hash (for limits and blocking abuse) and delete them after two days, unless the author has been blocked. The rules for images are the same as for comments.

We keep posts, comments and screenshots until they are deleted by their author (on the device on which they were added) or by the administrator — also at your request sent to the address in section 1. You provide information about your positions and their results voluntarily; we do not combine it with other data and do not use it for any other purpose. Legal basis: Article 6(1)(b) GDPR — participation in the group and the publication of content that you request, and Article 6(1)(f) GDPR — protecting the group against abuse.

Your browser's local storage

In the browser's local storage (localStorage), the blog stores only what is needed for the features you use to work:

• the list of posts saved “for later” and of posts you have liked,
• the random identifier for likes,
• the most recently downloaded price quotes and the page color — so that the page does not flicker on your next visit,
• the price ticker setting,
• the name from your last comment and your comments awaiting approval — so that you do not have to type the name again and can see your comment before it is published,
• the Investor Zone session key, if you have entered the zone,
• the Trading group session key and a random author key for your posts in the group, if you use it; the browser remembers that you confirmed the risk warning only until you close the tab (sessionStorage),
• the list of posts from X that the site has already reminded you about — so that the same notification does not come back.

This information does not leave your device (except for the identifier sent together with a like and the zone and Trading group keys sent when they are opened) and is not used for tracking. You can delete it at any time in your browser settings. Because it is necessary to provide the service you request, it does not require consent (Article 399 of the Electronic Communications Law (Prawo komunikacji elektronicznej)).

Technical connection data

To display the page, the servers of our hosting and database providers have to process your IP address and basic request data for a moment. The providers may keep them briefly in security logs. Legal basis: Article 6(1)(f) GDPR.

Contact

If you write to us, we process your email address and the content of your message in order to reply (Article 6(1)(f) GDPR). We keep the correspondence for as long as the matter it concerns requires.

3. Who we entrust data to

• Vercel Inc. — website hosting,
• Supabase Inc. — database; the blog's data is located on servers in the European Union (Frankfurt).

Your browser downloads some content directly from the servers of other companies, which see your IP address in the process:

• cryptocurrency price quotes and market data — Binance, CoinGecko and Alternative.me (quotes for currencies, commodities, indices, bonds and stocks are fetched by our server, so their provider does not see your address),
• photos and videos in the “Posts from X” tab — the servers of the X platform.

We serve the site's fonts and scripts from our own server. Some of the companies listed are based outside the European Economic Area, including in the USA. Data is transferred there on the basis of the European Commission's adequacy decision (Data Privacy Framework) or standard contractual clauses.

Links in articles, in posts from X, and the affiliate links to OKX (the “OKX” and “Wallet” buttons in the bottom right corner of the page) lead to external websites that have their own privacy rules. When you click the affiliate link, OKX receives the referral code contained in it — we do not pass on to it any other information about you.

4. Your rights

You have the right to access your data, to have it rectified or erased and to have its processing restricted, as well as the right to object to processing based on our legitimate interest. A message to the address given in section 1 is enough.

To be upfront: in the statistics we do not keep anything that would make it possible to recognize a specific person, so we are usually unable to point to “your” page views (Article 11 GDPR).

If you believe that we process data unlawfully, you can lodge a complaint with the President of the Personal Data Protection Office (UODO) — how to lodge a complaint is described on the website uodo.gov.pl.

5. What we do not do

• We do not sell data and we do not pass it on to advertisers.
• We do not profile readers and we do not make automated decisions about them.
• We do not use external analytics tools or social network pixels.

6. Changes to the policy

When the way the blog works changes, we will update this page and the date at the top. We will announce significant changes on the home page.