1. General provisions
This Privacy Policy applies to the smmese.com website, customer account, order forms, public calculators, API and other SMMESE functions (the “Service”). “Administration” means the party that operates SMMESE.
By using the Service, registering an account or placing an order, the customer confirms that they have read this Policy. A customer who does not agree must stop using the Service.
This Policy describes processing within SMMESE and does not govern independent third-party websites and services opened through external links.
2. Data that may be processed
The actual data depends on the functions used. SMMESE may process:
- email address and information required for registration, login, access recovery and account protection;
- for Google login, the account identifier, email and basic profile information that the customer authorizes Google to provide;
- IP address, User-Agent, date and time, request identifier, technical cookies, session data and security logs;
- links and usernames of Telegram channels, posts and bots, together with selected quote and order parameters;
- order identifiers, price, currency, balance state, statuses, operation history and available execution data;
- technical identifiers and request information when using the API;
- messages, files and other information voluntarily sent to support;
- public information about the selected Telegram channel, post or bot that is necessary to validate the target and execute an order.
3. Data that is not required
SMMESE does not ask for passport data, a full bank-card number, CVC/CVV, a Telegram password, SMS or two-step verification codes, Telegram session files, private keys or other secrets.
Do not send such data through forms or support. Information supplied voluntarily but not needed for the service may be deleted without separate notice.
4. Purposes of processing
Data may be used to:
- create and protect accounts and sessions;
- authenticate customers and restore access;
- calculate, create, execute and display orders;
- maintain balances, payment and operation history;
- validate Telegram targets and monitor measurable results;
- provide API access and protect it from abuse;
- answer support requests and investigate incidents;
- prevent fraud, duplicate operations, unauthorized access and technical abuse;
- meet legal, accounting and security obligations where applicable.
5. Telegram data and order execution
When a customer supplies a public Telegram link or username, SMMESE may read the public information needed to identify the target, detect future posts, record public counters or verify service availability.
SMMESE does not require access to a customer’s personal Telegram account and does not ask customers to provide session files or login codes.
6. Cookies and browser data
Strictly necessary cookies may be used for sessions, CSRF protection, security and preserving explicitly selected interface state. On your first visit, the site may use your browser language. Your saved language choice takes priority; a language-specific URL opens that language. The locale in the URL is authoritative for public localized pages.
Blocking essential cookies may prevent login or protected account actions from working.
7. Payments
Payment creation and reconciliation may involve an external payment provider. SMMESE may process a payment identifier, provider, method, invoice amount, credited amount, currency, status, timestamps and references needed for reconciliation.
Bank-card details or cryptocurrency credentials are entered on the payment provider’s interface and are governed by that provider’s own rules. SMMESE does not need a full card number or private wallet key.
8. Data recipients
Data may be shared only to the extent needed with infrastructure, email, payment or execution providers, professional advisers, or public authorities where disclosure is legally required. Third parties receive only the minimum data necessary for their role.
SMMESE does not sell customer personal data.
9. Retention
Retention depends on the data type and purpose. Active account, order, ledger and security records may be retained for the life of the account and for an additional period required for support, fraud prevention, accounting, dispute resolution or law.
Temporary sessions, recovery tokens, drafts and technical files are subject to shorter expiry periods. Backups may retain data until their normal rotation completes.
10. Security
SMMESE uses access controls, hashed credentials, CSRF protection, session restrictions, audit records, network segmentation, backups and operational monitoring. No internet service can guarantee absolute security.
Customers must protect their password, email account, device and API keys and promptly report suspected compromise.
11. Customer requests
A customer may request information about their data, correction of inaccurate account information, or deletion where retention is not required by law, security, accounting or an active contractual obligation.
A request must identify the account sufficiently. Additional verification may be required before disclosing or changing protected data.
12. Changes to this Policy
The Policy may be updated when the Service, providers, legal requirements or processing practices change. The current version and update date are published on this page.
13. Contact
Privacy and security questions can be sent through the official support channel shown in the Service. Do not include passwords, login codes, full card details or session files.
14. Related documents
Service and account rules are described in the Terms of Service. Cancellation and refund rules are described in the Cancellation and Refund Policy.