Agreement
By registering a Torn API key through a KAL bot, website, userscript, or API, you agree to this policy and confirm that you are authorized to provide that key.
Your API key remains confidential. It is not displayed to other users, included in public responses, sold, or transferred to another operator. The public information and derived records produced with it may be shared as described in the applicable table below.
Policy changes
Clarifications that do not expand key access, data sharing, or purpose may take effect when published. KAL will announce material changes to all affected users through its available Torn, Discord , website, or userscript channels. A material expansion will receive a new acceptance revision and affected keys will not be used under the expanded terms until the account accepts it or seven days have passed since the change was announced.
Account Verification
| Data Storage | Data Sharing | Purpose of Use | Key Storage & Sharing | Key Access Level |
|---|---|---|---|---|
| Persistent - until account deletion. | Nobody. | The API key is used to verify the identity/fac/job of the user. | Stored / Used only for automation. | Public Only (/key/info only). |
Public-pool API usage
All eligible keys are automatically opted in to KAL’s public-selection key pool and used to source the data that KAL tools rely upon. You may opt out of the pool by enabling that preference on the website’s account page, although doing so may result in reduced functionality or restricted access to tools, commands, pages, or KAL API endpoints that require additional Torn API calls.
| Data Storage | Data Sharing | Purpose of Use | Key Storage & Sharing | Key Access Level |
|---|---|---|---|---|
| Persistent - forever. | Public Torn data may be shown to the general public, authorized users, customers, or relevant faction members, depending on the tool. | Keys are used to gather the public data required to power various current and future KAL tools. The scope of the tools may include optimisation; data analysis; public community tools; competitive advantage; personal gain; public amusement. | Stored / Used only for automation. | Public Only. |
Public endpoints and selections
All Torn API endpoints/selections that KAL’s public-pool currently makes calls to are listed below. New public endpoints/selections may be freely added when features are added or changed, and this list will be automatically kept up to date
I am currently working on adding significantly more detail about which features call these selections and what they are used for, after which i’ll pinging everyone with an announcement and asking for feedback if there’s anything else people would like in my api policy, because it seems abuse is somewhat rampant out there.
Your keys are not, and will never be, used by KAL for a mug-bot.
| Endpoint | Selections |
|---|---|
/company | employees, profile, snapshot |
/faction | basic, members, snapshot |
/key | info |
/market | auctionhouse |
/torn | hof, itemdetails |
/user | discord, job, personalstats, profile, snapshot |
Future features
Non-public and faction selections are not covered by this public-pool agreement. If a future service needs selections such as attacks, logs, reports, faction-private data, or other non-public information, it will present a supplemental table describing the exact selections, purpose, storage, retention, and audience. The key will not be used for that feature until the owner explicitly opts in.
Removing a key and requesting deletion
- You can use the key-management control provided by the bot, website, or script where available.
- You can also pause or delete the key in Torn API settings to prevent further successful calls.
- Or you can contact Kalends [2032147] to request removal of a stored key or associated account data.
This policy supplements the Terms of Service. All API use remains subject to Torn’s API documentation and Terms of Service guidelines.
Contact
Questions, removal requests, or concerns about API use should be sent to Kalends [2032147].