01Operator
This policy explains how personal data is processed when you use tolovgo.uz and related services (the dashboard, payment pages, the API and the Telegram bot @tolovgobot). It should be read together with the Terms of Use.
- Operator: TolovGo
- Website: tolovgo.uz
- Contact: support@tolovgo.uz
02Who this applies to
TolovGo is a payment-acceptance service for Telegram bots, websites and online stores. The policy covers three groups:
- Store owners (dashboard users);
- Payers (a store owner's customers who use the payment page);
- Visitors and enquirers (people who open the site or write to
support@tolovgo.uzor the Telegram bot).
03What data is processed
3.1. Account and sign-in (store owner)
- Name, email, phone number (if provided), login.
- Telegram ID (as the dashboard owner's identifier) and Google account identifier (when signing in with Google).
- For existing accounts, the password is stored only as a one-way hash; the plain password is not stored.
- Last sign-in time.
- The two-factor authentication (2FA) secret is stored encrypted and backup codes as a hash (additionally encrypted).
- Sign-in codes sent by email are stored as a hash for a short time.
3.2. Verification
- Phone number and the time it was verified (if verified by SMS code).
- Location: coordinates, accuracy and an "in Uzbekistan" flag, sent once from your browser with your permission in the Verification section.
- Passport identification (KYC): required to open a new checkout and to withdraw funds. Passport data (full name, passport series and number, PINFL, date of birth, phone, passport and face photos) is collected and stored encrypted only on a separate server located in Uzbekistan (id.tolovgo.uz). The main TolovGo system stores only full name, a partly hidden (masked) passport number, the application status, the application number and (if rejected) the reason for rejection. PINFL, the full passport number and photos are not transferred to the main system.
3.3. Payments and financial data
- Store data: name, Telegram bot or website address, logo, settings, API keys (encrypted), webhook secret (encrypted), allowed IP addresses.
- Orders and payments: amount, status, time, note, order number, payment method, provider transaction number.
- Payer details: Telegram ID, username, name (optional). These details are sent by the store owner when creating a payment.
- Payouts: amount, status and recipient details: a card number or a phone number (encrypted); saved cards: encrypted number, last 4 digits, card type. A code for adding a card is sent by email or Telegram.
- Ledger records (balance, movements).
- The payer's bank card: the number, expiry and SMS code are typed into the form on the payment page, but are sent directly from the browser to the payment system (Payme) and do not reach TolovGo's servers; the server uses only a verified token.
04Data sources
- You: forms, the dashboard, an email to
support@tolovgo.uzor a message to the Telegram bot. - Telegram and Google (as sign-in tools).
- The store owner (payer details sent through the API).
- Payment providers (transaction status).
- The identification service (application status, full name; while it was running).
- Your browser and device: IP address, user agent, cookies.
05Purposes
- Creating an account, signing in and security (2FA, attempt limits).
- Accepting payments, settlement, payouts, reports.
- The Verification section (phone, location, identification). Phone, location and identification data are collected so that, in cases of illegal funds or fraud, a person's identity and whereabouts can be established and, when necessary, handed to the competent authorities.
- Sending messages (codes, payment and payout notifications).
- Answering enquiries and helping users.
- Keeping security logs (only data actually recorded in the system, for example session IP address and user agent, application logs), detecting suspicious activity and keeping the service secure.
- Resolving disputes.
- Complying with legal requirements.
06Legal bases
For each purpose, the reason the data is processed:
| Purpose | Reason |
|---|---|
| Account creation, sign-in | You create an account to use the service; an account cannot be created without the data. |
| Payments, settlement, payouts | Necessary to provide the service. |
| Sending messages | Codes and notifications are needed for the service to work. |
| Enquiries and help | To answer your enquiry. |
| Security log | To protect the account and the service, and to resolve disputes. |
| Dispute resolution | As evidence in disputes about payments and the account. |
| Verification (phone, location, identification) | So that, in cases of illegal funds or fraud, a person's identity can be established and handed to the competent authorities. |
| Legal requirements | To comply with the requirements of applicable law. |
07Third parties and data sharing
| Service | Purpose | Data involved |
|---|---|---|
| Telegram | sign-in widget (telegram.org script on the sign-in page and the payment page), bot messages | Telegram ID, name and username (at sign-in); text of bot messages (payment, payout, code) |
| Google sign-in; Google Fonts | Google account identifier and email (at sign-in); when fonts load (in the dashboard and on payment pages), the browser's IP address reaches Google's servers | |
| Cloudflare | DNS; proxy for some subdomains (e.g. pay.tolovgo.uz); forwarding of emails to support@tolovgo.uz; Turnstile on the registration form (registration is currently closed) | traffic metadata; incoming emails |
| Brevo | sending email (sign-in codes, notifications) | recipient email, subject and message text |
| Eskiz | sending SMS (phone verification) | phone number and SMS text |
| Payment providers (Click, Payme, Paynet, Xazna, Uzum) | accepting the payment | amount, order number and required technical parameters. Name, email and Telegram ID are not sent to these providers. The provider itself processes card data. |
| Store owner | payment notification (callback) | order status, amount, note (signed request) |
- The main system's server is located in Germany (rented hosting). The identification service's server is located in Uzbekistan.
- Data is not sold or used for advertising. No advertising is placed on the site.
- To date, there have been no cases of disclosure of data to government authorities.
08Retention periods
Set periods:
- Session: ends after 30 minutes of inactivity.
- Confirmation codes (email, Telegram, card): up to 5 minutes, deleted after use.
- Payment link: 1 hour from creation.
- Dashboard notifications: deleted automatically after 90 days.
- Server, application, Telegram bot and payment provider (Click, Payme, Paynet, Xazna, Uzum) logs: 2 years.
Other data:
- Account data is kept while the account exists. If you signed in with Telegram: Telegram ID, name and username; if you signed in with Google: your Google email address and identifier.
- Orders, transactions, payout requests, ledger records and saved cards are kept while the account exists.
- Webhook delivery records and enquiries in the mailbox are kept while the account exists.
- Session records (IP address, user agent) are deleted by the system periodically after the session expires.
- Location data is kept while the account exists.
- Historical KYC records (full name, masked passport) are kept while the account exists.
- When a store is deleted, all of the store's data (orders and history, logo, bot username, payment system settings) is deleted. Exception: logs (including payment provider logs) are kept for 2 years (to detect cases of illegal funds). The owner's saved payout cards remain, because they belong to the profile, not the store.
09Security measures (currently in place)
- Encrypted: card numbers, 2FA secret and backup codes, API keys, webhook secret and location data. Location data is handed over only at the request of competent authorities, and in encrypted form.
- Passwords are stored only as a one-way hash; sign-in codes as a hash.
- HTTPS (HSTS), security headers and a content security policy (CSP); cookies use
secure,httponlyandSameSite=Lax. - Payouts require a second factor (Authenticator); sign-in and code attempts are rate-limited; webhooks are signed with HMAC-SHA256.
- No system is 100% secure.
10Questions and suggestions
If you have a question, a problem or a suggestion, feel free to write to support@tolovgo.uz. You can also ask there to see, correct or delete your data.
11Cookies
The site uses only cookies needed for the service to work (sign-in session, security) and convenience settings (language, theme). No analytics or advertising cookies are used. You can delete or block cookies in your browser settings; if the necessary cookies are blocked, signing in to the dashboard and paying may not work.
12Age limit
People under 18 cannot use the service.
13Changes
If the policy changes, the new version is published on this page and the date above is updated.
14Contact
Questions: support@tolovgo.uz