Market intelligence for Torn
Send a Xanax to to get a subscription. 1x Xanax = 7 days access.
Torn API disclosure
This follows Torn's API Terms of Service guideline format. Login keys are not saved by this form; optional saved keys are managed later from the Account page.
| Data Storage Will the data be stored for any purpose? | Data Sharing Who can access the data besides the end user? | Purpose of Use What is the stored data being used for? | Key Storage & Sharing Will the API key be stored securely and who can access it? | Key Access Level What key access level or selections are required? |
|---|---|---|---|---|
|
Temporary - less than a minute Login key data is used during sign-in and is not written to the database by this form. Persistent - until account or key deletion If you later save an api key from the account page, encrypted key data and feature data may persist until removed. |
Service owners TornTicker does not publish your private API data API requests also pass through a proxy. |
Public community tools Sign-in identity verification, calendar offset setup, private dashboards, cashflow, trades, networth, stocks, tracker refreshes, overview widgets, and non-malicious statistics. |
Not stored / Not shared The login key is only held long enough to verify identity and read calendar timing. Stored remotely securely / Used only for automation Optional Account keys are encrypted at rest with the server secret, masked in the UI, and removable/changable from the account by the user. |
Minimal / Public for login Sign-in uses your own user basic data. Calendar timing may need the user calendar selection and falls back silently if unavailable. Stored-key features vary by feature; custom keys should include only the selections you intend TornTicker to use. |