VPN Businka Privacy Policy
Edition of 4 November 2026.
Service: VPN Businka — the website businkavpn.pro, the Telegram bot @BusinkaVPNbot, the Telegram mini app and the Businka applications for Windows, Android, iPhone, iPad and Mac (the "Service").
Administration: the owner of the VPN Businka project (the "Administration", "we").
Contact on data questions: email businka.support@gmail.com, the bot @BusinkaVPNbot, the Support section of the app.
In short
We keep no logs of your traffic: which sites you open and what you send is unknown to the application, and nothing of it is written down on our nodes. We store only what is needed to grant access and accept payment: a device identifier, your plan and its term, payment records, and — if you contacted support — the text of your request. We do not ask for your email at payment.
1. General provisions
1.1. This Policy describes what information the Administration receives when you use the Service, why it is needed, how long it is kept, who it is shared with and when, and how it is protected.
1.2. By using the Service — installing the app, starting the bot, registering, paying for a plan or receiving access — you agree to this Policy. If you do not agree, stop using the Service.
1.3. The Policy is written from what the program actually does: next to the statements is the code file where it can be seen. The rules of using the Service are in the Terms of Service.
2. What stays on your device and never leaves it
| What | Where |
|---|---|
| App settings, the selected node, the mode | a local settings file |
| The list of nodes with credentials | encrypted on your device (servers.bin, protected by Windows) |
| The application log | local; never sent anywhere |
Passwords for the local core login are stored encrypted and are never written to the log (src-tauri/src/settings.rs).
3. What data we collect, and why
Device identifier. On first launch the application creates a random number of the form HWID-XXXXXXXXXXXXXXXX (src-tauri/src/control.rs, ensure_hwid). It is not derived from your computer's characteristics and is not linked to your name — it is simply a random number used to tell one device from another when granting access.
Account and subscription. Email (if you provided one), plan, expiry date, number of devices, country as chosen by you at payment — the users table in the panel (admin-panel/server/db.mjs).
Buyer identifier at payment. We do not ask for an email at payment: you choose a plan and pay right away. The payment system requires a persistent buyer identifier in the form of an email address in every transaction, and we fill it in ourselves:
- if your account already has your email — that email;
- if you pay from Telegram — your numeric Telegram ID as
<number>@telegram.org; - otherwise — a persistent buyer number as
<16 digits>@mail.ru. It is derived from your account's internal number, cannot be turned back into it and is used for nothing but payments. The number you sign in to the account with is never passed on.
The identifier is the same in all your payments: the payment system and we use it to find a payment if you contact support. It is never used for mailings or advertising.
Payment records. Payment number, plan, term, amount, payment method, status and the transaction number in the payment system. Card numbers and bank details never reach us: they are entered on the payment system's page.
Installs. Operating system, application version, install date, the channel you came from — the installs table. This lets us know which versions are still in use.
Support requests. The subject and text of your message and the support replies — the tickets and ticket_messages tables. Text is limited to 4000 characters, the subject to 60. Letters sent to the support email are kept in the support mailbox.
If you use our Telegram bot. Your Telegram ID, username, name and language code — the tg_users table. The length of each field is capped (32, 64, 128 and 16 characters respectively) so that nothing superfluous enters the database.
Purposes of processing — only these:
- running the Service: granting access under your plan, tracking the term and device count;
- accepting payment and making refunds;
- contacting you: support replies, notices about payment and subscription expiry;
- keeping the network running and fixing errors.
We do not ask for passport data, documents, photos or anything beyond what is listed.
4. What we do NOT collect
- Browsing history. The addresses of the sites you open through the tunnel are not recorded anywhere — neither in the application nor on the nodes.
- Traffic content. It is encrypted and inaccessible to us.
- Your real network address, beyond what the node itself sees at the moment of connection; it does not enter the database.
- Device characteristics — the identifier is random, not computed from hardware.
5. What is collected on the nodes
Every 10 seconds each node reports its own state: CPU and memory load, traffic volume in total for the node, the number of simultaneous connections, a health flag. These figures describe the node, not people: they cannot tell you who did what.
The records are aggregated by minute and kept for seven days, after which they are deleted automatically (ubratStarieZamery, admin-panel/server/db.mjs). Node state changes (went down — came back up) are kept longer: there are few of them, and they are needed to analyse outages.
The nodes themselves are set up to leave no traces on disk: system logs are kept in memory, the swap file is disabled, and anything accumulated before that is deleted (deploy/provision-ramonly.sh).
6. The public network status page
The network status page shows only countries, the number of nodes in each and the time of changes. Node addresses, hosting provider names, the list of protocols, the number of people and the load are not shown — anonymisation is done on the server side (publichnoeSostoyanieSeti, admin-panel/server/db.mjs).
7. Who the data is shared with
Data is not shared with third parties except where the service cannot work without it or the law requires it:
- the payment system — when you pay. Currently this is Platega (payment through the Russian Faster Payments System, SBP — by QR code or by a link from your banking app — and in cryptocurrency); if you chose another connected payment service on the payment page, that service. It receives the amount, the order number, the purchase description, the buyer identifier in the form of an email address (section 3) and the internal account number. We neither see nor store card numbers;
- Telegram — if you use our bot yourself, your messages pass through it under Telegram's rules;
- when the law requires it — only within what we physically store (section 15);
- with your consent — if you yourself asked for the data to be passed on.
We do not sell data, do not pass it to advertising networks and do not use third-party analytics that track people.
Commitment for a VPN service (Apple guideline 5.4). Data that passes through our VPN service or arises in providing it is not sold, not used for any purpose other than operating the service itself, and not disclosed to third parties — not for payment, not for free, not in anonymised form. This covers the content of your traffic, the addresses you visit, and the time and volume of connections.
The transfers named above do not contradict this: the payment system receives payment data, not data about your traffic, and only when you pay; Telegram carries what you yourself wrote to the bot. Neither of them has any access to data of the VPN service.
The commitment is not a promise about the future: the nodes are built so that the listed data simply does not exist — exactly what is not written to disk is listed in sections 4 and 5.
8. How long it is kept
| What | Retention |
|---|---|
| Node measurements | 7 days, then deleted automatically |
| Account and subscription | while you use the service |
| Buyer identifier and payment records | while the account exists; deleted with it unless the law requires keeping them |
| Support requests | as long as needed to resolve your issue |
| Local settings and log | on your device, until you delete them |
9. How we protect data
9.1. Connections to the website and the payment page go over HTTPS only. The node list on the device is encrypted, and passwords are never written to the log. The control panel is not reachable from the internet: only the Administration enters it, through a secure connection to the server and with a password.
9.2. We take reasonable protective measures, but sending data over the internet always carries risk, and nobody can promise absolute security.
10. Your rights
You can ask to see what is stored about you, to correct it or to delete it. Write to businka.support@gmail.com or to the bot @BusinkaVPNbot. Deleting the account ends subscription access.
The application also works without an account: nothing needs to be set up in the free mode.
11. The legal basis for all this
| What we process | Legal basis |
|---|---|
| Device identifier, plan and term | performance of the contract with you: access cannot be granted without it |
| Buyer identifier and payment records | performance of the contract and the payment system's requirements for settlement |
| Support requests | performance of the contract: a request cannot be resolved without its text |
| Node measurements (load, availability) | our legitimate interest in keeping the network working; the measurements contain no personal data |
| The website visit counter | our legitimate interest in knowing which pages are needed; the counter sets no cookies and collects no device fingerprint (website-kit/counter.js) |
We do not ask for consent where we do without it: there are no advertising or tracking tools on the website or in the application, so there is nothing to consent to.
12. Where the data physically goes
Our nodes and control server are in the Netherlands (Amsterdam), that is, inside the European Economic Area — no extra safeguards are required for such a transfer.
Data leaves the area in two cases, and both depend on you:
- Telegram — if you write to our bot yourself. Messages travel under Telegram's rules, and its infrastructure is located outside the EEA.
- the payment system — when you pay, to the extent stated in section 7.
If we place a node in a country outside the EEA, you will see it in the node list before connecting: the node's country is something you choose yourself.
13. Withdrawing consent
Where we act on your consent (for example, you enabled the optional sending of crash reports), you can withdraw your consent at any time with a switch in the application settings. Withdrawal does not undo what was lawfully done before it.
You can delete your account and everything attached to it by contacting support.
14. We make no automated decisions about you
Neither the application nor the panel makes automated decisions about people: there is no profiling, no reliability scoring, no automated refusal of service. The node is chosen either by a person or by a speed measurement — and that concerns the node, not the person.
15. Transparency report
How many times government bodies have asked us to hand over information about the people using the service, and what we handed over:
| Period | Requests | What was handed over |
|---|---|---|
| from the start of the project to 27 August 2026 | 0 | — |
Zero here means exactly what it says: no requests have been received. If any appear, a row will be added to the table and the earlier rows will stay — we will not rewrite the history of this table.
What we can physically hand over. Only what we store, and we store little: a device identifier, plan and term, the buyer identifier and payment records, support requests (sections 3 and 8). There are no traffic logs — handing over something that does not exist is impossible under any demand.
What is missing here. We have no warrant canary — a signed notice, refreshed on a schedule, saying that no orders have been received. Keeping one makes sense only when someone refreshes it without fail: a canary that was forgotten frightens people more than no canary at all. Until such a routine exists, we say so plainly rather than imitate one.
16. Liability
16.1. You understand that sending data over the internet carries risk (section 9).
16.2. The Administration is not liable for loss, theft or disclosure of data caused by third parties or by the user — for example, if you gave someone else access to your device, your subscription link or your Telegram account.
16.3. Nothing in this section limits the rights you have under the law.
17. Complaints
If you believe we have handled your data wrongly, write to us at businka.support@gmail.com — we will answer and fix the error. If the answer does not satisfy you, you have the right to lodge a complaint with the data protection supervisory authority of the country where you live or work.
18. Changes to this Policy
18.1. The Administration may change this Policy. The current edition is always published at businkavpn.pro/privacy.html, and its date is shown at the top.
18.2. We mark significant changes with a new date and show them in the application. Continuing to use the Service after a change means you accept the new edition. Earlier editions remain in the project's change history.
19. Contact
Questions about data, requests to see, correct or delete it:
- email: businka.support@gmail.com;
- Telegram bot: @BusinkaVPNbot — each request gets a number and the answer arrives there;
- the Support section of the Businka application.
There has been no independent audit. This describes what the code does on the date of the edition. We have not undergone an external review, and until one happens the words "no-logs" remain our words rather than a verified fact.