This commit is contained in:
162
src/assets/docs/Privacy-Policy_en.md
Normal file
162
src/assets/docs/Privacy-Policy_en.md
Normal file
@@ -0,0 +1,162 @@
|
||||
*This document is an English adaptation of the Privacy Policy originally drafted in Russian. In the event of any disputes subject to resolution in courts of the Russian Federation, the Russian-language version shall prevail.*
|
||||
|
||||
# Privacy Policy
|
||||
###### Version 1.01 dated 15.08.2025
|
||||
|
||||
This Privacy Policy describes the scope of data (including personal data) collection from Users of the Application by the Developer, explains the purposes of such collection, and outlines processing methods.
|
||||
|
||||
## 1. Terms and Definitions
|
||||
1.1. **Bot** – The Telegram account "@tgCrewBot" ([https://t.me/tgCrewBot](https://t.me/tgCrewBot)), programmatically managed by the Developer via Telegram’s API. The Bot provides access to the Application and supports basic inline-mode interaction.
|
||||
|
||||
1.2. **Application** – The Telegram Mini App (TMA) "tgCrew", operating within Telegram’s ecosystem and accessible via the Bot. Though hosted on Telegram’s platform, the Application is developed and provided solely by the Developer. It is not a product of, endorsed by, or legally affiliated with Telegram FZ-LLC. Access requires acceptance of the Terms of Use and this Privacy Policy.
|
||||
|
||||
1.3. **Website** – The official site [https://tgcrew.ru](https://tgcrew.ru), hosting Application documentation and information.
|
||||
|
||||
1.4. **Terms of Use** – The current version available at [https://tgcrew.ru/terms-of-use](https://tgcrew.ru/terms-of-use) and within the Application. In case of discrepancies, the in-Application version prevails. Contractual relations commence upon in-Application acceptance.
|
||||
|
||||
1.5. **Privacy Policy** – This document governing the collection, storage, and processing of User data (including personal data). An integral annex to the Terms of Use. The current version is at [https://tgcrew.ru/privacy-policy](https://tgcrew.ru/privacy-policy) and in the Application. In-Application information prevails in conflicts. Consent is obtained via in-Application acceptance.
|
||||
|
||||
1.6. **Developer** – Individual Entrepreneur Martyshkin Alexey Alexandrovich (OGRNIP 318774600262084, INN 366316608346, Russian Federation).
|
||||
|
||||
1.7. **User** – An individual, legal entity, or authorized representative accepting the Terms of Use and Privacy Policy within the Application.
|
||||
|
||||
1.8. **Administrator** – A User managing the Application via the Admin Panel.
|
||||
|
||||
1.9. **Administrator Account** – Authentication credentials for Admin Panel access.
|
||||
|
||||
1.10. **Chat Participant** – A member of a Connected Chat who may not be an Application User.
|
||||
|
||||
1.11. **Admin Panel** – The Application interface for:
|
||||
- Connecting chats to the Application (see §1.12);
|
||||
- Adding supplemental User data;
|
||||
- Managing Developer remuneration payments.
|
||||
|
||||
1.12. **Connected Chat** – A Telegram chat where the Bot is added with necessary permissions. Only data from Connected Chats is processed.
|
||||
|
||||
1.13. **Application Use** – User actions to view/utilize Application functionality via online interfaces.
|
||||
|
||||
1.14. **Developer’s Representatives** – Persons engaged by the Developer for Application development/support.
|
||||
|
||||
1.15. **Personal Data (PD)** – Any information relating to an identified/identifiable natural person (Federal Law No. 152-FZ, Art. 3.1).
|
||||
|
||||
1.16. **Personal Data Processing** – Any operation(s) performed with PD, including collection, recording, storage, alteration, retrieval, use, transfer, anonymization, blocking, or destruction (Federal Law No. 152-FZ, Art. 3.3).
|
||||
|
||||
1.17. **Operator** – A legal/natural person organizing and/or processing PD, defining processing purposes and scope (Federal Law No. 152-FZ, Art. 3.2).
|
||||
|
||||
1.18. **Automated PD Processing** – PD processing via computer technology (Federal Law No. 152-FZ, Art. 3.4).
|
||||
|
||||
1.19. **PD Provision** – Disclosure of PD to specific person(s) (Federal Law No. 152-FZ, Art. 3.6).
|
||||
|
||||
1.20. **Cross-Border PD Transfer** – Transfer of PD to foreign authorities/entities (Federal Law No. 152-FZ, Art. 3.11).
|
||||
|
||||
1.21. **PD Destruction** – Actions rendering PD irrecoverable (Federal Law No. 152-FZ, Art. 3.8).
|
||||
|
||||
## 2. General Provisions
|
||||
2.1. This Policy governs solely the Developer-User relationship. It does not replace Telegram’s Privacy Policy.
|
||||
|
||||
2.2. This Policy complies with:
|
||||
- Federal Law No. 152-FZ "On Personal Data" (27.07.2006);
|
||||
- Section "4. Privacy" of Telegram’s "Bot Platform Developer Terms of Service".
|
||||
|
||||
2.3. The Developer acts as the **Operator** for PD processing.
|
||||
|
||||
## 3. Acceptance of this Policy
|
||||
3.1. Acceptance occurs by ticking "☑️ I consent to the processing of my personal data and accept the Privacy Policy" within the Application.
|
||||
|
||||
3.2. Application Use implies consent to data collection from Connected Chats (§§4.2-4.4).
|
||||
|
||||
3.3. Non-acceptance requires immediate cessation of Application Use.
|
||||
|
||||
## 4. Data Collection and Processing
|
||||
4.1. Essential User data is required for Application access.
|
||||
|
||||
4.2. **Collected Personal Data**:
|
||||
4.2.1. Automatically collected via Telegram API:
|
||||
- Username, Telegram ID, profile picture, language settings, Telegram Stars transaction data (Administrators only).
|
||||
- Technical data: IP address, request timestamp, requested URL, HTTP status, response size, User-Agent, Referrer.
|
||||
|
||||
4.2.2. **Administrator-provided**:
|
||||
- Email (if used for authentication).
|
||||
|
||||
4.2.3. **Administrator-supplied Chat Participant data** (via Admin Panel):
|
||||
- Full name, phone number, email, employment details.
|
||||
*The Developer ensures lawful processing but assumes no liability for data accuracy. Administrators must secure legal grounds for PD submission. Data is visible only to Users sharing a Connected Chat. Users may request data correction/deletion from Administrators.*
|
||||
|
||||
4.2.4. **User-provided data** (e.g., support requests):
|
||||
- Full name, phone number, email, employment details.
|
||||
|
||||
4.3. **Cookies**: Only HttpOnly cookies (mitigating XSS risks) are used.
|
||||
|
||||
4.4. **Chat Monitoring**: The Bot tracks events in Connected Chats (message/file changes). Relevant data is stored.
|
||||
|
||||
4.5. **User-Input Data Storage**: Project/company/task/meeting details.
|
||||
|
||||
4.6. **Non-Storage**: Chat/files are stored exclusively within Telegram.
|
||||
|
||||
4.7. **No Additional Collection**: Only data specified in §4.2 is collected.
|
||||
|
||||
## 5. Data Collection Purposes
|
||||
5.1. Purposes include:
|
||||
- User identification/authentication (§4.2.1a, 4.2.2);
|
||||
- Technical support (§4.2.1, 4.2.2, 4.2.4);
|
||||
- Administrator notifications (§4.2.1a, 4.2.2);
|
||||
- Telegram Stars transactions (§4.2.1a);
|
||||
- Connected Chat contact management (§4.2.1a, 4.2.3);
|
||||
- Application functionality (§4.2, 4.4);
|
||||
- Security/technical maintenance (§4.2.1b, 4.3).
|
||||
|
||||
5.2. Data is used solely for these purposes, unless required by Russian law or compatible purposes. New purposes trigger User notification.
|
||||
|
||||
5.3. PD processing is **automated**.
|
||||
|
||||
## 6. Data Security
|
||||
6.1. Technical/organizational measures ensure PD confidentiality, integrity, and protection against loss/theft/unauthorized access.
|
||||
|
||||
6.2. Measures include SSL encryption for data transmission.
|
||||
|
||||
6.3. Only authorized Developer personnel access PD. Representatives have no PD access. Security protocols are periodically reviewed.
|
||||
|
||||
## 7. Data Transfer
|
||||
7.1. No third-party transfers except to courts/state bodies when legally mandated.
|
||||
|
||||
7.2. The Developer will not sell/exchange PD without explicit consent.
|
||||
|
||||
7.3. **Data Localization**: All servers reside in Russia. **No cross-border transfers**.
|
||||
|
||||
## 8. User Rights
|
||||
8.1. PD subject rights include:
|
||||
- **Access**: PD copies provided within 30 calendar days.
|
||||
- **Rectification**: Correction via Application functionality, Administrator request, or direct contact.
|
||||
- **Erasure**: Deletion requests honored where legally permissible. Account closure triggers automatic deletion, except where retention is legally required (e.g., fraud prevention, legal obligations).
|
||||
- **Consent Withdrawal**: Withdrawal does not affect pre-withdrawal processing lawfulness.
|
||||
|
||||
8.2. Rights are not absolute and may be balanced against the Developer’s legal obligations/legitimate interests. Refusals include justification.
|
||||
|
||||
## 9. Data Retention
|
||||
9.1. PD is retained only as necessary for collection purposes.
|
||||
|
||||
9.2. Standard retention period: Duration of the Administrator Account.
|
||||
|
||||
9.3. Post-account closure retention occurs only if mandated by Russian law.
|
||||
|
||||
9.4. Extended retention applies for legal compliance, fraud prevention, or dispute resolution.
|
||||
|
||||
## 10. Policy Amendments
|
||||
10.1. The Developer may revise this Policy without prior notice. The revision date will be updated.
|
||||
|
||||
10.2. Users should periodically review the Policy on the Website or in the Application.
|
||||
|
||||
10.3. Continued Application Use after revisions implies acceptance.
|
||||
|
||||
## 11. Miscellaneous
|
||||
11.1. Queries regarding Policy interpretation: Contact the Developer at [a-mart@ya.ru](mailto:a-mart@ya.ru).
|
||||
|
||||
11.2. Contact details (§12) may be used for Policy-related matters.
|
||||
|
||||
## 12. Developer Contact Information
|
||||
**Individual Entrepreneur Martyshkin Alexey Alexandrovich**
|
||||
Legal address: 111394, Russia, Moscow, Perovskaya St., 66, Bldg. 3, Apt. 187
|
||||
OGRNIP: 318774600262084
|
||||
INN: 366316608346
|
||||
Phone: +7 (926) 339-04-25
|
||||
Email: [a-mart@ya.ru](mailto:a-mart@ya.ru)
|
||||
Reference in New Issue
Block a user