API Key Usage Policy¶

This page outlines the API Key Usage Policy for Stig’s services. Please ensure you read and understand this policy fully. If you have any questions or require clarification, you are encouraged to ask.

The Agreement¶

By registering your API Key with any of my bots, you agree to the terms set out in this policy.

Your API Key will remain confidential and will not be shared or made visible to anyone other than Stig.

Policy Changes¶

Any changes to this policy will be announced with at least 7 days’ notice. All affected users will be notified via Discord, or Torn if Discord contact is not possible.

If you do not remove your Torn API Key from my services before the end of the notice period, this will be taken as your acceptance of the updated terms, regardless of whether you actively use the service during that time.

Alerts regarding changes to this policy will be delivered via Discord direct messages, and an announcement will also be made in Stig's Dev Server

Data Storage & API Key Usage¶

Data Overview

Below is a summary of how your Torn API Key and associated data is stored, shared, and used across Stig's services.

Data Storage	Data Sharing	Purpose of Use	Key Storage & Sharing	Key Access Level
Persistent - forever	Nobody can directly access the data.	Optimization Data Analysis Public amusement Public community tools Competitive advantage Personal gain All of the above apply essentially as the data is required to power all of the bots which all do different things.	Your API Key will be stored & utilised by the bot in which it was paired, as well as in Stig-Cache. Find bot specific usage below.	Public Only

Data Refresh

Although data is stored indefinitely, it is updated every 12 hours to ensure freshness and accuracy.

Indirect Data Visibility

While nobody has direct access to the stored data, it can be indirectly viewed through the outputs of bots and public-facing tools that rely on this data.

API Key Security

Only public API selections are required. Your key is securely stored and utilised within both the bot it was paired with and Stig-Cache for performance optimisation.

Public Services¶

Applies to Public Order Services

This includes services such as Bounty Hunters Guild, Nebula Services Team, and WarMart. These services require access to private selections such as log and reports in order to fulfil orders and validate contributions.

Data Storage	Data Sharing	Purpose of Use	Key Storage & Sharing	Key Access Level
Persistent - forever	Nobody can directly access the data. Order progress submitted by sellers will be visible to authorised service staff via receipts.	Data is stored to power the service, validate your contributions to orders, and retain records for statistics and receipts.	Your API Key will be stored & utilised by the bot in which it was paired, as well as in Stig-Cache.	All Access Levels Your log will be accessed with specific categories to avoid exposure to unnecessary data. Your reports will be used to submit stat spies for applicable orders.

Private Services - Part 1¶

Applies to Private Faction-Based Modules

This includes the following modules: Chaining, Market, Membership, Monitoring, Ranked War, Stock Market, Territory & Verification

These modules rely on data linked to your Torn account and may surface it to your faction depending on leadership configuration.

Data Storage	Data Sharing	Purpose of Use	Key Storage & Sharing	Key Access Level
Data is Semi-Persistent – stored for up to 6 months.	Your faction and its members may access data derived from your API Key. This is based on faction leader preferences.	Data is stored to power the modules your faction has enabled, for live/historical statistics and real-time alerts.	Your API Key will be stored & utilised by the bot in which it was paired, as well as in Stig-Cache.	Public Access Only Selections correspond to module functions (e.g. monitoring tracks targets, membership uses personal stats).

Private Services - Part 2¶

Applies to Additional Private Modules

This includes the following modules: Armoury, Crime, Faction Banking, Mercenary, Retaliations & Reviving

These modules primarily use your faction API key provided by leadership, and may track individual contributions where relevant.

Data Storage	Data Sharing	Purpose of Use	Key Storage & Sharing	Key Access Level
Data is Semi-Persistent – stored for up to 6 months.	Your faction and its members may access provided data, depending on faction preferences.	Data is stored to power the modules your faction has enabled, display live/historical statistics, and trigger alerts.	Keys added via `/pair` are stored & utilised by Stig-Cache. Keys added to the Faction Config are only stored in that specific bot.	Limited Access Modules use the faction API key. For the Reviver Module, your revives and/or attacks may be used to fulfil contracts.

Mug Bot¶

Applies to the Mug Bot

Data is used to optimise alerts and performance in high-frequency mugging environments.

Data Storage	Data Sharing	Purpose of Use	Key Storage & Sharing	Key Access Level
Data is stored locally for up to 2 hours. Data is continuously refreshed by keys pooled into the module.	Your faction and members may access the resulting data, subject to faction leader configuration.	Data is stored to power faction-owned mugging modules and provide real-time alerts.	API Keys added with `/pair` are securely stored & utilised by the bot and in Stig-Cache.	Public Access Only Specifically uses Bazaar, player profile, and networth (personalstats) data.

Summary¶

The points below summarise how your Torn API Key may be used across services, depending on how it is paired and the modules enabled.

Stig-Cache usage is limited to public-only selections and does not access private data.
Keys added via Faction Config may access private faction data and be heavily utilised to power critical modules.
Private faction data is stored responsibly and deleted after approximately 6 months.
You may remove your key at any time using /unpair or by messaging Stig directly.

Consent Notice

By pairing your API key with any of my bots, you consent to the usage terms described in these sections.