The controller of your personal data is [operator name, address — to be published], reachable at [email protected].
What we collect, and why
| Data | Why | Legal basis |
|---|---|---|
| Telegram username and ID, email if you give one | To talk to you, deliver and support services | Contract |
| Services ordered, their configuration, IP addresses | To provide the services | Contract |
| Invoices and payments (amounts, transaction IDs, wallet addresses used) | Billing and accounting | Contract, legal obligation |
| Account security data (login times, addresses, 2FA status) | Protecting your account | Legitimate interest |
| Traffic metadata on protected services (client addresses, request lines, timings) | Filtering attacks and investigating abuse | Contract, legitimate interest |
We do not sell personal data and do not use it for advertising.
This website
This website sets no cookies, uses no analytics or tracking, and has no forms; the Telegram request builder only opens the chat in your browser. Our hosting provider and Cloudflare may log technical data (address, browser, time) to deliver and protect the site.
Retention
- Customer and billing records: as long as you are a customer, then as long as accounting law requires (up to [10] years for invoices).
- Access logs and traffic metadata of protected services: [14] days, longer only when tied to an open abuse case.
- Security logs: [90] days.
Who processes data for us
The companies that process personal data on our behalf are listed on the sub-processors page. Transfers outside the EEA rely on adequacy decisions or standard contractual clauses.
Your rights
You may ask to access, correct, delete or export your data, and object to or restrict processing based on legitimate interest. Write to [email protected]; we answer within one month. You may also complain to your data protection authority (in Romania, the ANSPDCP).
Security
Passwords are stored as argon2id hashes, sensitive fields are encrypted, backups are encrypted before they leave our servers, and staff accounts require two-factor authentication.