Privacy Policy
This policy explains what personal data powersport.one and the MNTLG Telegram bot @powersports_manuals_bot collect, why, for how long, who processes it, and how you get it back or have it deleted. Short version: there are no advertising trackers, no sale of data, and no passwords or card numbers.
1. Who is responsible for your data
The Operator of powersport.one (the owner of the MNTLG manual archive) is responsible for the processing of personal data of visitors to the Site and of users of the bot. In the terms of the GDPR, the Operator acts as a person responsible for processing within the meaning of Article 4(7) — a private, non-corporate responsible party.
The Operator is not established in the European Union. The Site and the bot are aimed at users in the United States, in Europe and in other regions, so processing takes place outside the EU and the EEA. Any question about this policy, or any request concerning your data, goes to @yitshock.
2. What is collected
2.1 In the bot
| Data | Where it comes from | Why it exists |
|---|---|---|
| Telegram user ID | Sent by Telegram when you open the bot | Identifies you so access can be granted and delivered |
| Telegram username or display name | Telegram, only if you have set one | Used to address you in the bot |
| Interface language and the language you selected | Your settings in the bot, or auto-detection from your Telegram language | To answer you in the right language |
| History of your queries and commands in the bot | Your messages | To serve the answer, keep a history of what was asked, and debug failures |
| Payment records: method, amount, timestamp, transaction reference, wallet address used | The payment provider and Telegram | To confirm payment, grant access, and keep accounting records |
| Grant status: what was granted and when | Operator action | To know what you are entitled to and to answer support requests |
The IP address of the Telegram servers that connect to the bot is not stored by the Operator.
2.2 What is not collected
- Passwords — the bot has no password and the Site has no login. Your Telegram account password never reaches the Operator.
- Card data — Telegram Stars are charged inside Telegram, and USDT transfers are settled on the TRC-20 network. No bank card number, CVV or card expiry is seen, requested or stored by the Operator.
- E-mail addresses — the Operator does not ask for one and does not collect one.
- Advertising or analytics identifiers — none are used, on the Site or in the bot.
2.3 On the Site
The Site has no accounts, no contact form that stores submissions and no analytics scripts. The hosting infrastructure keeps short-lived technical request logs (such as the requested path, a timestamp and the connecting IP address) for security and troubleshooting; those logs are not linked to your bot account and are not used to build a profile of you.
3. Why the data is processed
| Purpose | Legal basis (GDPR Art. 6) |
|---|---|
| Deliver the manuals you bought and operate your access | Art. 6(1)(b) — performance of a contract |
| Confirm payments, grant access, keep accounting and tax records | Art. 6(1)(b) and 6(1)(c) — contract and legal obligation |
| Operate and improve the search index and the bot | Art. 6(1)(f) — legitimate interests of the Operator in running the archive |
| Answer enquiries and data-subject requests | Art. 6(1)(c) and 6(1)(f) |
| Keep the archive secure and prevent abuse of the access-grant process | Art. 6(1)(f) |
There is no profiling and no automated decision-making that produces legal or similarly significant effects. Your data is not used for advertising, and it is not sold.
4. How long it is kept
| Data | Retention |
|---|---|
| Telegram ID, username, selected language | While your access is active, and up to 12 months after your last interaction, unless you ask for deletion |
| Bot query and command history | 12 months, rolling |
| Payment records and transaction references | 5 years, for accounting and tax purposes |
| Grant log (what was granted, when) | 12 months after the last grant |
| Correspondence about enquiries and rights requests | 3 years |
| Hosting request logs | Short period, set by the hosting provider for security and troubleshooting |
When a period ends, the data is deleted or anonymised. Data that must be kept for tax or accounting reasons is kept for that reason only, and is not used for anything else.
5. Cookies and local storage
The Site sets no cookies. It stores one item in your browser’s localStorage: the language you chose, so the page opens in that language next time. localStorage stays in your browser, is not transmitted to the Operator, and is never read by anybody else on your device.
There are no advertising cookies, no analytics cookies and no cross-site trackers on the Site.
The pages load the typefaces Unbounded and Onest from Google (fonts.googleapis.com and fonts.gstatic.com). When your browser downloads a font file, your IP address is transmitted to Google, which may process it under its own privacy terms. Nothing is sent to the Operator by this. If you would rather not contact Google, block those domains in your browser or with a content blocker — the page falls back to system fonts.
6. Who else receives your data
Only the parties that are needed to run the service, and only for that purpose:
- Telegram — the bot runs on Telegram, so your Telegram ID and your messages pass through Telegram’s infrastructure and are handled under Telegram’s own terms and privacy policy.
- Payment providers — Telegram Stars are charged inside Telegram; USDT payments are settled on the TRC-20 network by its operators. The Operator sees the amount, the time, the wallet address used and the transaction reference — not identity documents or card details.
- Hosting and infrastructure providers — they host the Site, the bot and the storage in which the files are kept, on the Operator’s instructions.
No personal data is sold. No data is shared for advertising purposes. No advertising or analytics scripts run on the Site.
7. International transfers
Processing takes place outside the EU and the EEA, and some recipients are established outside the EEA. Where a transfer is covered by an adequacy decision, that decision is relied on. Where it is not, the transfer is covered by appropriate safeguards — the European Commission’s Standard Contractual Clauses together with supplementary measures where needed, or the provider’s own compliance framework for the relevant service. Data in transit is protected by TLS/HTTPS.
You can ask which safeguards apply to a particular recipient by writing to @yitshock.
8. Your rights
Where the GDPR applies to you, you have the following rights:
- Access (Art. 15) — confirmation of whether your data is processed, and a copy of it.
- Rectification (Art. 16) — correction of inaccurate data, and completion of incomplete data.
- Erasure (Art. 17) — deletion of your data, where one of the grounds applies.
- Restriction (Art. 18) — limiting the processing while a question about it is resolved.
- Objection (Art. 21) — objecting to processing based on legitimate interests, and to direct marketing at any time.
- Data portability (Art. 20) — receiving your data in a structured, machine-readable format.
- Withdrawal of consent (Art. 7(3)) — where processing is based on consent, you may withdraw it at any time, without affecting the lawfulness of processing carried out before the withdrawal.
- Complaint (Art. 77) — lodging a complaint with the supervisory authority in your country of residence, in particular if you are in the EU or the EEA.
You also have the right not to be subject to a decision based solely on automated processing. The Operator makes no such decisions.
9. How to exercise a right
Write to @yitshock from the same Telegram account that holds your access. That is usually enough to identify the data concerned, and it means the Operator does not have to ask for additional identity documents. If a request cannot be matched to an account, the Operator will ask for the minimum additional confirmation needed.
Requests are answered within one month, and sooner where that is possible. There is no charge for this. Deletion requests are carried out across the bot records, the grant log and the query history; what must be kept for tax or accounting reasons is kept for that reason, and is stated when the request is answered.
10. Security
Access to the bot records, the grant log and the file storage is restricted to the Operator. Files are delivered in private Telegram chats rather than from a public link. Data in transit is encrypted by Telegram/HTTPS. No method of transmission or storage is completely risk-free, and no system can promise absolute security.
11. Children
The service is not directed to children below the age at which digital consent is permitted in their country (13 in the EEA under the GDPR, and the equivalent age elsewhere). If you are below that age, do not use the bot without a parent or guardian, and do not send personal information. The Operator does not knowingly collect data from children.
12. Changes to this policy and contact
This policy may be updated. The version in force is the one published on this page with the “last updated” date at the top. The Operator will not use your data for a purpose that is not described here without telling you first.
Related pages: Terms of Service · Copyright notice and DMCA · Trademark notice · Back to the catalog.