Terms of Service - Wolf Pack Bot

Effective Date: October 24, 2025

Please read these Terms of Service ("ToS") carefully before using the Wolf Pack Bot (the "Bot"). This ToS governs your use of the Bot and its interaction with the Torn API via your Discord server.

1. Introduction

The Wolf Pack Bot is a Discord bot designed to assist Torn factions and users with management and tracking. It integrates with your Discord server and utilizes the Torn API to provide real-time information for tasks such as user verification, hospital tracking, revive list management, player time zone display, and payment/subscription tracking.

By adding the Bot to your Discord server and configuring it with Torn API keys, you, as the server administrator, agree to be bound by this ToS. Individual members who interact with features requiring a personal API key (such as verification) also agree to these terms.

2. API Key and Data Handling Overview

This Bot interacts with the Torn API using two types of keys: guild-level API keys provided by server members for general bot function, and optional user-level API keys provided by individual members for specific features. The following table outlines how data is handled.

Category	Details
Data Storage	Persistent - until account deletion: The guild's API keys, individual user API keys (for verification), Discord IDs, Torn User IDs, and configuration settings are stored on the bot's secure server. Data fetched from the API (e.g., member lists, hospital status, user profiles) is stored in a database to provide core functionality and improved performance. Data is subject to deletion upon request or removal of the bot/user.
Data Sharing	Service owners & Faction: The Bot's administrator(s) may access stored data for maintenance, support, and optimization. Faction-level data (e.g., hospital/revive lists) is displayed exclusively within your Discord server. User-specific data (like a verified status) is shared within the faction community in your server. Data is not shared with unaffiliated third parties.
Purpose of Use	Public community tools & Optimization/Maintenance: Data is used to enable the Bot's functionalities as a community tool for faction management (hospital/revive lists), user verification, and time zone coordination.
Key Storage & Sharing	Stored / Used only for automation: All API keys (guild and user) are encrypted and stored in a secure database on the bot's hosting server. They are accessed only by the Bot for automated requests to the Torn API and are not shared externally. Access is programmatically restricted, with potential access by administrators strictly for maintenance.
Key Access Level	Custom (Guild & User): The required API selections depend on the feature. See the "Specific Feature Details" section below for a full breakdown.

3. Specific Feature Details & API Requirements

The Bot's functionality is divided into several modules, or "cogs," some of which have unique API and data requirements.

User Verification (`/verify`, `/key add`)

Functionality: Allows a Discord user to link their account to their Torn account, granting them roles and access within the server. This can be done by linking on the official Torn Discord (via `/verify`) or by providing a personal API key (via `/key add`).
Key Required: Can use the Torn-Discord link OR an Individual User's API Key.
API Selections: Requires a key with `Limited Access` to the user section, specifically the `profile` and `discord` selections to confirm identity.
Data Handling: The bot securely stores the user's API key (if provided), their Discord ID, and their Torn User ID to maintain the verification link.

Hospital Tracker (`/hospitaltracker`)

Functionality: Monitors Torn faction members and specific players for hospital exit times. Sends notifications at configurable intervals before exit and can display a live-updating list.
Key Required: Uses the pool of guild-level API keys provided by server members.
API Selections: Requires keys with access to faction -> `basic`, `members` (for faction monitoring) and user -> `profile` (for individual player monitoring).
Data Handling: Stores hospital exit times, notification status, and user associations in the database.

Revive List

Functionality: Displays a live-updating list of faction members who are currently revivable.
Key Required: Uses the pool of guild-level API keys.
API Selections: Requires keys with access to faction -> `basic`, `members` to get member status.
Data Handling: Fetches data live; primarily stores message IDs for updating the embed.

Time Display (`/showtimes`)

Functionality: Displays a live-updating list of users and their local times based on their configured UTC offset.
Key Required: None. This feature relies on user-provided data, not the Torn API.
Data Handling: Stores a user's Discord ID, their chosen display name, their (optional) Torn ID and Faction Tag, and their provided UTC offset string.

Payment Tracking (`/payment status`)

Functionality: Tracks the bot's subscription status for the server, which is managed by the Bot Owner.
Key Required: Uses the **Bot Owner's** private API key. This key is *not* provided by the server or users.
API Selections: The owner's key requires user -> `log` access to scan for Donator Pack payments.
Data Handling: Stores payment and subscription expiry timestamps for each guild. This data is not shared publicly.

Note: You are responsible for generating dedicated API keys for the Bot. You should provide keys only through secure, designated channels (e.g., a direct message to the bot or a secure configuration command).

4. API Key Security and User Responsibility

You are solely responsible for the security of your API keys.
It is your responsibility to ensure that you are using the official version of the Bot invited from a trusted source.
Do not share API keys publicly. If you suspect a key has been compromised, you should immediately revoke it via the Torn API page (www.torn.com/api.html) and generate a new one.
The author of the Bot is not responsible for any loss or damage resulting from unauthorized access to your data due to a compromised API key, if such compromise is not a direct result of a security flaw within the Bot itself.

5. Disclaimer of Liability

The Wolf Pack Bot is provided "as is" and "as available" without any warranties of any kind, express or implied.
The author(s) shall not be liable for any direct, indirect, incidental, special, consequential, or exemplary damages resulting from the use or the inability to use the Bot.
While the Bot is designed to be compliant with Torn's rules and API usage guidelines, you use it at your own risk. The author is not responsible for any actions taken against you or your faction that may result from the use of this Bot.

6. Changes to Terms of Service

The author reserves the right to modify or replace this ToS at any time. If a revision is material, an attempt will be made to provide notice (e.g., through a message in your Discord server or a linked forum post). What constitutes a material change will be determined at the sole discretion of the author.

By continuing to use the Bot after those revisions become effective, you agree to be bound by the revised terms.

7. Acceptance of Terms

By adding the Bot to your server or by providing it with a personal API key, you signify your acceptance of this Terms of Service.

8. Contact

If you have any questions or concerns about this ToS or the Bot, please use the Bot's support command or contact the administrator as specified in the Bot's documentation or help command.

By providing an API key to the Wolf Pack Bot, you acknowledge that you have read, understood, and agree to this Terms of Service.