Data Policy - Torn Travel Planner

Data Policy

Transparent usage of your data and API key.

Summary table

TopicDescription
Data storageUser ID including some public profile data - Persistent
Data SharingNobody
Purpose of useUsage analytics and tracking subscriptions
Key Storage & SharingNever stored on server
Key Access Level

Public: Authentication, username display, API key validation, and item prices

Minimal: Energy/Nerve bars, and travel state

1. API Key Usage

Your API key is used to access the Torn API. All calls are client-side (browser-only), except for one-time authentication.

Public Access Level

  • user/profile - Authentication & username display
  • key/info - Validates API key
  • market/itemmarket - Item prices for profit calculation

Minimal Access Level

  • user/bars - Energy/nerve tracking
  • user/travel - Travel state adjustments

Backend Authentication

API key sent once to verify identity, then discarded. Never stored on servers.

2. Data Storage

DataLocationDuration
API KeyYour browserUntil removed
Session TokenYour browserShort-lived
SettingsYour browserUntil cleared
User IDOur serverPersistent

Important: Your API key is never stored on our servers.

3. Abroad Stock Feature

API Key NOT used for abroad stock tracking

Stock data is sourced from Yata.yt and is completely isolated from user data.

  • Stock data is stored on our server and sourced from Yata.yt
  • This data is analyzed to create models for restock/decay predictions

4. Analytics

We collect anonymous usage stats:

  • User ID (session identification)
  • Basic profile info (name, level, faction, company), used to see what type of people use the site

We do not track money, inventory, or battle stats.

5. Data Sharing

No data sharing with third parties.

  • User ID used for subscription management only
  • Analytics used internally for improvements
  • No selling, trading, or transferring of data

6. Contact

Questions? Reach out:

Last updated: December 2025