Privacy

1. Cortex asks for no key and no account

No API key. No account. No sign-in. No email. Reading the sale ledger and running the companion script require nothing from you, on desktop or in Torn PDA. Neither has a field that takes a credential.

One unlisted page, the preview of a parked account tool, accepts a Torn key from people given access to it. It is not part of the public product, and its key handling is described where the key is entered.

2. Torn’s API disclosure table for the Cortex key

Torn asks every tool that uses API keys to state five things. Readers give Cortex no key, so each answer below is about the one key Cortex runs on: the owner’s own, which the price service uses to collect sales.

Data storage

Persistent, kept indefinitely. Sale records and item details are stored in the Cortex database. Nothing about a reader is kept beyond Cloudflare’s seven-day request logs and the reader’s own browser.

Data sharing

General public. Sale rows are published on this site and through the price service.

Purpose of use

A public community tool: price history and AAVs for ranked-war gear.

Key storage and sharing

One key, the owner’s own, stored remotely as a Cloudflare Worker secret. Only the price service uses it, and it is shared with nobody.

Key access level

Public. Every selection the price service calls works with Torn’s lowest access level.

3. Cortex holds public Torn records

3.1 Completed auction sales

The sale ledger is built from completed ranked-war auction sales that Torn publishes through its official API. Each sale is one row: the item, rarity, perks and rolls, quality, damage, accuracy, armor, bid count, price and time of sale. Where Torn supplied one, it also carries the copy id of that one item.

Each row carries the buyer’s and seller’s player names and player ids, exactly as Torn reported them. The ledger shows both names, each linking to that player’s Torn profile.

Those are Torn character names: the handle chosen in the game and the number Torn assigned to it. They are not real names, and nothing in this database can connect one to a person outside Torn. Every field came from Torn's public API, and stays in Torn's own sale records whether this site exists or not.

If you have bought or sold ranked-war gear at auction, some of these rows describe your trades. Searching a copy id lists every recorded sale of that one item, so its resale history is visible. Sale rows are not tied to a Cortex account, because there are none, and they do not record who looked them up.

3.2 The trader list

The ledger’s search box reads a list of every seller and buyer in those sales: player id, the name on their latest sale, and how many sales they made and bought. The price service rebuilds it from the sale rows once it is a day old and keeps it in Cloudflare KV. It adds nothing the sale rows do not already show.

3.3 Daily player and faction snapshots (stopped)

From late July 2026, Cortex copied two daily files that Torn gives any API key. The player file listed every active player by player id, with their character name and profile details. The faction file listed every faction with its member list of player ids. Cortex also recorded each faction’s ranked-war results.

Collection stopped on 25 October 2026. That day the copies in the Cortex database were deleted, and the raw files in Cloudflare R2 storage were deleted too.

Cloudflare keeps 30 days of database history for recovery, so the deleted rows can still be restored from it until about 24 November 2026. After that they are gone, and nothing else holds them.

3.4 Item details looked up by copy id

When the companion script sends a copy id the database has not seen, the id joins a queue. The price service then asks Torn for that item’s details with the Cortex key, four at a time, every two minutes. It stores the copy id, item, quality, rarity, perks and when it was first asked about, and not who asked.

3.5 The value each new sale was up against

From 26 October 2026, when a sale arrives, the price service first records the AAV it had published for that item, perk, rarity and roll, then stores the sale. The record holds the sale id, item, perks, rarity, quality, price and time, and the published value and ranges. It names no buyer or seller. Its purpose is the public track record described in the data policy.

3.6 Stored in your browser

This site stores one thing: your light or dark theme, under cortex_theme, once you choose one. The ledger keeps its filters in the page address rather than in storage. Opening the unlisted preview with its passphrase also stores cortex_preview_access.

The companion script stores, on your device:

• item and perk names, refreshed weekly
• a copy of the completed sales it has fetched, including each sale’s buyer and seller by name and player id, up to 72 items, each dropped after 21 days
• its settings, such as panel position, theme and which pages it runs on

The settings sit in your userscript manager’s storage, and the sales copy in an IndexedDB database named cortex_trade on torn.com. When either is unavailable, the script falls back to the other or to torn.com’s local storage.

4. Every record comes from Torn’s official API

Torn’s official API supplies the auction sales and the item details. Nothing is scraped from Torn’s website, and a field the API did not return is shown as missing rather than estimated.

Neither the site nor the companion script contacts Torn on your behalf, and neither carries a key that could. The price service does that with the Cortex key. The companion script reads only the Torn page you already have open.

5. What leaves your browser

Using the ledger sends the price service the filters you set: items, perks, rolls, price and quality ranges, and anything typed into the search box. That can be a player name, a player id or a copy id.

The page address holds the same filters, so a copied link shares them. Cloudflare keeps a log of each request to the price service, with its full address and the IP it came from, for seven days.

Nothing else identifies you: no key and no account. The price service is read-only. It answers this site and the companion script, refuses requests from other websites and from programs that name themselves as bots, and limits how many requests one address can make each minute.

It needs no key, so what this site shows, including the sale rows in section 3.1, can still be read by anyone who opens it.

The companion script sends the price service the items, perks, rolls, rarity and quality of the gear on your screen, plus the copy ids Torn shows for it. A copy id names an item, never a person. It sends no bid, no asking price, no name and no key.

It reads only the tab you are viewing, only while that tab is visible, and makes no requests to Torn. A copy id the database has not seen is looked up later, as section 3.4 describes.

The /price command in Discord sends the item, perk, roll, rarity and quality you typed. Section 7 lists what Discord adds to that, and what Cortex keeps of it, which is nothing.

6. Cookies

This site’s pages and the companion script set no cookies.

Cloudflare may set a cookie of its own when its bot check challenges a visitor. That belongs to Cloudflare’s infrastructure, and Cortex neither reads nor stores it.

7. Third-party services

Two, and each one’s role is limited to what is described here.

Cloudflare

Hosts this site and the price service, and stores the databases, caches and logs behind them.

As the host it sees what any host sees: your IP address, your browser user agent and the addresses you request. It keeps the price service’s request logs for seven days, and its bot check may set its own cookie.

Discord

Carries the /price command for anyone who uses the Cortex app in Discord, and shows the reply.

When you use /price, Discord sends the price service the command, the options you typed, your Discord user id and the server or chat you used it in. Cortex uses the user id to limit lookups per minute and keeps none of it.

There is no analytics service, no tracking pixel, no advertising network, and no font loaded from another host.

8. How long records are kept

Sale rows, item details and the value recorded for each new sale are kept indefinitely, with no automatic deletion. Torn’s own auction history does not reach far back, so expiring them on a timer would remove the reason for holding them.

The daily player and faction snapshots were deleted on 25 October 2026. Cloudflare’s 30-day database history, described in section 3.3, holds them until about 24 November 2026.

The trader list is replaced once it is a day old. Cached summaries and AAVs in Cloudflare KV expire within seven days. Cloudflare deletes the price service’s request logs after seven days.

In your browser, data stays until you clear it. The one exception is the companion script’s sales copy, which drops an item after 21 days.

9. Corrections and removal

The answer differs by what is being asked about.

Auction sale rows

A completed sale cannot be un-published. Editing a character name out of the database would not hold: the price service reads that same sale back from Torn whenever it fills a gap or re-checks an item, and its write puts the name back.

Cortex therefore does not offer to remove a name from a sale row. The row lasts as long as Torn publishes the sale.

A row that is wrong

This can be fixed. If a price, a name or a date does not match a sale you were part of, report it and it will be checked against Torn’s record.

Daily player and faction snapshots

These were all deleted on 25 October 2026, so no row remains to remove one player from. Section 3.3 gives the date their recovery history expires.

Your own browser

Clearing this site’s storage removes what it holds. In the companion script, Settings has a Clear cached sales button. Uninstalling the script and clearing torn.com’s site data removes the rest.

10. Security

The Cortex key is held as a Cloudflare Worker secret, outside the code and the database. It is sent only to api.torn.com, over HTTPS, and the price service removes it from any error text before a response leaves.

The price service’s diagnostic routes answer only a token the owner holds.

This site and the price service are served over HTTPS only, and the site tells browsers to keep using HTTPS for two years after a visit. Readers hold no credential with Cortex, so there is none of yours to protect.

No storage or transmission method is safe against every attack.

11. Age

Cortex is a tool for people already playing Torn and is not directed at children. It has no accounts, no sign-up and no contact details to give, so it gathers nothing from a visitor of any age. The player records it holds come from Torn's public API, not from the people reading the site.

12. Changes to this policy

The date at the top of this page is the date it last changed. When what Cortex does with data changes, this page changes in the same release. There is no mailing list, so that date is the record of a change.

13. Contact

Questions, a correction, or a request about anything on this page: message Shield [3516052] in Torn. It is the same profile as the Contact link at the foot of every page.

If a statement here does not match what the code does, report it as a bug.

For where the numbers come from and what they cannot tell you, see the data policy.