# Privacy Policy for BotHost
**Effective date:** August 23, 2026
**Last updated:** August 23, 2026
BotHost (package name `com.bat.bothost`) is an Android application provided by Thegsmwork ("we," "us," or "our"). BotHost lets users import, manage, and run their own Python-based bots directly on their Android device.
This Privacy Policy explains what information is handled when you use BotHost, where that information is stored, when third parties may receive information, and the choices available to you.
## 1. Summary
- BotHost does not require you to create an account.
- Your bot code, bot tokens, environment files, databases, and other bot workspace files are stored locally in the app's private storage on your device.
- We do not operate a server that receives or stores your bot files, bot tokens, bot messages, or runtime logs.
- BotHost uses the Google Mobile Ads SDK. Google may automatically collect and share certain device, advertising, interaction, diagnostic, and network information as described below.
- A bot you choose to run may independently connect to Telegram, package repositories, APIs, websites, or other third-party services. Those connections are determined by your code and configuration, not by us.
## 2. Information Handled by BotHost
### 2.1 Files and content you provide
BotHost may process files that you select through Android's system file picker, including:
- `bot.py` and other bot source files;
- `requirements.txt`;
- `.env` files, which may contain bot tokens, API keys, or other secrets;
- configuration files, databases, media, logs, and other files used or created by your bot; and
- files or folders that you choose to import or export.
These files are copied to and processed within BotHost's private app storage. We do not upload them to a developer-operated server. BotHost accesses only the files or folders you explicitly select through Android's system picker or files created inside the app's own storage.
### 2.2 Locally generated app data
BotHost stores information locally to provide its features, including:
- bot profile names and locally generated profile identifiers;
- bot creation and update timestamps;
- selected bot and app settings;
- installation state for optional components such as FFmpeg;
- deployment and runtime status; and
- recent deployment and bot output logs.
Runtime logs may contain any information printed by your bot or its dependencies. This could include usernames, chat identifiers, message content, API responses, file paths, tokens, or other sensitive information if your bot prints them. Avoid printing secrets to logs. Logs remain on the device unless you copy, export, share, delete, clear, or otherwise disclose them.
### 2.3 Network and download information
BotHost requires internet access for functions such as:
- downloading and verifying the local Python runtime;
- resolving and downloading Python packages listed in `requirements.txt`;
- downloading optional app components through Google Play Feature Delivery;
- loading advertisements; and
- allowing the bot code you start to communicate with services chosen by you.
When a connection is made, the receiving service normally receives technical information such as your IP address, request time, and information required to complete the request. Python package repositories and any service contacted by your bot process information under their own terms and privacy policies.
### 2.4 Advertising data processed by Google
BotHost integrates the Google Mobile Ads SDK to display advertisements. According to Google's current SDK disclosure, the SDK may automatically collect and share:
- your IP address, which may be used to estimate general location;
- user product interactions, such as app launches, taps, and ad interactions;
- diagnostic and performance information, such as app launch time, hang rate, and energy usage; and
- device or account identifiers, which may include the Android advertising ID, app set ID, and other applicable identifiers.
Google uses this information for purposes such as advertising, analytics, ad measurement, security, and fraud prevention. Data collected by the Google Mobile Ads SDK is encrypted in transit using TLS according to Google.
For more information, see:
- [Google Privacy Policy](https://policies.google.com/privacy)
- [How Google uses information from sites or apps that use its services](https://policies.google.com/technologies/partner-sites)
- [Google advertising technologies](https://policies.google.com/technologies/ads)
## 3. How Information Is Used
Information handled by BotHost is used to:
- import, organize, edit, run, stop, and export your bots;
- install and maintain the local Python environment and bot dependencies;
- display local deployment progress, errors, and runtime logs;
- remember local app state and settings;
- deliver optional components such as FFmpeg;
- display and measure advertisements;
- maintain security, prevent abuse, and diagnose technical problems; and
- comply with applicable legal obligations.
## 4. When Information May Be Shared
We do not upload or sell your bot code, bot tokens, environment files, databases, messages, or runtime logs.
Information may nevertheless be received or processed by third parties in the following circumstances:
### 4.1 Google services
Google Mobile Ads and Google Play services may process information for advertising, analytics, fraud prevention, security, app delivery, and optional feature delivery. Their handling of information is governed by Google's policies and your available Google or Android privacy settings.
### 4.2 Services contacted by your bot
Your bot code may connect to Telegram, APIs, websites, databases, cloud platforms, or other services. BotHost does not determine what information your bot sends. You are responsible for reviewing your code, protecting credentials, obtaining any required permissions or consent, and complying with the privacy policies and terms of the services you use.
### 4.3 Python package repositories
If you provide a `requirements.txt` file, package names and related network requests may be sent to Python package repositories to resolve and download dependencies. Those repositories process requests under their own policies.
### 4.4 User-directed disclosure
Information leaves the app when you deliberately export files, share a file, copy logs to the clipboard, or otherwise send information to another app, person, or service.
### 4.5 Legal and safety reasons
We may disclose information if required by applicable law or a valid legal process, or when reasonably necessary to protect users, the public, our rights, or the security of the app. Because we do not operate a server for bot content, we generally do not possess your locally stored bot files or logs.
## 5. Android Permissions
BotHost requests only permissions required for its current features:
- **Internet and network state:** to download runtime components and dependencies, load ads, and allow user-run bots to access the internet.
- **Notifications:** to show the persistent notification associated with a bot or deployment running in the foreground.
- **Foreground service and foreground service special use:** to continue a user-started bot or deployment while the app is not visible and to provide visible stop or cancel controls.
BotHost uses Android's system file picker rather than requesting broad access to all files on your device.
## 6. Data Storage, Retention, and Deletion
Bot files, bot profiles, settings, component state, and recent logs are stored locally in BotHost's private app storage. They remain there until you delete the relevant bot or files, clear app data, or uninstall BotHost. Exported copies remain wherever you chose to save or share them and must be deleted separately.
You can delete locally stored information by:
- deleting a bot or individual files within BotHost;
- clearing BotHost's storage in Android system settings; or
- uninstalling BotHost.
We cannot remotely delete local data because it is not stored on our servers. Google and other third parties determine their own retention periods. Requests regarding information processed by a third party should be directed to that party.
## 7. Security
BotHost uses Android private app storage for bot workspaces, restricts file operations to a bot's workspace, uses HTTPS for configured runtime downloads, verifies downloaded runtime files using checksums, and does not permit cleartext network traffic at the Android app level.
No method of storage or transmission is completely secure. The security of bot tokens, credentials, messages, and external connections also depends on the bot code, dependencies, services, and configuration you choose. Keep your device secure, review third-party code before running it, avoid exposing secrets in logs, and protect any exported files.
## 8. Advertising and Privacy Choices
Depending on your location and the applicable configuration, advertising may be personalized, non-personalized, or limited. Where required, consent or privacy choices may be presented through an applicable consent management mechanism.
You may also be able to reset or delete your Android advertising ID, manage ad personalization, and review other privacy settings through your Android device or Google account settings. Availability varies by device, Android version, account, and region.
In some jurisdictions, advertising-related processing may be legally treated as the sharing or sale of personal information. We do not sell your bot files or personal content. You may contact us using the address below regarding applicable privacy rights or choices.
## 9. International Data Processing
Google and other third-party services contacted by the app or your bot may process information in countries other than the country where you live. Their privacy policies explain the safeguards and legal bases they apply to international transfers.
## 10. Children's Privacy
BotHost is a developer utility and is not directed to children under 13 or the minimum age required by local law to consent to data processing. We do not knowingly collect children's personal information on a developer-operated server. Parents or guardians who believe a child has provided information in connection with BotHost may contact us.
## 11. Your Rights
Depending on where you live, you may have rights concerning personal information, such as rights to access, correct, delete, restrict, object to, or obtain a copy of certain information, and to withdraw consent where processing is based on consent.
Most information directly handled by BotHost is stored only on your device and can be accessed or deleted using the app or Android settings. To make a request concerning information that we may control, contact us. We may need sufficient information to understand and lawfully respond to the request.
## 12. Third-Party Services and User-Provided Code
This Privacy Policy covers BotHost itself. It does not govern:
- a bot that you create, import, or run;
- third-party Python packages;
- Telegram or another messaging service;
- websites, APIs, databases, or platforms contacted by your bot;
- Google services; or
- another app or destination to which you export or share information.
Review the privacy practices of those third parties before using them.
## 13. Changes to This Privacy Policy
We may update this Privacy Policy when the app, third-party SDKs, legal requirements, or our practices change. The revised policy will display a new "Last updated" date. Material changes may also be communicated through the app or its store listing where appropriate.
## 14. Contact Us
For questions, privacy requests, or concerns about this Privacy Policy, contact:
**Thegsmwork**
**Email:** thegsmwork@gmail.com