Terms of Service
In short You buy a subscription for a fixed period. For as long as it lasts you are present at every place that has been put into service, all of them at once: you hold one key, and the same link serves all of your devices. The link is issued in this bot, under «My keys», and there is a single one of it for the whole service — the service issues no separate link per place. Adding it to your app once on each device is enough: from then on the app fetches it on its own and gets the current list of places.
What we do not record Our nodes and the subscription host keep no access log. Nothing is stored about which sites and services you open, which addresses you connect to or which domains you look up. That log is switched off in the server configuration: when a node is installed, its access log and its DNS query log are explicitly disabled, and the technical error log is kept at a level that never captures destination addresses.
Seeing your device's address cannot be avoided — there is no connection without it: the node you connect through works with the address of your connection, and the node's panel counts your simultaneous connections by it. On the nodes and on the subscription host that address is not stored: the access log on the nodes is switched off, and the subscription host keeps no log of subscription requests and does not pass your address on to the service's own application — all a subscription fetch leaves behind is a timestamp, and it answers a single question: does your app fetch the subscription at all. Opening the app itself, though, is ordinary web traffic: your device's address ends up in the web server's log there, the same as on any site.
We never ask for, and never store, your name, e-mail address or phone number.
What we do count and store
Traffic volume is counted on the server. The node's control panel keeps counters for your connection on each node: how many bytes went out and came in, and when that connection was last active. That is volume and timing — not content, and not destinations. There is no traffic cap in this service; the counters exist so the servers can be operated.
The service database holds your account data:
- your Telegram account id, your @username if you have one, and the language you chose;
- your registration date, plus the fact and the version of your acceptance of these terms;
- your subscription: expiry date, state, purchased tariff;
- your payment history: amount, currency, payment method, payment state, date and the invoice id on the payment provider's side;
- your internal balance by part and the history of its changes, including corrections by support: what was changed, by which staff member and why;
- XRPL top-ups: the destination tag issued to your account, the payments received and what they were valued at in dollars;
- your link and your key: the link's secret part, the key's identifier and the list of places it is placed at, with timestamps;
- your devices added in the app: the name you gave each one, the marks of when it was created and last seen, and the mark of revocation. The device key itself is not stored — only its hash; a revoked device stays as a record carrying that mark rather than disappearing;
- device link codes — as a hash, never the code itself: a code lasts five minutes, one use or five wrong guesses, and the record of it, with the marks of when it was created and used, stays after the code has stopped working;
- a mark of when your app last fetched the subscription — with no device address;
- which promo codes you redeemed, and when;
- failed promo code attempts: how many came in a row, and until when promo code entry is closed after a run of them;
- a mark that the one-off free extension the service can grant an account on its own, without a promo code, has been used up: it is set at your first successful payment and when a promo code is redeemed — that is, also when no such days were ever given to you;
- if you arrived through an invite — who invited you; referral credits — with the date they become available, and a cancellation mark if one was cancelled;
- a mark that you blocked the bot, and since when — so that we do not write to you while messages are not getting through;
- a mark that you opted out of reminders, and since when;
- a journal of the reminders sent: which one, when, and whether it was delivered;
- marks of which service messages have already been sent to you — so that the same one is not sent twice.
Payment itself happens on the payment provider's side (Telegram Stars or a crypto payment service). Card and wallet details never reach us: we receive only the amount, the method, the payment state and the invoice id.
Topping up the balance over XRPL The internal balance can be topped up by a direct payment on the XRP Ledger. Your account is issued a permanent destination tag — that is what identifies a payment as yours. The receiving account is configured to refuse a payment without the tag: the network rejects such a transfer, the amount itself stays in your account, and only the network's fee for the rejected attempt is kept. Forgetting the tag therefore cannot lose the transfer — but neither does it credit anything, and the payment has to be sent again with the tag. An accepted asset may have a minimum top-up. Where one is set it is shown next to that asset on the top-up screen — and where no minimum is shown beside an asset, none applies to it. A transfer below a stated minimum is neither credited to your balance nor returned: it stays with the service. The reason is that reviewing and returning an amount comparable to the network's own fee costs more than the amount itself. You are told immediately when a transfer came in below the minimum, and such an amount does not accumulate towards the next one.
What arrives at or above the minimum is valued in dollars at the ledger's own rate at the moment of receipt and credited to the internal balance; if it cannot be valued automatically, an operator reviews it and you are told so.
This method differs from the others in one way: a payment on the ledger is public. Its amount, the sender's address and the destination tag are visible to anyone — a property of the XRP Ledger itself, not of this service, and not something we can change. If that openness does not suit you, choose another payment method.
What is blocked The BitTorrent protocol is blocked on our servers — torrent clients will not work. The same routing policy on the node also closes domains from the advertising, malware, phishing and browser cryptominer lists. Neither is a fault in the service or in your connection: everything else keeps going as usual.
Devices Your tariff sets the number of simultaneous connections, not the number of keys. You hold one key, issued once: the same link works on all of your devices, and no separate key for a second device is needed — the service does not issue one at all.
The simultaneous-connection limit is counted at each place separately: the node's panel has no single counter across all places at once. Connections beyond the limit at a given place do not go through even though the link is correct — disconnect where you are not using it right now and try again.
The places you connect through There are several places, and you are present at all of the ones that have been put into service. No single server is picked for you, and you are never moved from one server to another: your list of places follows from the rule «the subscription is active and the place is in service», and the service brings the actual state into line with that rule on its own.
The list therefore changes without your involvement. The list of places updates in your app, not in the bot: the app re-reads your link from time to time and fetches the list anew. We put a new place into service and it appears for you by itself. A place stops answering, or is taken out of service, and it drops out of the list just as much on its own, while the rest keep working. Your subscription period does not change, and nothing has to be paid.
The bot shows the same list under «My keys» for reference: a look at where we are. The place you connect through is picked in the app, not in the bot.
The bot sends no separate notification about any of this — your app gets the new list by itself.
The link, and resetting it There is one link and it is permanent. The parameters of the places do change — the address, the port, the TLS fingerprint profile we change when the previous one stops getting through — but that is no reason to fetch the link again: your app receives the new parameters through that same link by itself, at its next subscription update.
«My keys» carries a «Reset link» button, for the case where your link reached somebody else or a device was lost. The consequences of a reset are these: the old link stops working at once, and the new one has to be added again on every one of your devices. Until you have done that, the devices already connected keep working with what they had already received, but they will get no new list of places.
Subscription period and renewal There is no auto-renewal. We do not store payment instruments and we never charge you on our own. Every renewal is a separate purchase that you make in the bot.
The bot may remind you that your subscription is ending: Your subscription expires in N day(s). Renew it to keep your access.
When the period you paid for runs out, the subscription moves to the «expired» state and your right to connect ends. Go by the date in the main menu's header.
From that moment your link hands out no places, and your app, once it has updated the subscription, clears our servers away on its own. That happens in the app, and at the moment it next fetches the subscription — not in the very second the period ended.
Removing your client from the nodes is a separate procedure, and it does not happen in the same minute the period ends: the service removes it with a delay, so that renewing a day or two late costs one action rather than reconfiguring every one of your devices. That is a technical delay, not free extra time: using the service without a valid subscription is not permitted by these terms, access may stop at any moment once the period is over, and the delay must not be relied on.
Your key is not reissued, and the link stays as it was. If you subscribe again, places come back through that same link — there is no need to fetch it anew.
If you renew before your current period ends, the new period is added to the time you have left — paid days are never forfeited.
Reminders The bot may send notifications and reminders — for example, if your subscription has ended, an invoice was left unpaid or a subscription was never taken.
To stop these reminders, tap «Stop reminders» in any of them. The opt-out switches off only those: messages about payments, open invoices and the end date of your current subscription keep coming. You can turn reminders back on with the «Turn reminders back on» button in the opt-out message.
Promo codes A promo code adds days to your subscription — not money, and not a discount. You can enter a code in the bot.
- The same promo code can be used only once per account.
- Every promo code has a cap on total activations; once the cap is reached, the code stops working.
- A promo code may have an expiry date, after which it is no longer accepted.
- A promo code may carry a condition — a subscription to the channels it names. If you unsubscribe, the bot warns you and gives you time to come back; if the condition is still unmet after that, the granted days are taken back and the code can never be redeemed again.
Promo days are added to your current subscription period.
Invites and the internal balance If you invite other users, you earn cashback on your internal balance from their payments. The cashback rate depends on how many of the users you invited hold an active subscription right now; the bot shows your current rate and your invite link under «Referrals».
Cashback is earned on the part of a purchase paid with money: by card, in crypto, with Telegram Stars or from your top-ups. It is not earned on the part paid with cashback or bonuses.
Cashback does not become available at once. It is first “in progress”: for as many days as the subscription the invited user bought, plus one day; for long subscriptions the wait is capped. The bot shows the amount in progress and the exact date it becomes available in the “Balance” section. If the purchase it was earned on is refunded during that time, the cashback in progress is cancelled. Cashback that has already become available stays yours.
A user who arrives through an invite gets a discount on their first purchase. That discount applies once, and only to the first purchase.
What the balance is made of Your internal balance has three parts: “Top-ups” — money you sent yourself; “Cashback” — referral earnings that have become available; “Bonuses” — credits from the service. The bot shows each part separately.
The balance can be spent on a subscription inside the service, in full or in part. Bonuses are spent first, then cashback, then top-ups. You can top the balance up yourself by a payment on the XRP Ledger — the “Balance” section in the bot.
Balance corrections by support Support can credit money to any part of your balance or take money from it by hand — for example, to correct a credit made by mistake. If that part does not hold enough and a subscription was paid with it, the shortfall is taken as days of that subscription: whole days only, and only from a subscription paid with that part of the balance. Whatever cannot be recovered that way is not demanded from you. Support can also cancel cashback that is still “in progress”; cashback that has become available is not cancelled.
The bot sends you a message about every such correction: what was credited or taken and from which part, by how many days the subscription was shortened and until when it now runs. If days were taken, the message also explains why.
If a payment over the XRP Ledger reached your account under someone else's destination tag, support moves it to its owner. The amount is taken from “Top-ups”; if it has already been spent on a subscription, the shortfall is taken as days of that subscription — only the one paid with that money after it arrived. The part of a subscription paid with your own funds stays. You are sent a message about the transfer. When a payment made with money that support moved to its owner, or took back as credited by mistake, is refunded, that money is not returned.
If something does not work Check the two most common cases first:
- It stopped connecting suddenly, with nothing changed on your side — your app has most likely not updated the subscription for a long time and is holding settings that are out of date. Update the subscription in your app and try again; if that did not help, pick a neighbouring place there.
- Torrents do not work — that is intended; see «What is blocked» above.
If neither applies, write to us: the /support command, or the «Support» button in the main menu — that screen holds the answers to the most common questions, and the operator can be reached from it too. Your message reaches a person, and the reply arrives in this same chat.
About these terms These terms may change. When they do, the bot asks you to accept the new version — until then the version you accepted is the one that applies. We store the fact and the version of your acceptance.