Privacy policy
Last updated 17 October 2026.
Who is responsible. TrainYourCS is run by TrainYourCS trading as TrainYourCS, a sole trader in the United Kingdom — one person, not a company — who is the data controller for the personal data described here. We do not publish a postal address; email reaches us for everything, including requests about your data. Contact support@trainyourcs.com about anything on this page.
What we hold, and why
Your account. Your name, email address, a hash of your password (never the password itself), an optional in-game name, and when you last signed in. We need these to give you an account and to let you back into it. Your teammates see your in-game name, not your real name.
Your team. Which teams you belong to and your role on each, plus the training you have been assigned, opened and completed; the team’s calendar, tasks, stratbook, opponent notes, demos and recordings. Owners and coaches of your team can see your training records — that is what the product is for, and it is the basis on which you joined.
Linked accounts, if you connect them. Connecting Steam stores your Steam ID, which is how the app knows which player in a parsed demo is you. Connecting FACEIT stores your FACEIT id, nickname, match history and elo readings. Connecting Discord stores your Discord user id and username, so the bot’s commands know which account is yours. All three are optional, all can be disconnected from your account page, and disconnecting removes the link.
Your team’s Discord, if the owner connects it. We store the server, channel and role the owner chose, and post the team’s training, calendar and strat announcements there — session titles, in-game names and strat images. We never post a player’s training record or anything from their account page.
Demo files. A demo contains the names and Steam IDs of everyone in that match, including people who have no account here. We parse it into positions, rounds and statistics. The original file is deleted after 30 days; the parsed data stays with the team that uploaded it.
The TrainYourCS recorder, if you use it. When Record is pressed it captures your screen, your microphone and your computer’s sound until it stops, and uploads them to your team, where your teammates, owners and coaches can watch them. Nothing is recorded until you (or, if you turned on “Record together”, a teammate while you are in CS2) press Record. Your microphone and computer sound can include other people’s voices — your team’s comms or a voice call — and those recordings are shared only with your team. For each signed-in copy of the app we hold which account it belongs to, the app version, when it was signed in and when it was last seen — not your computer’s name. While the app is open it tells us every few seconds whether you are in CS2 and whether you are recording, so your team can see who is ready; that is kept in memory only and never written down. If you were recorded and want a recording removed, ask your team’s owner or email us.
Training clips. A clip is a start and end point in a recording (or a moment in a demo) with an optional note. It belongs to a training module, and who has done it is recorded like any other training.
Payments. When you buy a plan you pay Link (Sold through Link, LLC, part of Stripe), which sells the subscription as the merchant of record. Link collects your payment details, billing address and email at checkout and is responsible for them under its own privacy policy. Card details never reach us. We receive a customer reference, the plan, its status and renewal date, and enough about the payment to know your team has paid.
Support tickets, if you open one. What you write, any screenshots you attach, which team it is about if you choose one, and our replies. Read only by you and by our support staff. Staff may add internal notes to a ticket, which are kept with it.
Security records. Sign-in attempts, successful and failed, with the IP address they came from — this is what makes account lockout possible after repeated failures. Deleted after 30 days. Each browser you are signed in on is noted in words — the browser and the system, like “Chrome on Windows” — with when it signed in, so your account page can list where you are signed in; that goes when the browser signs out or its sign-in runs out. Actions taken by staff in the admin panel are logged with their IP address, so that support access to an account can be accounted for afterwards. Like any web server, ours keeps short-lived access and error logs, which include IP addresses and the address an email was sent to.
Visits to the public pages — only if you say yes. If you press Accept on the cookie banner, we count your visits, but do not track them. We record that a page was viewed on a date, which site linked to it and which page a visit began on, as running totals. To tell one person’s four page views from four people’s one, each visit is hashed together with a secret that is generated fresh every day and never written to disk — so the hash cannot be matched back to an address once the day has turned over. We do not store IP addresses for this and no third party is involved. Until you answer, or if you press Reject, your visits are not counted at all; nor are they while you are signed in. The hashes are deleted after 90 days.
Cookies, and your choice
We ask you one thing: whether your visits to the public pages may be counted, as described above. Until you answer, they are not. Reject keeps it that way; Accept counts the page you are on and the ones you open after it. If your browser sends Global Privacy Control, we take that as Reject and do not ask.
The cookies this site sets:
- tyc_consent — your answer, yes or no, kept for six months so we do not ask on every page. It holds nothing else and is only there to remember your choice.
- tyc.sid — the session cookie. Set when you sign in, or when you open the sign-in, sign-up or password-reset form, because the form’s protection against forged requests needs it. It lasts up to 30 days, renewed while you use the site, so you stay signed in. It is strictly necessary for a service you have asked for.
There are no advertising, social-media or third-party cookies, and nothing on the public pages is loaded from another company. If you pick a currency for prices, that choice is kept in your browser’s local storage and never sent to us. Which currency prices first appear in is guessed in your browser from its time zone; that is not sent to us either.
Why we are allowed to
Running your account, your team, your recordings and anything you pay for is necessary to provide the service you signed up for (contract). Where a recording captures someone else’s voice, we rely on the legitimate interest of the team in reviewing its own matches — kept to the team, for a limited time, and removable on request. Security records and the staff audit log are in our legitimate interest in keeping accounts safe. Every kind of email we send on our own can be turned off on its own, from your account page or from the link in each one, and reminders go only to an address you have confirmed. The only emails without that link are a password reset or a confirmation link, sent when you ask for one. Billing records are kept because the law requires it.
Who else sees it
Only the services needed to run TrainYourCS, and only what each one needs:
- Link and Stripe — the sale and the payment, as described above.
- Our email provider — sends account email such as invitations, password resets and reminders. It sees the address and the message.
- Our hosting provider — the server the app runs on, in the United Kingdom. Your data, demos and recordings are stored there.
- Steam and FACEIT — only if you connect them, and only to identify your account and read your own match data.
- Discord — if you link your account, or your team’s owner connects a server: Discord receives the announcements described above and tells us which Discord account ran a command.
- Embedded content — if your team embeds a Google Doc, a YouTube video or a Twitch clip in the stratbook, opening that page loads it from Google, YouTube or Twitch, who will see the request as they would on any site.
We do not sell personal data, we do not share it for advertising, and we do not use it to train machine-learning models.
Link, Stripe, Discord, FACEIT, Steam and some email providers are based outside the UK, mostly in the United States. Where they receive personal data it is under the safeguards UK data protection law requires for such transfers, such as the UK–US data bridge or standard contractual clauses.
How long we keep it
Account and team data for as long as the account or team exists. Original demo files for 30 days. Recordings for 7 days on Team and 21 days on Pro, unless the team deletes them sooner, and for as long as a training clip points at them. Sign-in records for 30 days. Support tickets and their screenshots for as long as your account exists — they are deleted with it. Visitor hashes for 90 days. Aggregate visit counts, which identify nobody, indefinitely. Link keeps its own payment records under its own policy. Ask us to delete your account and we will remove your personal data within 30 days, except anything we must keep for accounting.
Your rights
Under UK GDPR you can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to have it sent to another provider. Email support@trainyourcs.com and we will answer within one month. If you are not happy with our answer you can complain to the Information Commissioner’s Office at ico.org.uk.
A note on team data. If you ask us to delete your account, your personal details go — but the content you created for a team belongs to that team and stays with it, as clause 4 of the terms says. Ask the team owner if you want that removed too.
Children
Accounts are for people aged 13 and over, and anyone under 18 should check with a parent or guardian before signing up. If you believe a younger child has an account, tell us and we will delete it.
Changes
If this policy changes materially we will say so by email or in the app. The date at the top always reflects the last change.
See also the terms of service.