Legal, Privacy & Compliance

1. Acceptable Use & Monitoring Targets

You may only create custom monitors for websites, servers, or endpoints that you own or have explicit authorization to monitor. Probing unauthorized systems, conducting denial-of-service (DoS) simulations, or triggering excessive high-frequency polling is strictly prohibited.

2. Bot-Hosting OAuth & API Monitoring

Connecting your Bot-Hosting account grants read-only permission to query your server deployment metadata and current state. You agree to only connect accounts and claim server ports that you rightfully own or co-manage. API monitors evaluate states via the official Bot-Hosting API and are subject to upstream API availability and rate limits.

3. User Submissions, Requests, Appeals & Confidentiality Disclaimer

When submitting outage reports, service feedback, API access requests, ban or report appeals, or monitor and webhook limit increase requests, you agree to provide truthful, accurate, and relevant information. Submitting false reports, fraudulent requests, spamming forms, or attempting to mislead staff regarding service status or ownership will result in immediate denial, revocation of privileges, or a permanent ban.

Submission at Your Own Risk: All user submissions, including outage reports, feedback, API access applications, appeal statements, and limit increase justifications, are stored on our systems, are accessible to and reviewed by staff members and administrators, and are submitted strictly at your own risk. Do NOT include confidential, sensitive, proprietary, or personally identifiable information (such as passwords, secret tokens, private API keys, payment details, credentials, or personal contact info) in any report, appeal, API application, or limit increase request. We accept no responsibility or liability for any sensitive or confidential information you choose to disclose.

4. Service Availability, Detection & “As-Is” Disclaimer

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, UPTIME DATA, INCIDENT REPORTS, WEBHOOK NOTIFICATIONS, AND API TELEMETRY ARE DELIVERED ON A STRICTLY “AS-IS” AND “AS-AVAILABLE” BASIS, WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR ACCURACY. WHILE WE STRIVE FOR CONTINUOUS ACCURACY, WE DO NOT GUARANTEE 100% UNINTERRUPTED DELIVERY OF EXTERNAL WEBHOOK ALERTS OR REAL-TIME METRICS. WE MAY PROVIDE ROOT-CAUSE SUMMARIES OR POST-INCIDENT REPORTS AT OUR DISCRETION; THEY ARE INFORMATIONAL ONLY, MAY BE REVISED AS INFORMATION BECOMES AVAILABLE, AND ARE NOT GUARANTEED FOR EVERY INTERRUPTION, DEGRADATION, OR INCIDENT.

• Alert & Webhook Delivery: Status alerts (webhooks, Discord notifications, etc.) may not always be sent for every status change. Not all status types will trigger webhook notifications. Delivery depends on upstream service availability, configured thresholds, and internal rate limits.
• Detection Limitations: Various automated methods are used to detect service status, including HTTP probes, TCP checks, ICMP pings, API polling, and component condition evaluations. However, partial degradation, intermittent issues, and some failure modes may not be automatically detected by these checks. Automated monitoring is not a substitute for comprehensive observability.
• User Report-Based Status: Users may submit reports on any monitor to indicate perceived issues. All submitted reports are subject to a character limit, are made at your own risk, and are visible to all staff members at any time, do not include confidential, sensitive, or personally identifiable information in your reports. When a monitor accumulates a sufficient number of reports exceeding its per-monitor threshold, an alert is automatically sent to staff so they can investigate and verify the reported issue. Report-driven status changes reflect community perception and may not always correspond to a verified technical state. Status reverts automatically when reports expire or fall below the threshold. ALL REPORTS ARE CLEARED WEEKLY AUTOMATICALLY, admins can clear reports for any or all monitors at their discretion.

5. Account Termination & Access Revocation

We reserve the right to restrict, suspend, or terminate access for any account that violates these terms, bypasses security controls, abuses API limits, or disrupts system operations.

6. Subdomain Separation & Independent Operation

The Bot-Hosting Status Tracker is hosted on a separate subdomain (status.bot-hosting.net) and operates as an independent application from the main Bot-Hosting platform (bot-hosting.net). These are distinct web applications with separate servers, databases, and authentication systems. Login sessions, cookie preferences, browser storage, and any other client-side state do not carry over between the two domains. Logging in on bot-hosting.net does not log you in on status.bot-hosting.net, and vice versa. Similarly, cookie consent choices (e.g. accepting or rejecting analytics cookies) made on one domain have no effect on the other you must set your preferences independently on each site.

7. Limitation of Liability & Exclusion of Damages

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL BOT-HOSTING STATUS, ITS OWNERS, OPERATORS, STAFF, CONTRIBUTORS, OR INFRASTRUCTURE PROVIDERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING, WITHOUT LIMITATION, LOSS OF PROFITS, LOST REVENUE, LOST BUSINESS OPPORTUNITIES, CUSTOMER CHURN, DATA CORRUPTION OR LOSS, SERVICE INTERRUPTION, OR DOWNTIME COSTS, ARISING OUT OF OR IN CONNECTION WITH YOUR ACCESS TO, USE OF, OR INABILITY TO USE THIS SERVICE, AUTOMATED STATUS CHECKS, WEBHOOK NOTIFICATIONS, LATENCY HISTORY, OR TELEMETRY DATA, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THIS STATUS TRACKER IS A FREE OPERATIONAL VISIBILITY TOOL AND PROVIDES NO FINANCIAL GUARANTEE.

8. Modifications to Service & Terms

We reserve the right to modify, enhance, suspend, or discontinue any feature of the service, or update these terms at any time without prior individual notice. Any updates become effective immediately upon posting to this page.

User Responsibility to Stay Informed: It is your sole responsibility to periodically review this page and stay up to date with the latest Terms of Service and Privacy Policy. By continuing to access or use the service after any revised terms are published, you acknowledge and agree to be bound by the updated terms. If you do not agree to the modified terms, you must discontinue your use of the service.

Information We Collect

• Discord Identity: When you log in via Discord OAuth, we receive your Discord User ID, username, display name, avatar hash, and an authentication access token. This token is used strictly to verify identity and periodically refresh active avatars.
• Bot-Hosting OAuth & Deployments: If you connect your Bot-Hosting account, we store your OAuth access/refresh tokens, deployment IDs, server names, assigned nodes, ports, and runtime status. Tokens are used exclusively to fetch deployment lists and power API-based state monitoring.
• Monitors & Webhooks: URLs, ports, check intervals, monitor types (HTTP probe or API cloud check), and webhook destinations (Discord, Slack, Generic) that you explicitly configure.
• Reports, Requests & Appeals: Issue descriptions, affected service selections, application statements, appeal explanations, and limit increase justifications submitted through our forms (all submissions are voluntary, accessible to staff, made at your own risk, and must never include confidential credentials or secrets).
• Security & Session Data: Encrypted session identifiers, IP addresses (used strictly for rate limiting and fraud prevention), and browser user-agent headers.
• Aggregate Analytics: Anonymous traffic and performance metrics measured via Google Analytics. In jurisdictions with opt-in cookie regulations (such as the EU, UK, Switzerland, Canada, Brazil, and other covered regions), visitors receive an interactive choice prompt on their first visit to select either Essential Cookies or All Cookies. In other regions, cookies are enabled by default.

How We Use Your Data & Third-Party Infrastructure

• Executing periodic health checks on configured services, querying Bot-Hosting API states, and recording latency history.
• Dispatching incident alerts to your configured webhook endpoints.
• Bot-Hosting API: Communicating with api.bot-hosting.net to synchronize deployment states and verify server ownership.
• Cloudflare Reverse Proxy & CDN: Routing traffic through Cloudflare for global edge caching, SSL/TLS encryption, and DDoS mitigation.
• Google Analytics: Measuring aggregate visitor counts and popular monitor views.
• Authenticating administrative operations with 2FA and new device verification checks.
• Mitigating DDoS attacks, abusive scraping, and unauthorized automated API queries.

No Data Selling or Advertising Networks

We never sell, rent, or monetize your personal data. We do not use third-party advertising networks. Data is only communicated to trusted infrastructure providers (e.g. Discord for webhooks/OAuth, Bot-Hosting for deployment telemetry, Cloudflare for network defense, Google Analytics for consented aggregate metrics) as necessary to operate the service.

Legal Basis for Processing

• Consent: When you voluntarily log in via Discord, connect your Bot-Hosting account, configure custom monitors, or subscribe to alerts.
• Legitimate Interests: To maintain system security, detect fraudulent new devices, enforce API rate limits, and provide accurate uptime tracking.
• Legal Obligation: If required to comply with binding law enforcement requests under applicable law.

Your Statutory Rights

• Right of Access & Portability: You may request a copy of all monitor configurations, deployment caches, logs, and account metadata stored on your profile.
• Right to Rectification: Changing your avatar or username on Discord automatically synchronizes with our platform during session refresh.
• Right to Erasure (“Right to be Forgotten”): You can delete any monitor or webhook directly in your dashboard at any time. Disconnecting your Bot-Hosting account instantly deletes stored OAuth tokens and purges deployment cache data. For complete account purging or GDPR data inquiries, contact support at [email protected] or on the Discord support server.
• Right to Object & Restrict Processing: You may disconnect Bot-Hosting OAuth or revoke OAuth permissions from your Discord User Settings at any time to immediately halt data synchronization.

API Key Security & Secret Protection

You are solely responsible for keeping your API key confidential. Do not embed keys in public GitHub repositories or client-side JavaScript. Compromised keys should be revoked and regenerated immediately.

Prohibited Uses & Clone Restrictions

• No Commercial Resale: The API is provided for personal and non-commercial integrations unless explicit written permission is granted by Bot-Hosting management.
• No Status Clone Pages: You are not permitted to scrape or reproduce public replica sites whose primary purpose is to mirror this status tracker.
• No Confusing Public Discord Bots: You may not build public bots that clone or impersonate our official Bot-Hosting status bot.
• Rate Limit Compliance: Automated pollers must respect response headers and rate limits. Intentionally spamming endpoints will result in automatic key revocation.

Essential First-Party Cookies

We use strictly functional, first-party session cookies (such as connect.sid and device_id). These cookies maintain your authenticated session state and verify trusted administrative devices.

Cloudflare Security & DDoS Protection

Our traffic is routed through Cloudflare to protect the status platform against DDoS attacks, automated exploit attempts, and malicious bots. Cloudflare may set technical security cookies (such as __cf_bm or cf_clearance) to distinguish human visitors from automated botnets. These cookies do not store personally identifiable profiles.

Google Analytics & Cookie Preferences

We use Google Analytics to measure aggregate visitor trends and see which monitor pages are actively viewed so we can keep the infrastructure fast and reliable.

In countries and regions requiring prior opt-in consent (including the EU, UK, Switzerland, Canada, Brazil, and other applicable regions), first-time visitors receive a consent banner with the choice to allow All Cookies or keep Essential Only. In other locations, cookies are enabled by default. You can open the Cookie Preferences prompt in the site footer at any time to review or change your selection.

Subdomain Isolation & Cross-Domain Boundaries

The Status Tracker (status.bot-hosting.net) and the main Bot-Hosting platform (bot-hosting.net) are entirely separate applications. Because they run on different subdomains with independent backend servers:

• Sessions & Login: Authentication on one domain does not grant access on the other. You must log in separately on each site. Discord OAuth sessions are maintained independently.
• Cookies & Preferences: Cookies set by status.bot-hosting.net (including session cookies, consent selections, and analytics opt-in/out choices) are scoped to that subdomain and are not readable by bot-hosting.net, and vice versa.
• Cookie Consent: Accepting or declining analytics cookies on the main Bot-Hosting site has no effect on the Status Tracker. You must independently configure your cookie preferences on each domain via the respective footer prompts.
• Local Storage & Browser Data: Theme preferences, cached UI states, and any localStorage data are sandboxed per origin by the browser and do not synchronize between the two sites.

Device Verification & MFA

To protect staff accounts, logins from unrecognized devices require multi-factor verification (if setup). Device fingerprinting hashes are stored in encrypted format and used exclusively for security audits.