Legal
Privacy policy
This page describes how this static web app handles data. There is no login and no server run by this project that stores your rig or API key. If you paste a Torn API key, requests go to Torn’s servers under their rules. Official API terms: torn.com/api.html.
Torn API disclosure (required table)
The Torn API documentation asks third-party tools to disclose storage, sharing, purpose, key handling, and key access level. The table below matches their format.
| Data storage | Data sharing | Purpose of use | Key storage & sharing | Key access level |
|---|---|---|---|---|
Only locally. The API key and a short-lived market price cache live in your browser’s localStorage until you clear site data or use Clear in the app. The rig “seed” and UI state are not uploaded by us. Loading assets/rig.json is a normal HTTP fetch of public component templates (same origin or fallback URL). |
Nobody besides you on your device. This app does not send your key or cache to our servers (we do not operate an application backend for this static page). | Public community tool: estimate rig and component cost using Torn item data and optional item market listings. | Stored locally in your browser only, not transmitted to us. Each request to Torn includes your key in the query string as Torn requires. We do not share your key with other services. | Uses a public API key you provide (custom keys work if they include the selections this app calls: Torn item info and market item listings). |
What we store locally
rig_torn_api_key_v1… your Torn API key, if you click Apply. Removed when you click Clear.rig_torn_market_cache_v1… JSON map of item IDs to cached lowest market price and timestamp (about one hour TTL). Cleared when you clear the API key from this app.
Anything else (seed in the URL as ?r=, form fields) stays in the page or address bar the usual way. Use private browsing if you do not want persistence on this device.
What we send to Torn
Only when you save a key and the app refreshes prices, the browser calls Torn API v2 over HTTPS. Endpoints used include item batch info under /torn/…/items and item market listings under /market/…/itemmarket. Each request includes your key and a static comment parameter set to CrackingRigSimulator so Torn’s logs show which application called. That matches Torn’s expectation that scripts identify themselves. Rate limits and logging apply as described in Torn’s documentation.
What we do not do
- No analytics or advertising trackers are added by this project’s source.
- No password or Torn login credentials are requested (only an optional API key).
- No warranty: this page is accurate for the shipped static files...if you host a modified copy, update this policy yourself.
Questions about Torn’s side of API use should go to Torn staff. Suspected key misuse can be reviewed in Torn’s key log as described in the Torn API docs.