Lilibtc Bot

Privacy Policy

Last updated: 2026-08-06 · Effective date: 2026-08-06

Lilibtc Bot ("we" or "the Service") is a content automation tool for Binance Square users. We handle your data under three principles: minimal collection, explicit consent, and the right to withdraw at any time.

1. What we collect

  • Telegram account identifier: your TG user_id, username, and language_code (captured automatically when you /start the bot).
  • binance_uid: the unique numeric ID of your Binance account (used to verify via Binance OpenAPI that you own this Square account).
  • agent_token: a per-user publishing credential (system-generated, used to post to Binance on your behalf).
  • Configuration and command logs: your review_mode, posting frequency, promo-slot ratio, and management commands such as /start, /set_mode, /pause.
  • Bot-generated and published post content: used for audit history, compliance traceability, and duplicate prevention.
Key clarifications: binance_uid is a public identifier (visible to anyone on your Binance Square profile) — knowing it cannot move your funds. agent_token is a publishing credential and not an API key; it can only call the posting API — it cannot trade, withdraw, or read balances.

2. What we never collect (and never ask for)

  • Wallet addresses, private keys, seed phrases
  • Exchange API keys (the Binance OpenAPI key we use is held by the operator, not submitted by users)
  • KYC information (ID cards, passports, facial photos)
  • Bank cards, credit cards, payment accounts
  • Your fund balances, positions, or trade history

3. How your data is used

  • Calls to Binance OpenAPI to publish posts on your Square account.
  • Recording your preferences (review_mode, posting frequency, promo-slot ratio).
  • Deduplication and compliance auditing of generated content.
  • Never sold as user profiles or shared with third parties for marketing.

4. How your data is stored

  • Location: the operator's VPS (Tokyo, Japan), in SQLite database files.
  • Transport encryption: all website–bot traffic over HTTPS; bot ↔ Telegram ↔ Binance also over TLS.
  • At rest: protected by VPS filesystem permissions; isolated ops accounts under least privilege.
  • Retention: data is kept while your account is active unless you request deletion; deleted within 90 days of account termination.

5. Third parties

  • Telegram Bot API: receives your commands, delivers review messages, and returns publishing results.
  • Cloudflare: this website is served through Cloudflare CDN and DDoS protection; Cloudflare may log edge access records.
  • Binance OpenAPI: used to publish on Binance Square. The OpenAPI key is held by the operator; user private keys are never touched.

Apart from these three providers, we do not sell or share your personal data with any third party.

6. Cookies and website analytics

This website uses no tracking cookies, shows no ads, and needs no cookie banner. Site analytics are aggregated via Cloudflare Web Analytics (cookie-free, no personally identifiable information recorded).

7. Your rights

  • Access / export: you may request a copy of your data at any time via bot command or email.
  • Correction: you can change review_mode, posting frequency, and other settings; binance_uid cannot be edited manually (re-linking required).
  • Deletion: email [email protected] to request deletion of all your data, or use the /delete_my_data command in the bot (if available).
  • Withdraw consent: simply stop using the bot; your data will be handled per the retention terms above.

8. Note for international users

This Service is built for Chinese-speaking Binance users. Servers are located in Tokyo, Japan, and data processing occurs mainly within the jurisdictions of mainland China, Hong Kong, and Japan. By accessing the Service from other regions, you consent to the cross-border data processing arrangements described above.

9. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be announced on the website and in the bot for at least 7 days before taking effect. Previous versions are available on request from [email protected].

10. Contact