VAITGS BACS Build: Terms of Service and Acceptable Use Policy

Operated by VAITGS BACS · Contact: build@bacs.pro

Confirmed. Version 2026-10-26.

These terms apply to every bot build, hosting plan and change request sold by VELETOP LTD, a company registered in England and Wales (Company Number 17542468), registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom, trading as VAITGS BACS ("we", "us"). You are the "Client". Contact: build@bacs.pro · bacs.pro · Telegram @bacsbuildbot.

Issuer details for invoices:
VELETOP LTD (trading as VAITGS BACS)
Registered in England and Wales · Company Number: 17542468
Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ

Availability. We sell to customers worldwide.

By accepting these terms in @bacsbuildbot, on bacs.pro or by paying an invoice, you agree to them. If you buy for a company, you confirm you may bind it.

Part A. Terms of Service

1. What we sell

1.1 Builds: Starter (from a template), Custom and Pro. Scope, price and turnaround are fixed in your quote.

1.2 Hosting: Host Basic and Host Plus, monthly, for bots we built.

1.3 Host-only: we host a bot whose code you supply, after a review (Part C).

1.4 Change requests: one small change each, priced in the price list.

1.5 Prices are on bacs.pro/build and in the bot. Your invoice shows the amount charged.

2. Your bot, your token, your code

2.1 You create the bot in your own @BotFather account and send us its token only after payment. You stay the owner of the bot at all times. You can revoke our access at any time with /revoke in @BotFather; we are then no longer able to run the bot and hosting ends without a refund for the current period.

2.2 After full payment you receive a licence to use, change and run the code we wrote for your bot, for any lawful purpose. We keep the ownership of our generic template core, libraries and tools, and may reuse them.

2.3 On request (and when hosting ends) we send you a code export of your bot.

3. Orders, payment and turnaround

3.1 Starter, hosting, Host-only setup and change requests are paid in full upfront. Custom and Pro: 50% to start, 50% before go-live.

3.2 Payment methods: Telegram Stars (in the bot), card (via our payment provider) or USDC on Solana (on bacs.pro/pay). Stars prices are set separately and may differ from card prices because of Telegram's fees.

3.3 Turnaround counts from the later of full payment and a complete brief (and, for Host-only, a passed review).

3.4 Revisions included: Starter 1, Custom 2, Pro 3. Extra work is a change request or a new quote.

4. Hosting

4.1 Hosting runs on our servers in the EU (Hetzner, Germany/Finland), 24/7 with monitoring, automatic restarts and daily backups (7 daily + 4 weekly kept). We aim for high availability but do not guarantee uninterrupted service; Telegram or provider outages are outside our control.

4.2 Each client bot runs isolated with resource limits (memory, CPU, processes, disk, network). A bot that keeps exceeding its limits gets a warning and an upgrade offer; we may throttle or pause it to protect other clients.

4.3 Hosting renews every 30 days. Stars subscriptions renew automatically until you cancel in Telegram. Card and USDC hosting is invoiced 5 days before renewal. 7 days overdue: the bot is paused. 30 days overdue: we send the code and data export and delete the hosting slot.

5. Refunds and right of withdrawal

5.1 If we cannot deliver the agreed scope, you get a full refund of what you paid for that scope.

5.2 After delivery we fix defects and use the included revisions instead of refunding.

5.3 Consumers have a 14-day right of withdrawal. Because our services start right away at your request, you agree when ordering that we start immediately and you acknowledge that you lose the right of withdrawal once the service has been fully performed; if you withdraw earlier, you pay for the part already done.

5.4 No refund is due when we suspend or end a service because of a breach of Part B or C (see 9.2).

6. Support

Email build@bacs.pro or /support in @bacsbuildbot. Host Basic: reply within 48 h; Host Plus: within 24 h (business days). We do not provide phone support, legal, tax or financial advice.

7. Your responsibilities

7.1 You warrant that your bot, its content and its use are lawful in every country where you offer it, comply with Telegram's Terms of Service, Bot Developer Terms and payment rules, and do not infringe anyone's rights.

7.2 You are the controller of your bot's users' data and responsible for your own privacy notice, consents and any licences your activity needs (for example for financial services or gambling).

7.3 You keep your BotFather account, API keys and third-party accounts secure and pay their costs (e.g. AI or data APIs).

8. Logging and records

We log for each hosted bot: start/stop, resource use, errors, network connections (destination, time, bytes), and admin actions. We do not log message content unless your bot does so itself or we need it to investigate a fault or abuse report. Logs are kept for 90 days; payment and invoice records for as long as tax law requires.

9. Suspension and termination

9.1 You can cancel hosting at any time; it ends at the end of the paid period.

9.2 We may suspend a bot immediately and without notice, and terminate without refund, if we reasonably believe it breaches Part B or C, is the subject of a credible abuse report, or puts our servers, other clients or Telegram's platform at risk. Where the law and the situation allow, we tell you why and give you a chance to respond.

9.3 We may end hosting for any other reason with 30 days' notice and a pro-rata refund of prepaid periods.

9.4 On termination we send a code and data export on request within 30 days, then delete your data and the encrypted bot token (backups roll off within 35 days).

10. Cooperation with Telegram and authorities

We report illegal content we become aware of and cooperate with Telegram and with competent authorities on valid legal requests. We may preserve relevant logs and data for that purpose. We may notify Telegram of bots that breach its terms.

11. Liability

11.1 Our total liability under these terms is limited to the fees you paid us in the 12 months before the event.

11.2 We are not liable for indirect or consequential loss, lost profits, lost data that you could have exported, or trading or investment losses.

11.3 Nothing in these terms limits liability for intent, gross negligence, death or personal injury, or rights that consumers have under mandatory law.

12. Indemnity

You indemnify us against claims, fines and reasonable costs (including legal costs) arising from your bot's content, your instructions, your code (Host-only) or your breach of Parts B or C. This does not apply to the extent the claim is caused by our own breach.

13. Data protection (GDPR processor terms)

13.1 For your bot's users' personal data we act as your processor under Art. 28 GDPR; you are the controller. We process it only to build, host, monitor, back up and support your bot, on your documented instructions (these terms and your brief).

13.2 Our staff and tools with access are bound to confidentiality. Security: isolated runtime per bot, encrypted tokens, access only for the service, encrypted transport, backups in the EU.

13.3 Sub-processors: Hetzner Online GmbH (hosting, EU) and Telegram (the platform you chose). We tell you before adding a new sub-processor; you may object and end the service.

13.4 We help you answer data-subject requests and notify you without undue delay (within 72 h) of a personal-data breach affecting your bot. On termination we return or delete the data (9.4). We give you the information needed to show compliance and allow reasonable audits by document review.

13.5 Data stays in the EU. If you ask us to connect services outside the EU, you are responsible for the transfer basis for those services.

13.6 For your own data as our customer (name, email, Telegram id, country, VAT id, payments) we are the controller; see the privacy notice on bacs.pro.

14. Changes, law and disputes

14.1 We may update these terms; changes apply to new orders and to the next hosting period after 30 days' notice.

14.2 The laws of England and Wales apply. Consumers keep the protection of the mandatory law of their country of residence. The courts of England and Wales have jurisdiction for business clients; consumers may sue in their home courts.

14.3 If a clause is invalid, the rest stays in force.

Part B. Acceptable Use Policy (all packages)

We do not build, host or support, and you must not use our services for:

Scams, fraud, phishing, fake support or account-recovery bots.
Wallet drainers, seed-phrase or private-key collection, fake wallet connect, approval/permit phishing.
Custody of users' keys or funds by the bot, or signing wallet transactions on users' behalf, unless agreed in writing in a Pro quote with a security design we approve (never for Host-only).
Spam, unsolicited messages, mass DMs or mass adds, messaging people who did not start the bot or join the group, scraping members, contact lists or phone numbers.
Fake engagement: view, member, subscriber, vote, reaction or review bots, account farming, userbots that automate personal accounts.
Pump-and-dump, market manipulation, paid shilling without disclosure, fake airdrops or giveaways, Ponzi or pyramid schemes, unlicensed investment or financial services.
Malware, ransomware, stealers, keyloggers, RATs, botnets, cryptojacking, DDoS, exploit or cracking tools.
CSAM or any sexual content involving minors (reported to authorities at once), non-consensual intimate content, adult content.
Gambling, betting, lotteries or casinos without a valid licence for every market served.
Sanctions evasion, terrorist content, money laundering, illegal goods (drugs, weapons, counterfeits).
Impersonation of people, brands or Telegram; doxxing, stalking, harassment, hate speech.
Copyright infringement and piracy.
Anything that breaches Telegram's Terms of Service, Bot Developer Terms or payment rules (including selling digital goods in the bot with anything other than Telegram Stars).
Anything illegal in the United Kingdom, the EU or the countries where the bot is offered.

We screen every brief automatically and may refuse any order without giving reasons. A refused order is not charged or is refunded in full.

Part C. Host-only (we run your code): extra rules

Review before go-live. Your code does not run on our servers until it passes our review. The setup fee pays for the review and is not refunded if the code fails because of a breach of Part B.
Automated pre-deploy scan of the full repository and its dependencies, on every deploy, for: secrets and keys committed in code; known malware, stealer and drainer patterns and known-bad packages; mass messaging (loops over user lists calling send methods, joining or adding members); outbound wallet signing or key handling (seed phrases, private keys, signing libraries, transaction building); obfuscated or packed code, download-and-execute, shell execution; network calls to undeclared domains.
Manual review of the scan results, the bot's flows and its declared purpose by us. We may ask questions or for changes. Obfuscated or unreadable code is refused.
Right to review at any time. You grant us the right to inspect the code, configuration, dependencies, logs and runtime behaviour of the hosted bot at any time, including after go-live and after each update.
Updates go through the same scan; only reviewed commits/versions are deployed. You do not get shell access.
Network egress limits. The bot can only reach api.telegram.org and the domains you declared and we approved. Everything else is blocked and logged. No inbound ports unless agreed (webhooks via our proxy).
Runtime limits. Rootless container per bot with memory, CPU, process, disk and bandwidth caps; no access to other clients, our own products or the host.
No wallets. Host-only bots may not hold, request or use private keys or seed phrases and may not sign blockchain transactions.
Logging as in section 8, plus a record of every deployed version (commit hash and scan result).
Violations: immediate suspension without refund, termination, preservation of evidence and, where required or appropriate, reports to Telegram and the authorities. You indemnify us under section 12.
You warrant that you own or may license the code and that it contains no hidden functions.

Home · Privacy · build@bacs.pro