Skip to content

Privacy Policy

Complete transparency about how we handle your data and API key

September 9, 2026 last updated

You can freely browse TornW3B without providing an API key, but providing your key helps improve the accuracy and reliability of data on the site and keeps your bazaar updated more frequently.

This privacy policy explains exactly how your data is used and what you can expect from this service.

The table below contains important information about how your API key and data are handled - giving you complete transparency about what to expect:

Data Storage
Data Sharing
Purpose of Use
Key Storage & Sharing
Key Access Level
Will the data be stored for any purpose?Who can access the data besides the end user?What is the stored data being used for?Will the API key be stored securely and who can access it?What key access level or specific selections are required?
Persistent - until account deletionGeneral publicPublic community toolsStored / Used only for automationLimited, Full, or Custom for bazaar scanning

What Your API Key Is Used For

Core Service (Always Active)

Bazaar Scanning: Your API key is used to periodically check your bazaar for new listings, price changes, quantity updates, and open/closed state. TornW3B also stores bazaar activity history and related metadata, including detected bazaar changes, recent bazaar-change timing, and activity level signals used to decide how frequently to scan you. This happens automatically every few minutes to keep the TornW3B database current. A Limited, Full, or Custom key with profile and bazaar permissions is required - Public and Minimal keys are not accepted because Torn's two-tier cache can serve listings up to 72 hours old on those access levels.

API Endpoint: api.torn.com/user/?selections=profile,bazaar

Optional Community Features (Opt-In Only)

Active player discovery (site master key):

TornW3B uses the site master API key to download Torn's daily public /v2/user/snapshot CSV of recently active players. That directory seeds names (and null-only faction/company) so unregistered bazaars can be covered — it does not use your personal API key and does not overwrite live status, last-seen activity, or federal-jail fields.

API Endpoint: api.torn.com/v2/user/snapshot

Unregistered Bazaar Scanning:

If enabled, your API key is used to scan bazaars of players who haven't registered with TornW3B. This helps build a more complete database of available items across the entire Torn community.

API Endpoint: api.torn.com/user/{playerId}?selections=profile,bazaar

Item Market Scanning:

If enabled, your API key helps scan item market details for regular items. This is separate from bazaar listings and is used to provide broader market pricing data for the community.

API Endpoint: api.torn.com/market/{itemId}

Ranked Weapon Scanning:

If enabled, your API key is used to fetch detailed stats about ranked weapons across all bazaars. This helps other players find weapons with specific stats they're looking for.

API Endpoint: api.torn.com/v2/torn/{uids}/itemdetails (up to 25 UIDs per call)

Faction Scanning:

If enabled, your API key is used to scan faction member lists. This helps identify active players whose bazaars need timely updates, and the member scan history is also used to infer user activity patterns that are shown in admin-only activity views and heatmaps. The site master key separately downloads Torn's daily faction directory snapshot to keep the faction pool complete.

API Endpoints:

  • api.torn.com/v2/faction/{factionID}/members?striptags=true (your key, when faction scanning is enabled)
  • api.torn.com/v2/faction/snapshot (site master key, daily directory seed)

Personal Stats:

If enabled, your API key is used to fetch your personal stats once daily. This data is collected for all active users in TornW3B's database and is used to accurately populate leaderboards and each user's personal activity history. The data is public on Torn and includes categories such as drugs used, online activity, and similar statistics.

API Endpoint: api.torn.com/v2/user/personalstats?cat=all

Display Case Scanning:

If enabled, your API key may be used to fetch public display case contents via Torn's user display selection (OpenAPI lists this as a V1 fallback selection, alongside bazaar). Display cases are public on Torn; this opt-in helps catalog collectibles across the community.

API Endpoint: api.torn.com/user/{playerId}?selections=display

Faction Hub Key Contribution (factions.weav3r.dev):

Signing in on the Factions hub may add your API key to that faction's rotation to refresh its Torn data (roster, attacks, and other faction endpoints your key already allows). Keys are never used beyond their permissions and are never sold or shown to other players. For 39th Street factions this can work before the full hub UI is unlocked; other factions will need a separate premium subscription when that product ships.

API Endpoints (examples): api.torn.com/v2/faction/... selections your key allows (such as attacks or members)

Battle Stat Estimates (opt-in / BSS):

If you enable battle-stat estimate features (when available), TornW3B may read your battle stats and attack log to improve fair-fight style estimates for you and consented observers. This only runs while the relevant opt-in is enabled.

API Endpoints:

  • api.torn.com/v2/user/battlestats
  • api.torn.com/v2/user/attacks

Eliminations (opt-in):

If you enable Eliminations scanning, your API key may be used to read public Torn elimination and elimination-team data so TornW3B can power the Eliminations board and related tooling.

API Endpoints:

  • api.torn.com/v2/torn/elimination
  • api.torn.com/v2/torn/{id}/eliminationteam

Premium Trade Tools (Paid Beta):

With an active Premium subscription and premium trade sync enabled, your API key reads Torn log entries to build cost basis (including $0 acquires), track sells/consumes, compute FIFO profit, power ledger / overflow / museum views, expand museum set exchanges, and keep receipt trade status in sync. Item-movement pulls only the log groups you enable in Settings (market & bazaar on by default; other groups opt-in). Trade economics use trade logs (category 94). Sync runs only while Premium sync is on and your subscription is active. To save calls, item-movement pulls may skip when you have been offline ~20+ minutes unless you still have an open bazaar with listings; Sync Now, first enable, and truncated catch-up always pull fully. Trade-status sync is not skipped for offline users.

API Endpoints:

  • api.torn.com/v2/user/log?log=…&comment=TornW3B (enabled item-movement log types)
  • api.torn.com/v2/user/log?cat=94&comment=TornW3B (Trades)

Premium Subscription Payments (Site Master Key)

Premium access is granted when a player sends Xanax (Torn item ID 206) to Weav3r with the exact comment W3B (case-insensitive). Quantity equals weeks of access (1 Xanax = 1 week). To detect those payments, TornW3B periodically calls Torn using the site owner's master API key (not subscriber keys) to read Weav3r's own item-receive logs (log type 4103) from a short recent window. Matching sends are stored as payment records and used to extend premium_expires_at for the sender.

API Endpoint: api.torn.com/user/?selections=log&log=4103&comment=W3B&from={unix}

Only Weav3r's receive logs are read for payment detection. Subscriber keys are not used for this purpose. Premium is currently a paid beta: bugs, inconsistencies, and feature changes should be expected.

Rate Limits & API Usage

Rate Limit: Your API key will never be used more than 10 times per minute. TornW3B uses this limit to avoid overloading your key (Torn allows up to 100 per minute).

API Identification: Calls made with your user API key include the comment "TornW3B" so you can identify them in Torn API usage logs. Premium payment polling uses comment "W3B" on the master key.

Log Access: Premium trade sync uses Torn /v2/user/log (item movement and trade categories) and only runs for subscribers who explicitly enable sync with a key that has log permission. You can limit which item-log groups are fetched in Settings.

Important Notes

  • All optional community features are disabled by default - you must explicitly enable them in your settings
  • You can enable/disable any feature at any time without affecting your core bazaar scanning
  • Limited, Full, or Custom keys with profile and bazaar permissions are required for core bazaar scanning; Public and Minimal keys cannot be used because Torn's cache can return stale listings
  • Restricted custom keys are fine for core bazaar tracking, but optional features may require additional permissions such as faction or log access
  • Premium trade tools are a paid beta - subscribe with Xanax + comment W3B, then enable sync yourself; expect bugs and changing features
  • If you later want to enable community or Premium sync with a restricted key, you'll need to create a new key with the necessary permissions

Cookies, Analytics & Consent

TornW3B shows a consent bar powered by the open-source library vanilla-cookieconsent for privacy notices and optional cookies. You can accept, reject, or customize analytics and advertising, and reopen preferences anytime via Cookie Settings in the site footer. The same bar links to this Privacy Policy and the Terms of Service; when the privacy policy version changes, the bar appears again so you can review the update.

Necessary: Session and security cookies required to stay signed in, protect the site, and remember required preferences (for example, your privacy-policy acknowledgement and theme).

Analytics: Google Analytics (measurement ID G-PF693NSPW1) loads on public pages only after you accept Analytics, under Google Consent Mode. Until then analytics storage stays denied and the gtag script is not injected. Choose Reject optional (or leave Analytics off in Cookie Settings) if you prefer not to share that data.

Advertising: TornW3B may use Google AdSense to show ads that help keep the site running. The AdSense script loads only after you accept Advertising. Reject optional or leave Advertising off in Cookie Settings to opt out.

Other: Error reporting (Sentry) and CDN/security tooling (Cloudflare) may process technical data needed to keep the service reliable. Cookie preferences are stored in a first-party consent cookie managed by vanilla-cookieconsent.

Changes to This Policy

TornW3B may update this Privacy Policy from time to time. Changes will be announced publicly on the TornW3B Discord server and Torn forum thread, and the site may prompt you to review and acknowledge the updated version before continuing to use certain features.

Privacy Policy Acceptance

To accept this update, you must review the policy on this page and scroll all the way to the bottom first.

Scroll to the bottom of this page to unlock the accept button.