Cookie Policy
Last updated: 29 July 2026
1. What this covers
This policy explains the cookies and similar technologies used on dna.forex, including data stored in your browser that is not technically a cookie. It sits alongside our Privacy Policy, which explains how we handle personal data more generally.
2. What we use
We use a small number of strictly necessary items and nothing else. An authentication session cookie keeps you signed in as you move between pages. A two-factor authentication cookie remembers a device you have already verified, so you are not asked for a code on every visit. Your browser's local storage holds your theme preference and, if you use the support chat, your chat history. This stays on your device and is not sent to us.
3. What we do not use
We do not use advertising cookies, tracking pixels, social media cookies, or third-party analytics cookies. We do not profile you, we do not follow you across other websites, and we do not sell or share browsing data. Our website analytics are provided by Vercel and are cookieless: they count page views without storing anything on your device or identifying you.
4. Why we do not ask for consent
Under the Privacy and Electronic Communications Regulations, cookies that are strictly necessary to provide a service you have requested do not require consent. Everything listed in section 2 is in that category. Without them you could not stay signed in or use two-factor authentication. Because we set no non-essential cookies, there is nothing for you to accept or reject. If that ever changes, we will ask for your consent before setting anything new, and this page will be updated first.
5. Controlling cookies yourself
You can delete or block cookies through your browser settings, and clear local storage the same way. If you block our authentication cookie you will not be able to sign in, because there would be no way for the site to know who you are between one page and the next. Instructions for each browser are on its own support site.
6. How long they last
The authentication session cookie lasts for the duration of your signed-in session and is refreshed while you remain active. The two-factor device cookie lasts until it expires or you sign out. Local storage persists until you clear it. None of these are used for any purpose other than the one described.
7. Changes
If we add anything to this list we will update this page and, where consent is required, ask for it before the item is set. The date at the top of this page shows when it was last changed.