Last updated: October 30, 2026
The short version
- Trend Following Traders runs no ads, and we don’t sell personal data.
- Our pages don’t use Google Analytics or any other third-party analytics tool.
- We count visits to articles, and clicks on the links to our partners, with our own counter. It uses no cookies and does not store your IP address. After 48 hours only daily totals remain, apart from copies in our encrypted backups. You can opt out of the counter’s scripts at any time, free of charge. Clicks on our partner links that start with /en/go/ are counted by our server, as explained below.
- Some articles show videos from our YouTube channels in YouTube’s privacy-enhanced mode, and commenters’ pictures come from Gravatar. These services receive your IP address, and YouTube may use cookies when you play a video. Our typefaces are served from our own server.
- If you leave a comment, your name and your comment are published, and Akismet checks the comment for spam.
- Cloudflare delivers and protects the site. It may set a security cookie.
- Our web server keeps standard access logs, including IP addresses, for security and troubleshooting. They are deleted after about 10 days.
- If you follow a link to one of our partners, the partner’s website may set its own cookies. That is how the partner knows we sent you.
Who is responsible for your data
The English edition of Trend Following Traders (trendfollowingtraders.com/en/) is run by Stefano Mastria. Under data protection law, he is the controller of the personal data described on this page.
Address: Via Romolo Murri 1, Casoria (NA), Italy.
Email: [email protected].
This policy covers the English site. The Italian site at trendfollowingtraders.com has its own privacy policy, in Italian, and so does our community site (see Our community site).
What we collect and why
Server logs
Like most websites, our web server records each request in a log file: the IP address, the date and time, the site and page requested, the request method, the response code, the size of the response, the referring page (when your browser sends it), the time taken to answer and the browser’s user agent string. Cloudflare sits in front of the server, and the server records the visitor’s IP address as Cloudflare passes it on.
We use these logs to keep the site secure, to investigate errors and to stop abuse. We manage the server ourselves, on infrastructure provided by Amazon Web Services (AWS) in its Europe (Milan) region, in Italy.
Cloudflare
All traffic to trendfollowingtraders.com, including the English site, passes through Cloudflare, Inc., which provides our network, caching and security services. To do that, Cloudflare processes your IP address and the details of each request. It uses them to deliver pages quickly, to block attacks and automated abuse, and to keep the site available. Cloudflare gives us aggregated statistics about traffic and threats.
Cloudflare may set strictly necessary security cookies to tell people from bots: __cf_bm, which expires after 30 minutes of inactivity, and, if your browser is asked to pass a security check, cf_clearance, which remembers that it passed. Cloudflare’s responses also ask your browser to remember, for 7 days, where to report network errors (Network Error Logging). Cloudflare handles this data under its data processing terms with us and its privacy policy.
Our visit and click counter
This site counts visits to its articles, and clicks on the links to our partners (the brokers, prop firms and trading tools whose affiliate programs we have joined), with an internal counter that uses no cookies and stores nothing on the visitor’s device. The IP address is not stored. For at most 48 hours the site keeps a pseudonymous identifier for each visitor and article, and one for each visitor and link, calculated with a random code that changes every day. They are used only to avoid counting reloads and repeated clicks twice and to estimate the number of unique visitors in a day. They cannot be linked across different articles or links. Once the site has deleted the daily code, the identifiers left on the site can no longer be traced back to a visitor. Our encrypted backups may also contain these pseudonymous identifiers and the daily code (see “How long we keep data”).
For the same period the site keeps pseudonymous counters for each IP address and network, without the address itself, so that repeated or automated requests don’t inflate the counts. After that, only aggregate counts remain. For visits: by day, article, traffic source (for example a search engine, social media or email) and market (United States, United Kingdom, European Union, other countries). For clicks: by day, article, link, partner and market.
How visits are counted: on article pages, a small script served from our own domain sends one request per visit to our server, with the page, the referring page and any utm_source and utm_medium values in the link.
How clicks are counted: the partner links in our articles usually point to an address on this site that starts with /en/go/ followed by the partner’s name. When you click one, your browser asks our server for that address, and our server sends you on to the partner’s website. At that moment our server counts the click, with the same rules as the rest of the counter: no cookie, the IP address not stored, and at most one count every 30 seconds for the same visitor and link. For partners whose affiliate program supports it, the address we send you to also carries the name of the article you came from (the last part of its web address), so that the partner’s report can tell us which article led to a sign-up or a purchase. It carries nothing about you. For partner links in our articles that don’t go through /go/, a second small script, also served from our own domain and loaded only on article pages that contain partner links, sends one request to our server when you click such a link (or open it in a new tab with the middle mouse button), with the page, the address of the link and our own reference for it. It doesn’t delay or change the link.
The daily identifier is calculated from your IP address (for IPv6, your network) and your browser’s user agent string. The market comes from the country that Cloudflare derives from your IP address, and we keep it only as United States, United Kingdom, European Union or other countries.
Counting a click doesn’t tell us who you are or whether you buy anything. Partners report sign-ups, purchases and commissions to us separately (see Links to our partners), and we combine those reports with our click totals only as totals, to estimate how much each article and each link earns.
Because the scripts read information in your browser (the referring page, the address of the page and the partner link you click), the law treats them as access to information on your device. In the United Kingdom we rely on the exception for statistics: the counter is used only to produce statistics on how the site is used, such as which articles are read and which links readers follow, so that we can improve it, and its data is not shared except with the service providers that run the site for us. In the European Union we rely on the conditions under which the Italian data protection authority treats analytics tools like technical ones: the counter is run by us alone, it produces aggregate statistics only, and it does not identify you.
You can object at any time, free of charge, with the button below. Your choice is kept in your browser’s local storage as nlr_counter_optout, and the counter’s scripts then send nothing from this browser, for visits or for clicks. The choice applies to this browser only, so use the button again on other browsers and devices. If you clear the site data in your browser, the choice is deleted too. If your browser sends a Global Privacy Control signal, the counter’s scripts send nothing either, for visits or for clicks.
The button and the Global Privacy Control signal work inside your browser, so they cannot stop the count that our server makes when your browser asks for a /go/ address. That count is pseudonymous and is reduced to daily totals as described above. If you don’t want a click counted at all, go to the partner’s website directly instead of following our link.
The button concerns only our own counter. It doesn’t affect the YouTube player or Gravatar images, which are described in their own sections below.
The opt-out button needs JavaScript. With JavaScript turned off, the counter’s scripts cannot run either, so your visits are not counted. Clicks on our /go/ links are still counted by our server, as described above.
Links to our partners
Some of our links, in articles and in the Extra Resources menu, are affiliate links: they tell the partner that the visit came from Trend Following Traders. When you follow one, the partner’s website, and any tracking platform the partner uses for its affiliate program, may set or read their own cookies, or use similar technologies, to credit us with a sign-up or a purchase. They may collect information such as your IP address, browser type and operating system, and use it under their own privacy policies. We don’t control these cookies, and our pages don’t set them. Some of our pages also show a discount code from a partner: if you use it, the partner may use the code to credit us as well.
The reports we receive from partners tell us about the sign-ups and purchases that came through our links or codes, and the commission due. Depending on the partner, a report may also include details such as the country of the purchase or an order or account reference. We use these reports only to check and attribute our commissions and to keep our accounts. We don’t receive your payment details, and we don’t ask partners for your name or contact details. Our own counter also counts clicks on the partner links in our articles, without cookies (see Our visit and click counter).
YouTube videos
Some of our articles show videos from our YouTube channels. The videos load in YouTube’s privacy-enhanced mode, from www.youtube-nocookie.com. According to YouTube, in this mode it doesn’t set cookies until you play the video. The video frame is still loaded from YouTube’s servers, run by Google, when you open the article, so Google receives your IP address and technical details of your browser, as with any request to a web server, and the player may store data in your browser’s local storage. When you press play, YouTube may use cookies and your browser’s local storage. Google handles this data under its privacy policy. We don’t control YouTube’s cookies; from YouTube we only see aggregate view statistics for our channels.
Comments
Comments are open on most articles. If you leave one, we collect what you enter in the form: your name, your email address, your website (optional) and the comment. WordPress also records your IP address, your browser’s user agent string and the date and time. Your name, your website and your comment are published with the comment; your email address is not. The comment form doesn’t save your details in cookies.
To keep spam out, each comment is checked by Akismet, a spam filter run by Automattic Inc. Akismet receives the comment and the details above, the page, the referring page and other technical details of your browser’s request. On pages with the comment form, a small Akismet script, served from our own domain, also notes how the form is filled in (for example the timing of key presses, mouse movements and touches) and sends this with the comment. Automattic handles this data under its privacy policy.
Next to each published comment, our pages show the commenter’s picture from Gravatar, a service also run by Automattic. To find it, WordPress turns the commenter’s email address into a coded string (a hash), which appears in the address of the image. If the commenter has no Gravatar picture, Gravatar returns a generic icon. These images are loaded from Gravatar’s servers (secure.gravatar.com), so Automattic receives the IP address of anyone who reads a page with comments. Gravatar sets no cookies on our pages.
Our community site
We also run a community site, community.trendfollowingtraders.com, with its own pages and policies. This site connects to it in three ways:
- The “Production Accounts & Funds” panel on our home page shows public, aggregate figures from the community site. Your browser asks our own server for them, and our server fetches them from the community site, so nothing about you is sent there.
- Where one of our pages shows a form to join our mailing list, what you enter (your email address and, if the form asks for them, your name and other answers) is sent by our server to the community site, which runs the mailing list, together with any
utm_source,utm_mediumandutm_campaignvalues from the link you arrived from. This site keeps no copy. Depending on the form, the community site first sends you an email with a link to confirm. - Links such as “Sign in with your Account” or “Activate Premium” take you to the community site, where its own policy and cookies apply.
If you email us
The quote request form on our Business page doesn’t send anything to our server: when you submit it, it opens your own email program with a pre-filled message, and we receive only what you then choose to send.
If you write to us, we receive your email address, your message and anything you attach. We use them to reply to you. Our mailbox is on a mail server that we run ourselves, on the same AWS infrastructure in Italy as the site. The emails we send are delivered through Amazon Simple Email Service (Amazon SES).
Pages not found
When someone asks for a page that doesn’t exist on this site, our SEO plugin, Rank Math, records it in a log so that we can fix broken links: the address requested, how many times it was requested and when. In the mode we use, it doesn’t record the IP address, the referring page or the browser’s user agent string. The log keeps at most 100 entries.
Search data
We use Google Search Console to see which searches lead to our pages. Google provides these reports as aggregated data. We view them, together with PageSpeed results, through the Site Kit by Google plugin in our WordPress dashboard. Site Kit adds no Google script and sets no cookies on the pages you read.
What we don’t do
- No advertising.
- We don’t sell personal data.
- No third-party analytics on our pages: no Google Analytics or similar services.
- No Google Fonts: our typefaces (Poppins and Nunito) are served from our own server, so your browser doesn’t download them from Google.
- No social media share buttons or widgets. Apart from the YouTube videos described above, the links to our YouTube, TikTok and LinkedIn profiles are plain links, which load nothing from those services until you click them.
- Readers don’t need an account on this site.
Cookies and similar technologies
These are the cookies and similar technologies used when you read the English site:
- YouTube. On articles with a video, the player loads from www.youtube-nocookie.com. According to YouTube, it sets no cookies until you play the video. The player may store data in your browser’s local storage, and when you play a video YouTube may set its own cookies, for as long as Google’s policies say (see YouTube videos).
- Your choice about the counter. If you use the button in Our visit and click counter, your browser’s local storage keeps one entry,
nlr_counter_optout, so the counter’s scripts send nothing, for visits or for clicks. It never leaves your browser and has no expiry date. You can delete it with the same button or by clearing the site data in your browser. - Our visit and click counter. It sets no cookies and stores nothing in your browser, but its scripts read the referring page and the address of the page and, on pages with partner links, note which partner link you click, as described in Our visit and click counter.
- Akismet. On pages with the comment form, its script notes how the form is filled in and sends it with your comment, only to check it for spam. It sets no cookies (see Comments).
- Gravatar. No cookies, but your browser downloads commenters’ pictures from Automattic’s servers, as described above.
- Cloudflare security cookies. Strictly necessary security cookies, as described above.
__cf_bmexpires after 30 minutes of inactivity. - Cloudflare network error reporting. Cloudflare’s responses ask your browser to remember for 7 days where to report connection failures (Network Error Logging).
- HTTPS only. Our server asks your browser to remember for one year to use only HTTPS on trendfollowingtraders.com (HTTP Strict Transport Security).
- Comments. The comment form sets no cookies.
- Partner websites you visit through our links. Their own cookies, set on their websites after you follow a link, for as long as their own policies say.
- Site editors. WordPress sets login cookies only for the people who sign in to manage the site. Readers never need to sign in.
In the European Union, the ePrivacy rules (in Italy, Article 122 of the Italian Personal Data Protection Code) require consent before a website stores or reads information on your device, unless it is strictly necessary for the service you asked for. The cookie guidelines of the Italian data protection authority (June 10, 2021) treat analytics tools like strictly necessary ones when they only produce aggregate statistics for the site that runs them and do not identify visitors. In the United Kingdom, the Privacy and Electronic Communications Regulations (PECR) have the same rule, with an exception for strictly necessary uses and, since February 5, 2026, one for uses that only produce statistics to improve the site, when you are told clearly and can object simply and free of charge. Our visit and click counter relies on these provisions (see Our visit and click counter). Cloudflare’s security cookies and network error reporting, the HTTPS-only instruction, the record of your choice about the counter and the Akismet script, which sends its data only with a comment you choose to post, are strictly necessary. We set no analytics or advertising cookies. The YouTube player loads without asking for your consent first, in privacy-enhanced mode: according to YouTube, it sets no cookies until you play a video, though the player may store data in your browser’s local storage, and when you play one, YouTube may use cookies (see YouTube videos).
Legal bases
Trend Following Traders is run from Italy, so the EU General Data Protection Regulation (EU GDPR) applies to the data described on this page. For readers in the United Kingdom, the UK GDPR applies too. Both require a legal basis for each use of personal data. We rely on:
- Legitimate interests (Article 6(1)(f)) for server logs, Cloudflare and the log of pages not found: running a secure, fast and available website and fixing broken links.
- Legitimate interests for the visit and click counter: knowing which articles are read, where readers come from and which of our links they follow, using pseudonymous data that is reduced to daily totals after 48 hours.
- Legitimate interests for partner reports: checking that our commissions are correct and which articles they come from.
- Legitimate interests for comments: publishing and moderating them and keeping spam out with Akismet.
- Legitimate interests for Gravatar images: showing commenters’ pictures next to their comments.
- Legitimate interests for YouTube videos: showing the videos from our own channels in our articles, in YouTube’s privacy-enhanced mode. You can choose not to play them.
- Legitimate interests for emails: replying to you.
- Consent (Article 6(1)(a)) for the mailing list sign-up form: you send it yourself to join the list, and you can withdraw your consent and unsubscribe at any time, free of charge, by writing to us.
- Legal obligation (Article 6(1)(c)) when the law requires us to keep or disclose data, for example accounting and tax records.
You can object to any processing based on legitimate interests (see “Your rights” below). For the counter’s scripts, the simplest way is the button in Our visit and click counter: it works at once, and you don’t need to write to us.
Who receives the data
These service providers process data on our behalf:
- Cloudflare, Inc.: network, caching and security.
- Amazon Web Services (AWS), Europe (Milan) region, in Italy: the server that runs the site and our mailbox.
- Amazon Web Services (Amazon S3): encrypted backups of the site.
- Amazon Web Services (Amazon SES): delivery of the emails we send.
- Automattic Inc.: the Akismet spam filter for comments.
Some services receive data directly from your browser and handle it under their own policies: Google, for the YouTube player; Automattic, for Gravatar images; our partners, when you follow a link to them. Our community site receives what you send through the sign-up form. We may disclose data when the law requires it.
International transfers
Our server and our mailbox are in the European Union, in Italy. UK law recognizes the countries of the European Economic Area, including Italy, as providing adequate protection for personal data. Some of our providers, such as Cloudflare, Amazon Web Services and Automattic, are based in the United States and operate worldwide, so they may also process data there or in other countries. When data goes to a country outside the European Economic Area and the UK, we rely on the provider’s data processing terms, which include the EU Standard Contractual Clauses and the UK International Data Transfer Addendum, or on the EU-US Data Privacy Framework and its UK Extension where the provider is certified under it. For YouTube and Gravatar, your browser connects to these services directly, and they handle any transfer under their own policies.
How long we keep data
- Server logs: about 10 days. The log files are rotated every day, and only the most recent ones, covering about 10 days, are kept. Copies may also remain in our encrypted backups (see below).
- Visit and click counter: pseudonymous identifiers and per-address counters for at most 48 hours on the site; after that, daily totals only. Copies of the identifiers and of the daily code may remain in our encrypted backups (see below).
- Log of pages not found: at most 100 entries; when the log reaches that limit, Rank Math clears it.
- Comments: for as long as the comment stays on the site, together with the IP address and user agent recorded with it. Comments that Akismet marks as spam are deleted automatically after about 15 days.
- Cloudflare, Google (YouTube) and Automattic (Akismet and Gravatar): as described in their privacy policies.
- Mailing list sign-ups: kept by the community site, which runs the list, for as long as you stay subscribed. If you unsubscribe, it may keep your email address only to make sure you are not emailed again.
- Partner reports: for as long as accounting and tax law requires us to keep the records of our income.
- Emails: for as long as we need them to answer you and to handle any follow-up, then we delete them.
- Backups: encrypted backups of the site, which may contain the data above, are kept for up to about six months: one a day for the last 7 days, one a week for the last 4 weeks and one a month for the last 6 months.
Your rights
Under the EU GDPR and the UK GDPR you have the right to:
- get a copy of the personal data we hold about you;
- have inaccurate data corrected;
- have your data deleted;
- ask us to restrict how we use it;
- object to processing based on legitimate interests;
- withdraw your consent at any time, where we rely on it, without affecting what was done before;
- receive your data in a portable format, where this right applies.
Wherever you live, to use these rights email [email protected]. We aim to reply within one month. We may ask for information to confirm that the request is yours. For server logs, it helps to tell us your IP address and roughly when you visited; for comments, the email address you used. Our visit and click counter does not store IP addresses and deletes its identifiers within 48 hours, so we usually cannot link counter data to you. To stop the counter’s scripts, use the button in Our visit and click counter.
You can complain to the Italian data protection authority, the Garante per la protezione dei dati personali (garanteprivacy.it), or to the data protection authority of the EU country where you live, where you work or where you believe the problem occurred. In the United Kingdom you can complain to the Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint. We would appreciate the chance to fix the problem first.
Readers in the United States
We don’t sell personal information, and we run no ads. If your browser sends a Global Privacy Control signal, the counter’s scripts send nothing, as if you had used the opt-out button. The signal doesn’t change anything else: the YouTube player and Gravatar images work the same way, and our server still counts clicks on /go/ links, as described in Our visit and click counter.
Children
Trend Following Traders is written for adults. It is not directed to anyone under 18, and we don’t knowingly collect personal information from children.
Security
Every page is served over HTTPS. Access to the server, its logs and its backups is limited to the people who run the site, and backups are encrypted.
Changes to this policy
When we change how we handle data, for example when we add or remove a service, we update this page and change the date at the top.
Contact
Questions about this policy: [email protected].
