Privacy Policy
Effective Date: October 2026 • Last Reviewed: October 25, 2026
1. Commitment to Developer Privacy
At Bot Hoster (bots.godhosting.online), we respect the privacy, security, and intellectual property of developers who trust our cloud infrastructure to host their automated bots and workers.
This Privacy Policy explains what information we collect, how your bot tokens and environment variables are safeguarded, how container isolation protects your files, and your rights regarding data deletion.
2. Information We Collect
We only collect the minimal information necessary to deliver, authenticate, and maintain your 24/7 bot services:
- Account Information: When you register an account, we store your chosen name, email address, and a securely hashed password generated using cryptographic bcrypt salting. We never store plain text passwords.
- Bot Configuration Metadata: Your bot display name, runtime environment (Python 3.12, Node.js 22, Bash), main entry script, and startup commands.
- Ephemeral Telemetry & Logs: Live CPU/RAM utilization and standard output (
stdout/stderr) generated by your bot process. Logs stream through memory via Server-Sent Events (SSE) and are retained only within your container instance.
3. Zero-Retention Policy on Bot Tokens & Secrets
Bot Hoster operates under a strict zero-retention policy for API secrets. Tokens detected during code analysis (including TELEGRAM_BOT_TOKEN, API_ID, API_HASH, and DISCORD_TOKEN) are written directly into your isolated bot sandbox's private .env file.
We never inspect, harvest, log, or sell bot tokens. Tokens are utilized solely by your bot's container runtime to communicate with upstream provider APIs (Telegram Bot API, Discord Gateway, WhatsApp WebSocket).
4. Docker Sandbox Isolation & 100% Code Ownership
You retain 100% intellectual property ownership of all source code, databases, media files, and scripts deployed to Bot Hoster.
Every bot process executes inside an unprivileged Linux container sandbox isolated by Linux namespaces (pid, net, ipc, mnt, uts) and cgroups v2. No other user or bot on the system has filesystem access or network namespace visibility into your container.
5. Data Erasure & Permanent Wiping
You have absolute control over your data. When you click "Permanently Delete Bot" in the Bot Console or Danger Zone:
- The running Docker container is stopped (
SIGKILL) and pruned immediately. - All bot source files, configuration files, and virtual volumes are recursively deleted from disk.
- All metadata records associated with the bot are wiped from the database.
- This action is irreversible and leaves zero residual traces on our storage drives.
6. Security & Network Encryption
All incoming web traffic to Bot Hoster is encrypted in transit using industry-standard Transport Layer Security (TLS 1.3 / HTTPS) with 256-bit encryption. Our cloud perimeter is defended by AWS security groups, hardware firewalls, and active rate limiting to mitigate denial-of-service (DDoS) and brute-force intrusion attacks.
7. Contact Our Privacy Team
If you have questions, inquiries, or requests regarding this Privacy Policy or your stored bot data, please contact our support desk: