UK GDPR

Privacy Notice

What we collect, why, what allows us to, who else handles it, how long we keep it and what you can make us do about it. Last updated 27 October 2026. Version 1.3.

The short versionWe collect very little: an email address if you join the waitlist, your name and email when you buy something, your Discord username if you give us one, and - for BTR Bot only - a one-way fingerprint of the computer you install it on, so one licence runs one machine. We never see your card details and we never see your broker password. We do not sell or rent anything to anyone. You can ask us to delete what we hold, and you can complain to the Information Commissioner.

1. Who we are, and how to reach us

Data controller: BTRTrades (United Kingdom). Full legal name and postal address are available on request by email.
Email: [email protected]

We have not appointed a data protection officer. Write to the email address above and it reaches the person responsible for your data.

2. What this notice covers

It covers btrtrades.uk, the emails we send you about an order, the BTR Bot software you install, and the parts of the BTRTrades Discord server that we run. It does not cover Stripe's checkout pages, Discord's own platform, Instagram, or your broker. Those are separate companies with their own notices.

What this site keeps on your device, and how to switch off the one optional item, is set out in the cookie notice.

3. What we collect, why, and what allows us to

3.1 Joining the waitlist

What we collect: your email address, your first name if you choose to give it, which product you asked about, and the fact that you ticked the consent box.
Where it goes: straight into a private staff channel on our Discord server. It is not written to our database. That means Discord holds it for us until we delete the message.
Why: so we can email you when that product is released.
What allows us to: your consent - Article 6(1)(a) of the UK GDPR - and, for the marketing email itself, the same consent under the Privacy and Electronic Communications Regulations.
Changing your mind: reply to any email, or write to us, and we will remove you. Withdrawing consent is as easy as giving it, and it does not affect anything we did before you withdrew it.
Not collected: your IP address is not stored with your signup. It is used briefly to stop automated abuse - see section 3.8.

3.2 Buying something

What we collect: your name and email address as you gave them to Stripe, what you bought, the Stripe checkout session and customer references, the amount of any discount and the promotion code used, and - if you type one in at checkout - your Discord username.
What we never receive: your card number, expiry date or security code. Payment happens entirely on Stripe's pages.
Where it goes: a Cloudflare D1 database that we control, in a table of orders. A copy of the order also exists in your Stripe account records.
Why: to deliver what you bought, to give you support afterwards, to keep the accounting records the law requires, and to prevent the same order being fulfilled twice.
What allows us to: performing our contract with you - Article 6(1)(b) - and, for the accounting records, our legal obligations - Article 6(1)(c).

3.3 Your licence or access key

What we collect: the key itself, your email address, your Stripe subscription, session and customer references, your Discord username if you gave one, whether the key is active, suspended or withdrawn, and - for BTR Bot - the machine fingerprint in section 3.4 and the time it last checked in.
Where it goes: the same Cloudflare D1 database, in a table of licences.
Why: so your key opens what you paid for, so a cancelled subscription stops working, and so a leaked key cannot be run by other people.
What allows us to: performing our contract with you - Article 6(1)(b).

3.4 The BTR Bot machine fingerprint

This deserves its own section, because it is the only thing we collect that comes from your hardware.

What it is: when the software first runs, it works out a fingerprint of the computer it is running on. On Windows it takes the identifier Windows creates for your installation (Windows calls it the MachineGuid), which stays the same through Windows updates and a change of computer name and normally changes only if Windows is reinstalled. If that identifier cannot be read, it takes three things instead - your computer's name, the hardware address of its network adapter and the name of its operating system - and joins them together. Either way it runs the result through a one-way cryptographic hash and sends us the first 32 characters. A licence first activated before 1 October 2026 was bound to an older fingerprint, a one-way hash of your computer's name, the hardware address of its network adapter and its operating system version; the software keeps using that one until a Windows update or a change of computer name means it has to move to the new one.
What it is not: the hash cannot be turned back into the Windows identifier, your computer name, your network address or anything else. We never see those values.
Why we treat it as personal data anyway: it is stable, it is unique to one computer, and we store it in the same record as your email address. Under the UK GDPR that makes it information relating to an identifiable person, and we would rather tell you that plainly than hide behind the fact that it is hashed.
Why we use it: your subscription licenses one computer. The fingerprint is how we stop a leaked key running the software on several machines at once. If we did not do this, the subscription would not be enforceable at all.
What allows us to: our legitimate interests - Article 6(1)(f) - in preventing licence abuse. We weighed that against the effect on you: the value identifies a machine and not a person, it cannot be reversed, we use it for nothing else, and one machine per licence is a term you agree to when you buy. Performing the contract - Article 6(1)(b) - applies for the same reason. You have the right to object; see section 8.
Do you have to give it? Yes, if you use BTR Bot. It is a requirement of the licence (one licence, one computer). The software cannot activate or check your licence without it, so without it the software cannot trade. Nothing obliges you to buy BTR Bot in the first place.
The check-in time: we also record when the software last contacted us, which it does when it starts and then about every 30 minutes while it is running. That shows, to within about half an hour, when you last had it running. It is what tells us a licence is live, and it is what lets us tell you why the software has stopped if your payment has failed.

What the software never sends usNot your broker password, not your full account number, not your journal file and not your other files. Unless and until you connect a phone (section 3.10), it also sends none of your balances, positions or trades: the only things it sends are your licence key and the fingerprint above. When a licence has to move to a new fingerprint (for example a licence activated before 1 October 2026 moving to the new one), it also sends the fingerprint it was bound under, so we can recognise the same computer; we compare the two and keep only the new one. Everything the software does happens on your own computer.

3.5 Support tickets in Discord, and the Report a problem file

What we collect: your Discord username and Discord user ID, which ticket channel was opened, which member of staff picked it up and closed it, and the times.
Where it goes: the ticket record is in our Cloudflare D1 database. The conversation itself stays in Discord.
Why: so a ticket is not lost, so we can see whether it was answered, and so we can find it again if you come back.
What allows us to: performing our contract with you - Article 6(1)(b) - or, where you are not a customer, our legitimate interest in running a support desk - Article 6(1)(f).

The Report a problem file. The Report a problem button on the BTR Bot desk makes one file on your own computer for our support team. It is sent nowhere unless you send it yourself.

What is in it: the bot's own logs and status, its version and your Windows version, your account record and broker mapping, and the recent lines of its trading logs. That can include your account number, your balances and your trades. Passwords, keys and tokens are taken out, your licence key is cut to its last four characters, and your Windows user name is left out.
How to send it: by email to [email protected], or in a private support ticket on our Discord. Never post it in a shared channel.
Why: so we can see what went wrong and put it right for you.
What allows us to: performing our contract with you - Article 6(1)(b).
How long: we keep the file for 12 months after we receive it, then delete it.

3.6 Emails you send us

If you email us we keep the message and our reply. What allows us to is our legitimate interest in dealing with your enquiry and keeping a record of what was agreed - Article 6(1)(f) - or performing our contract with you, if you are a customer.

3.7 Website analytics

What happens: unless you turn it off, each page loads a counter from Cloudflare Web Analytics. Cloudflare states publicly that it does not store anything on your device and does not build a profile of you. Loading it does tell Cloudflare your IP address and your browser's user-agent string, because that is how the request reaches them.
Why: so we can see which pages are actually used and whether the site is slow.
What allows us to: our legitimate interests - Article 6(1)(f) - in understanding and maintaining our own website.
Your control: a Cookie settings button in the footer of every page turns it off at any time, free of charge. See the cookie notice.

3.8 Stopping abuse of the waitlist form

When you submit the waitlist form, our server reads the IP address the request came from and keeps a count of submissions against it for 60 seconds, held in Cloudflare's edge cache, so that automated scripts cannot flood the form. It expires by itself. It is not written to our database and it is not stored with your signup. What allows us to is our legitimate interest - Article 6(1)(f) - in keeping our own systems usable.

3.9 The gated course library

To open the library your browser sends back the access-key cookie described in the cookie notice, and our server checks it against your entitlement on every request. Audio links are signed and stop working after an hour, so a link copied out of the page is useless to anyone else. What allows us to is performing our contract with you - Article 6(1)(b).

3.10 The phone desk: BTR Bot on your phone

Off until you switch it on. Nothing in this section happens unless you press Connect your phone on the bot's desk and pair a phone with the code it shows. Until then the software asks our site one question - whether the phone desk is available at all - and sends nothing about you with it.

What the software sends once a phone is connected: a status report about once a minute while it is running (and, while a pairing code is on the desk, a short check every few seconds with no report in it). Each one is identified by your licence key and the computer fingerprint in section 3.4, so that we know which bot it comes from. A report contains, and contains only:
- the bot: whether it is running, paused or stopped, its version, its licence status, the time of the report, and its trading schedule (the last and next cycle, whether new entries are allowed, whether the news calendar can be read, and any update waiting to install);
- each connected account: the name you gave it, the firm, the platform, the name of your broker's server and the last three digits of the account login (never the full login, and never the password, which the software does not hold), the currency, the balance and equity, today's and the open profit or loss, whether it is in a trade, and any reason it cannot trade;
- your totals: the profit or loss since you connected your accounts, today's and the open profit or loss, how many trades are open, and how many of your closed trades were winners out of how many;
- your results by day, for the calendar: for each of the last 62 days on which a trade closed, in each currency, the profit or loss, how many trades closed, how many were winners and how many were longs and shorts;
- your results by period, for the share picture: for today, this week, this month and since you connected your accounts, in each currency and for each account (by the name you gave it, with any account number masked), the profit or loss, the money made by winning trades, how many trades and how many winners, and up to 12 of that period's closed trades (account, instrument, direction, time and result);
- the trades the bot has open (account, instrument, direction, size, entry, current price, stop, target and open profit or loss) and the last 20 trades it closed (account, instrument, direction, entry, exit, time and result);
- each account's prop-rule meters (for example drawdown used, daily loss used and progress to the profit target);
- the next session times, and any warning the desk is showing.
When a trade opens or closes, or the bot pauses, resumes, stops or needs you, the report also carries a one-line note of it for your notifications. It sends no file paths, no settings files and nothing else from your computer. When you stop the bot on the computer it sends one last report saying so.
What your phone sends: when you pair, the pairing code and a short name for the phone (such as "iPhone"); afterwards, a token we issue that identifies that phone; and, only if you turn notifications on, the push subscription your phone's browser creates (an address at Apple, Google or Mozilla and two keys). Pause, Resume and Close all from the phone are stored as commands until the bot collects them, with the outcome the bot reports.
Why: to show your bot to you on the phones you have connected, to carry your Pause, Resume and Close all to the bot, and to send the notifications you asked for (a trade opened, a trade closed, a breaker, or the bot not reporting for ten minutes during market hours). Nothing else: we do not profile you with it or make decisions about you from it.
Where it goes: the same Cloudflare D1 database, in tables set aside for the phone desk. A notification travels through your phone's own push service (Apple, Google or Mozilla), encrypted so that service cannot read it.
What allows us to: performing our contract with you - Article 6(1)(b) - for the desk you asked for by connecting a phone; your consent - Article 6(1)(a) - for notifications, which you can withdraw on the phone at any time.
How long: the status report is one record per licence, replaced by the next report; closed trades and the alerts we sent are kept for 30 days; commands for 7 days; a pairing code stops working after 10 minutes, and its record is deleted within about 20 minutes after that. Disconnecting a phone deletes that phone's record at once, and when it was the last phone connected, everything stored for the phone desk goes with it. When your subscription ends, everything stored for the phone desk is deleted. See section 7.
Stopping abuse: when a phone claims a pairing code, or a request reaches the phone desk with a licence key we do not know, our server counts it against a one-way hash of the IP address it came from, so that automated scripts cannot guess codes or keys. The count is kept in the same database, is not stored with anything else about you, and is deleted within about two hours. What allows us to is the same as in section 3.8.

4. What we never do

We do not sell, rent or trade your data. Not to anyone, not ever.
We do not use your data for advertising, and we run no advertising cookies or tracking pixels.
We do not send marketing emails to anyone who has not asked for them.
We do not receive, store or transmit your broker credentials. They stay on your own computer.
We do not profile you, score you, or make automated decisions that have a legal or similarly significant effect on you. The licence check is automatic, but all it checks is whether a subscription has been paid.

5. Who else handles your data

These are our processors. Each one only gets what it needs to do its job, and each one is bound to act on our instructions.

Cloudflare - hosts this website, runs the code behind it, holds our database and our product files, provides DNS and security, and provides the page-view counter in section 3.7.
Stripe - takes the payment and holds the payment record. Stripe also decides some things about your data for itself, particularly for fraud prevention and its own legal obligations, so for those purposes Stripe is a controller in its own right and Stripe's own privacy policy applies.
Resend - sends our order, delivery, licence and access emails. That means Resend handles your email address, your first name and, for PDF products, the file being sent to you.
Discord - runs the community server, the private staff channel that receives waitlist signups and delivery alerts, and the support ticket system.

One thing worth knowing. If an order email fails to send, an alert is posted into our private staff channel on Discord so we can send it by hand, That alert identifies the order by its checkout reference only, it does not contain your email address, and it goes to a channel only we can see.

Other services the BTR Bot contacts from your computer. Apart from our own site and your broker (through your trading platform), the software fetches a few public files from the services below. They are not our processors and we pass them nothing: no licence key, no account details and nothing about you. Like any request over the internet, each one can see the internet address of the computer asking.

Yahoo Finance (query1.finance.yahoo.com) - about every 20 minutes while the bot is running, it fetches public 15-minute price and volume data for three US index funds (QQQ, SPY and DIA), which the bot uses to judge trading volume. The request carries only the fund's symbol.
faireconomy.media (nfs.faireconomy.media) - about every 12 hours, and every 15 minutes while it has no up-to-date copy, it fetches the public economic calendar for the week, which the news pause reads. The request carries only the file's address.
MetaQuotes (download.terminal.free and download.mql5.com) - only when you press Install MetaTrader 5 for me on the setup page, or when the Windows VPS setup installs MetaTrader 5 for you, it downloads the MetaTrader 5 installer and checks that MetaQuotes signed it. The request carries only the file's address.
Microsoft Sysinternals (download.sysinternals.com) - only on a Windows VPS, when the VPS setup or the installer's This is a VPS: keep BTR Bot running after restarts step switches on automatic sign-in, it downloads Microsoft's Autologon tool and checks that Microsoft signed it. The Windows password you give it is stored by Windows on that VPS; it is never sent to Microsoft or to us.

6. Sending data outside the UK

Cloudflare, Stripe, Resend and Discord are all United States companies, and your data may be processed outside the United Kingdom.

Where that happens, the transfer is protected by a safeguard that UK data protection law recognises, set out in each supplier's data-processing terms: the UK's approved clauses for international transfers (the International Data Transfer Addendum to the EU standard contractual clauses, under Article 46 of the UK GDPR), or, for a supplier certified under it, the UK Extension to the EU-US Data Privacy Framework, which the UK government has found gives adequate protection. To find out which safeguard applies to a supplier, or to get a copy of it, email [email protected].

7. How long we keep things

We would rather be honest than tidy here. Our software does not currently delete any of these records automatically. The periods below are the periods we work to, and they are applied by hand.

Order and payment records: six years from the end of the tax year in which the sale falls, the period UK tax rules require us to keep business records.
Licence and access-key records: while the licence or access is live, and for 12 months after it ends so that we can deal with any dispute or reinstatement; then deleted.
The machine fingerprint and the last check-in time: deleted 12 months after the licence ends; they have no purpose once it has.
The phone desk (section 3.10): these are the only records our software does delete by itself. The latest status report is replaced by the next one; closed trades and the alerts we sent go after 30 days; commands after 7 days; pairing records within about 30 minutes of the code being made; the abuse counts in section 3.10 within about two hours. Disconnecting your last phone, or your subscription ending, deletes everything stored for the phone desk at once.
Waitlist signups: until the product you joined the list for launches and you have been told, or until you ask us to remove you, whichever is first.
Support tickets: for as long as the matter is open, then for as long as we need a record of how it was resolved.
Report a problem files you send us: 12 months after we receive them, then deleted.
Emails: for as long as we need them to answer you and to keep a record of what was agreed.
Analytics: held by Cloudflare under Cloudflare's own retention period.

8. Your rights

Under the UK GDPR you have the right to:

Be told what we do with your data - which is what this notice is for.
Get a copy of the personal data we hold about you.
Have it corrected if it is wrong or incomplete.
Have it deleted, where we no longer need it or where you withdraw consent. We may have to keep accounting records even so, and we will tell you if that is the case.
Restrict what we do with it while a dispute about it is sorted out.
Take it with you in a portable format, where we hold it on the basis of your consent or your contract.
Object to anything we do on the basis of legitimate interests, including the machine fingerprint and the page-view counter.
Withdraw consent at any time, where consent is what allows us to process it.
Not be subject to a decision made solely by automated means that has a legal or similarly significant effect on you. We do not make any such decisions.

How to use them. Email [email protected]. It is free. We answer within one month, and we will tell you if a complex request needs longer. We may ask you to confirm who you are first, so that we do not hand your data to somebody else.

9. Complaining

If you are unhappy with how we have handled your data, please tell us first - we would rather fix it. You can also complain to the Information Commissioner's Office at any time, and you do not have to come to us first.

Website: ico.org.uk
Helpline: 0303 123 1113
Post: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF

10. How we look after it

The whole site is served over HTTPS and browsers are told never to use anything else.
A content security policy restricts what code a page is allowed to load, and the site cannot be embedded in another site's frame.
The cookie that opens the paid library cannot be read by any page script, and is only sent over HTTPS.
Paid files are never public. They are held in private storage and released only by code that has already checked your entitlement, and audio links are signed and expire after an hour.
Payment notifications from Stripe are cryptographically verified before we act on them, and the software checks its licence only with our own website, over an encrypted HTTPS connection.
Your broker credentials never reach us at all.

11. Children

Our products are not intended for anyone under 18 and we do not knowingly collect data about children. If you believe a child has given us their data, tell us and we will delete it.

12. Changes to this notice

If we change how we use your data we will update this page and raise the version number at the top. Where the change is significant we will tell customers by email.

Related: the cookie notice, the terms and conditions and the risk disclaimer.