Mark TRD School
Legal · Privacy

Privacy policy

What is collected, why, how long it is kept, and how to have it removed. There is no contact form on this website, so most of this concerns the Telegram bot.

Last updated: 26 August 2026

1. Who is responsible

The controller of the personal data described here is Individual Entrepreneur Petruk Oleksandr Romanovych, 44/140 Molodizhna Street, Kvasyliv, Rivne district, Rivne region, Ukraine, individual tax number 5486328970, which operates the website mark-trd-school.com and the associated Telegram bot.

For any privacy question or request, write to mark-trd-school@gmail.com.

2. What we collect

2.1 When you browse this website

  • Server log data, collected automatically by the hosting provider: IP address, date and time, requested page, referring page, browser and operating system. Used for security and for keeping the site running.
  • A local storage entry recording your choice in the cookie notice, so that you are not asked again. It contains only the value "accepted" or "declined".
  • Analytics data. No analytics or advertising measurement is in use on this website at present, so none is collected. If one is added later, it will be listed here and in the cookie policy, and it will only load after you accept it in the cookie notice.

This website has no contact form, no newsletter sign-up, and no advertising pixel that fires without consent.

2.2 When you click through to the Telegram bot

The button that opens the bot goes through a link-tracking service before it reaches Telegram. That service records that a click happened and passes an anonymous click identifier along with it, which lets us tell which page or advertisement a booking came from. It does not receive your name, and it does not see anything you later send to the bot. Nothing is stored on this website as a result.

2.3 When you use the Telegram bot

  • Your Telegram user ID and username, and your first name as shown in Telegram.
  • Your answers to the bot: time zone, stated experience level, and what you want to learn.
  • The messages you send to the bot and the sessions you book, attend or cancel.
  • Notes Mark keeps about what has been covered, so that a session does not repeat the previous one.

The bot does not ask for and must not be sent identity documents, financial account details, payment card numbers, passwords or authentication codes. If you send such information anyway, it is deleted.

2.4 When you email us

Your email address, your message, and anything you choose to include in it.

3. What we do not do

  • We do not sell, rent or trade your personal data.
  • We do not pass your details to brokers, lead buyers, advertisers or affiliate networks.
  • We do not build advertising profiles about you, and we run no advertising trackers on this site. The only measurement is the click identifier described in section 2.2, which is attached to the outbound link and not to your visit here.
  • We do not make automated decisions with legal or similarly significant effects about you.

4. Why we use it, and on what legal basis

PurposeDataLegal basis (UK/EU GDPR)
Arranging and running your sessionsTelegram identifiers, answers, schedule, session notesPerformance of a contract, or steps taken at your request before entering one
Answering emailsEmail address, messageLegitimate interest in responding to enquiries
Keeping the website available and secureServer log dataLegitimate interest in security and reliability
Measuring how the site is used (not currently done)Analytics data, if analytics is ever switched onYour consent, given in the cookie notice and withdrawable at any time
Meeting legal obligations and defending claimsAny of the above, as strictly requiredLegal obligation and legitimate interest

5. How long it is kept

  • Bot conversations and session records: for the duration of the program and 12 months afterwards, then deleted.
  • Email correspondence: 24 months from the last message.
  • Server logs: as configured by the hosting provider, typically up to 30 days.
  • Analytics data: none is collected. If analytics is switched on later, up to 14 months, in aggregate form.
  • Your cookie choice: stored in your own browser until you clear it or 12 months pass.

6. Who else processes it

We use a small number of service providers, who act on our instructions only:

  • Telegram Messenger, for the bot and the messages you send to it. Telegram is an independent controller of your account data under its own privacy policy; we can only see what you send to the bot.
  • Cloudflare, which hosts this website and its logs.
  • The link-tracking service behind the bot button, which registers the click and forwards you to Telegram.
  • Google (Gmail), which handles the mailbox listed on this site.
  • Telegram, used for the screen-share session itself.

Some of these providers may process data outside the UK or the European Economic Area. Where that happens, transfers are covered by an adequacy decision or by Standard Contractual Clauses.

7. Your rights

Subject to the conditions in applicable law, you may ask us to give you a copy of your data, correct it, delete it, restrict or object to its use, or provide it in a portable format. Where we rely on consent, you can withdraw it at any time without affecting what was done before.

The quickest routes:

  • Send the word DELETE to the Telegram bot, which removes your bot record.
  • Email mark-trd-school@gmail.com for anything else.

We answer within 30 days. If you are not satisfied, you may complain to the data protection authority in your country; in the UK that is the Information Commissioner's Office, and in the EU it is your national supervisory authority.

8. Children

This website and these sessions are intended for people aged 18 or over. We do not knowingly collect data from anyone under 18. If you believe a minor has contacted the bot, write to mark-trd-school@gmail.com and the record will be deleted.

9. Security

Access to the bot data and session notes is limited to Mark and, where strictly necessary, the operator of the website. Accounts are protected by two-factor authentication. No system is perfectly secure, which is another reason the bot asks for so little.

10. Changes

If this policy changes, the new version appears here with a new date at the top. Material changes affecting current students are announced through the bot.