Trust & ToS Posture

How Arbiter sources data, what runs on your machine, what reaches our server, and where we draw hard lines. This is our operating posture and a set of commitments — not legal advice.

The one line that matters

Arbiter does not automate the game. No botting, no auto-trading, no clicking, no input injection, no reading game memory. Every trade is read by you and executed by you, by hand. The tool does math; you make the decision and do the trade. This is the operative line under Grinding Gear Games' Terms of Service.

What the tool actually does

1. Your reads → your verdict

The client reads the trade in front of you — optical character recognition of your own screen, the same pixels you are already looking at — and sends that read to our server, which returns the verdict against the current market.

We do not hook the game, inspect its process, or read its memory.

If you switch on map auto-tracking for the Loot Valuer, the client follows the game's plain-text event log (Client.txt) to notice when you return to your hideout. That file is read-only, only when you enable the feature, and nothing from it leaves your machine.

2. The discovery radar

A broad market scan (movers, spreads, cross-hub mispricing, underprice watch) surfaced in the dashboard. Discovery points you at where to look; the verdict on your own read decides whether to act.

What leaves your machine — the complete list

The client sends the following to the server to run the service:

• your Arbiter sign-in token;
• the market read in front of you (want / have / ratio, plus the order book if it is on screen) — sent to compute your verdict;
• your recent OCR observations (market, rate, time) — sent so the server can build your Flip Calculator from your own browsing and check the best currency to sell in.

What stays on your machine, always

• Images. Inventory screenshots for the Loot Valuer are processed locally; no capture, crop, or screenshot is ever uploaded.
• Your config, file paths, worth-it bar, and game-log path.
• Loot corrections and saved maps.

What we do — and don't do — with your data

Your reads and observations are stored under your account and used to run and improve Arbiter, including its market data and features. We don't sell them or share your individual reads with third parties.

Where market data comes from

Public market-data APIs, polled within their published rate limits. We do not scrape the website, drive the trade UI, or circumvent any access control or rate limit. Where official API programs exist we pursue sanctioned access and operate within its granted terms.

Freshness tiers

Free sees the previous snapshot; Pro sees the latest. The age shown on any snapshot is its real age.

Privacy

• Account data is limited to what authentication and billing require. Payment is handled by Stripe; card details never touch our servers.
• Your reads and observations live under your account; ask us and we delete your account and its data.
• Any future telemetry is privacy-respecting and aggregate; it never includes your reads or observations.

What we will not do

• Automate, bot, or inject input into the game.
• Read game memory or hook its process. (The one game file we read is the plain-text Client.txt event log, read-only, for the map auto-tracking you switch on.)
• Upload images from your machine.
• Sell, share, or pool your reads or observations.
• Scrape around, or circumvent, any source's access controls or rate limits.
• Dress stale data as fresh.

Questions

Ask in the Discord or write to the contact address on the front page.