Last updated 18 November 2026
Privacy policy
TLI Toolkit is a free, fan-made companion app for Torchlight: Infinite, made by an independent developer. It is not affiliated with or endorsed by the developer or publisher of the game. This policy covers the desktop app, its community server (api.tlitoolkit.com) and this website (tlitoolkit.com). Questions: hello@tlitoolkit.com.
In short
- No account needed, no ads. The app sends anonymous usage statistics (Google Analytics) only if you turn them on; this website counts visits with Cloudflare’s cookieless Web Analytics, and with Google Analytics (which sets cookies) only if you accept it.
- Your sessions, prices and settings stay on your PC.
- Diagnostics and private replay sharing are on by default. Supported uncertain reads may send a game image privately, including character names or chat. Replay access expires after 14 days; scheduled cleanup removes expired copies and retries failures. Turn sharing off in Diagnostics (main menu). Private replay sharing is a separate default-on switch and can send game images showing character names or chat; see Private read replay bundles.
- Steam sign-in is optional. You can publish a saved build as a public guide with your display name, and unpublish it or delete the build or account. Moderators can hide guides or bar an account from publishing. Leaderboards are optional and show your chosen display name when enabled.
- Run sharing is on by default; turn it off in Settings → Community. Uploads are pseudonymous: tied to a random install id, not your name; linked to your account only if you link the app.
- Sync between your PCs and browsers is optional and needs no account: everything it sends is encrypted on your device first, so our server cannot read it. Farming history syncs only if you turn that on too.
- You can delete what you shared from inside the app at any time. We keep a deletion marker in the database and object storage: the keyed hash of the old install id and deletion time, with no play data. It has no scheduled expiry and blocks late uploads from that id.
What the app reads on your PC
- The game’s log file (
UE_game.log), which Torchlight: Infinite writes once you press Enable Log: maps entered, items picked up, prices you looked up in the Trade House, minigames opening. To find it, the app looks in your Steam library folders, the standalone launcher’s and TapTap’s install folders, and the running game’s folder. - Where the game window is (its position and size), so the mini window and the on-game highlights line up.
- Game-area pictures for screen reading. Auto-read is on by default for Vorax, Tartarus and TOWER, and off by default for Arcana and Void Sea. Each tool has its own toggle. It reads when Auto-read is on and the advisor is open (or the log shows that minigame), or when you press Read now (Ctrl+Alt+R). The app first requests the game window. If that stream cannot open, it automatically captures the monitor containing the game and crops each frame locally to the game area. The monitor stream can include other desktop content before cropping; only the cropped game area is passed to the reader. Text recognition runs on your PC, offline. A separate failure-frame cache may keep pictures on your PC (up to 30). Its local-retention switch is on by default in Diagnostics (main menu). Cached failure frames are uploaded only with Send this frame; review the selected image first. Save frame also saves game images you may choose to attach in a bug-report archive. The reader also keeps confidently recognised Vorax card names and instrument pictures as small grids of numbers in its data folder. With Share minigame runs on (on by default for new installs), these references may be shared too; they are not screenshots.
- Boards you type in, where neither the log nor screen reading covers them.
What the app keeps (history, settings, prices, your builds library) is stored in its data folder in your Windows user profile. It is yours: delete the folder and it is gone. The app never reads or changes the game’s memory, injects nothing and automates nothing.
What the app contacts without run sharing
- The price feed: The app gets public item prices from api.tlitoolkit.com. You can turn off the feed in Settings. If an item icon is missing locally, the app may download it from a saved image address, including one on tlicompanion.com.
- Usage statistics, only if you turn them on (Settings → General → Usage statistics, off by default): Google Analytics is told when the app starts and which of its pages you open (the page’s name, such as Vorax or History), with the app version, the UI language and a random id made for this alone (not the run-sharing id). It goes from the app straight to www.google-analytics.com; no Google script runs in the app. Never item names, prices, log paths, character or account names, or anything you type. Turning it off deletes the random id.
- The update check: GitHub’s public API, to see which versions of
SheF1k/tli-toolkit-releasesexist. A new version is downloaded from GitHub only when you click Update. - The patch status: tlitoolkit.com/status.json, a public file saying which parts of the app work with the current game patch (the status page), downloaded when the app starts and every 6 hours. No id and no other data go with it.
These sites see your IP address, as with any web request, and their own privacy policies apply (for tlitoolkit.com, this one: Cloudflare hosts it, see below). Nothing about you or your play is sent with these requests. A bug report (Ctrl+Alt+B) is a zip saved on your PC, with character names, account ids and IP addresses taken out of the log lines in it; you decide whether to attach it to a GitHub issue.
Run sharing (on by default)
Sharing is on by default, as in other trackers. The first time the app starts, a notice says so, with See what’s sent and Turn off right there; for community uploads, nothing is sent until that notice has been on screen for a minute or you close it. Settings → Community → Share my runs turns it off (or back on) any time. Recorded run-sharing choices are respected. Older installs without a recorded choice were switched on once with a notice. Separately, beta.51 turned private replay sharing on once when local retention and diagnostics were on, even if replay sharing had been off. Once it is on, each map you finish from then on is sent in small batches to the community server, to build the farming-strategy tables. Turning it off empties the queue. See exactly what’s sent in the app shows the next batch byte for byte. Each map carries:
- the hour it started, rounded to the hour (not the minute), and how long it took;
- its zone, Timemark tier and kind of run;
- what opening it cost and what dropped, as item ids and counts; for a map, the Netherrealm Resonance spent opening it and on rerolls, as separate numbers (the sum is already part of the cost);
- your setup: the Pactspirits and Void Chart constellations the app knows about, and your hero and its trait (game ids);
- for a map, how far your Void Chart goes into each constellation: none, light (under a third of its points) or heavy (a third or more), and Profound in or out; never the nodes themselves, and nothing when the app is not sure of your chart yet; When available, shared maps include points allocated and total points per non-Profound constellation.
- the app version, the season, an optional game-server region, and a random install id the app made (you can reset it).
- for a map, the Vorax and Tartarus entry tokens it earned (so the strategy tables can credit the minigames back to the maps that paid for them);
- for a map, its boss fight: the seconds from the map’s start to the fight, and from the fight’s start to the kill;
- for a map, how many Cube of Rapacity Greeds the game log showed during it, won and lost (for the measured Greed chance on the Odds Lab);
- for a Tartarus run, how many Warden’s Caches of each rarity its Riot opened, and its special caches (the start-of-fight cache, the Jailer’s), as the game log shows them (the caches’ ids and counts only);
- for a Tartarus run, only while Share minigame runs is on too: how many Warden’s Caches of each rarity its Riot opened and whether the Objective’s cache came, from the advisor’s journal of that run.
While sharing is on, the app also checks in once a day: it tells the community server that a copy is running, with the same random install id, the app version and the UI language, and nothing else.
While sharing is on, the app also sends the Trade House searches it sees in the game log, which make TLI Toolkit’s own item prices: for each search, the item, the prices listed (the 40 cheapest), the season and when, with the same random install id and the app version. Each install’s latest search of an item in an hour counts once. The searches are kept 14 days; the hourly prices made from them hold no install id and are kept 180 days.
Earlier maps, only if you ask. Maps you finished before sharing was on are sent only if you ask for it: Settings → Community → Also share my earlier maps. Then the finished maps History has from this season and the one before (not the ones you left out of your stats or edited by hand) are sent once each, oldest first, a few hundred a day, with the same fields and the same random install id, plus the price the app had saved for each of their items. Those prices are used only for days before the community’s reference prices began, and only within a limit around them. Delete my data removes them like every other map sent with that id.
Minigame run sharing (on by default)
A separate switch, on by default for new installs (settings from an older version keep what they had): Settings → Community → Share minigame runs to improve the advisors, one click turns it off. The app keeps a journal of each Vorax and Tartarus Prison run you use its advisor in, on your PC. With the switch on, each run you finish from then on (never practice runs) is sent after the minigame closes, with the same random install id as run sharing, so the advisors can be checked against real games. See exactly what’s sent shows it. Each run carries:
- the hour it started, rounded to the hour, and how long it took;
- each board the advisor was asked about, as game ids and numbers (monsters or Inmates, cards and instruments on offer, the round or day), whether it was read from the screen, corrected or typed in, and the reader’s confidence;
- the advisor’s three best moves with what it expected of each, and the move you made;
- how the run ended, as far as the app knows (the final score or Chromatics);
- Observed end outcomes are included only while minigame run sharing is on, to improve the advisors: Vorax final score and reward bonus, or Tartarus final board, Chromatic score and completion result. Missing values stay unknown; no new identifiers, images or free text.
- the app version, season, UI language, the advisor’s settings, and the game window’s size and UI scale (to fix misreads).
With the same switch on, the app also sends, at most once a day and only after a minigame run was sent, what the Vorax screen reader has learned since: small grids of numbers made from the game’s interface, one for each card name and instrument picture it learned to recognise (a few kilobytes at most), with the same random install id and nothing else. They are sent so the reader recognises more cards for everyone: the ones several players’ readers agree on are added to the app’s built-in references. Never a picture of your screen, a crop of it, a window title or a file path; the numbers cannot be turned back into a picture. See exactly what’s sent shows them too.
With the same switch on, the TOWER Sequence calculator’s rounds that its screen reader read surely go with them: for each R&D, its type (Basic or In-Depth), the hour it started and the chips each round offered, nothing else (not the chips you took, the weapon or the sequences you want).
Shared minigame runs are also counted for the Odds Lab: how often each kind of Vorax card and each instrument is offered, and how many Warden’s Caches a Riot opens. Only totals are published, and only once at least 5 players have sent some. The same runs give the advisor results: for each game and season, how runs ended when players followed the advice and when they didn’t (runs, players, the share that reached the goal). A row is listed only with at least 3 players and 10 runs, and its numbers only with 5 players.
Diagnostics (on by default)
To find what breaks, the app records things that fail quietly (an icon that is missing, a game screen it cannot read, an item or price it does not know) in a file on your PC, and sends a summary to the community server once a day at most: the kind of failure, item ids, how many times, the app version, the game and the size of the screen it read, and the same random install id. The daily summary contains no paths, your name or character name, item names, or pictures. Kept 90 days, and removed by Delete my data.
With the same diagnostics switch, the app also counts page and tool opens (such as a calculator tab, Explain or the mini window) and how many Vorax/Tartarus advice decisions were shown, from a fixed list of short names. These counts travel in the same upload with the random install ID. The server stores only combined totals per day and feature, without an install ID, for 400 days. Turning off this switch stops sending failure details and feature counts. See exactly what’s sent shows the counts too.
Send diagnostics and feature counts is a separate switch, on by default, in Diagnostics (main menu). Its own notice offers Turn off; the upload schedule does not wait for that notice to close or for community sharing to be on. See exactly what’s sent previews the next summary. Keeping failed-read frames locally is a separate default-on switch (up to 30). A frame from this separate cache is uploaded only when you press Send this frame, scaled down and kept for 90 days. Review it before sending.
Automatic reader incident reports
With diagnostics on, the app automatically sends private reports for problems observed during Vorax or Tartarus reads. Each report uses predefined codes for the observed steps, field results and image status, with the app version and random installation ID. The report can also include time between steps, capture dimensions, attempt numbers and response status codes. It contains no image, recognized text, paths or raw log lines. If a replay image exceeds its size or daily limit, the incident report can still be sent.
The incident limit per installation is 24 reports and 96 KiB of request bodies per day, with at least 60 seconds between new reports. Each incident is at most 4 KiB, and the whole request is at most 6 KiB. Replay images have separate limits.
Turn off diagnostics in Diagnostics (main menu) to stop automatic incident reports. You can turn off replay image sharing separately. Reports are kept privately for up to 14 days. Delete my data removes reports sent by this installation. Sending selected game or app log text still requires developer approval, an editable preview and pressing Send.
Private read replay bundles
Supported uncertain or rejected reads can save a replay locally under Diagnostics (main menu) → Keep failed-read pictures and uncertain-read bundles on this PC (on by default). It holds numeric reader evidence, the board before/proposed/accepted, confidence and reasons, solver input and advice state where available, app/reader versions, game language, resolution, capture method and time. A bundle may include the full analyzed game-client area, with window borders cropped, only from a verified game-window capture; the HUD can remain. Images that fail format or size checks are omitted. Desktop fallback and unverified captures keep state only. A game image can still show character names or chat.
New local replays expire after 14 days and keep at most 30 bundles, 36 MB (36,000,000 bytes) each. That is up to 300 MiB of replay payload plus file overhead, additional to the existing failure-frame cache and other app files. New bundles replace the oldest at the limit. Turning local retention off stops future saves; existing bundles stay until expiry, eviction or Clear.
Private replay sharing is on by default on new installations. When both local retention and diagnostics are on, the beta.51 update turns replay sharing on once, including PCs where it was off. If either control is off, replay sharing stays off until you choose to enable it. You can turn it off again in Diagnostics (main menu), and that choice is saved. Sharing requires both local replay retention and Send diagnostics and feature counts. Only new captures made while all three switches are on enter the upload queue. Previously saved bundles stay on your PC. New bundles go to the developer’s private diagnostics storage under the same installation id. The server keeps its keyed hash. These bundles are not published in community tables. Up to 5 unique submissions per installation and UTC day share the existing manual-frame quota, with a 36 MB combined limit per replay bundle.
Turning off automatic sharing, local retention or Send diagnostics and feature counts cancels queued retries; it does not recall uploads already sent. Clear removes local replay bundles and queued sends. Delete my data removes uploaded diagnostics for the original installation. Replay access expires after 14 days. Scheduled cleanup removes expired copies and retries after failures. Separately sent legacy failure frames keep their 90-day policy.
Manually shared developer logs
Developer mode is off by default on each PC. To request access, link this installation to your Steam account and show its request code to the Toolkit owner. The owner chooses which features this installation may use, including game logs and app logs separately. Approval expires within 30 days and can be revoked sooner. A separate permission can lift the daily bundle count limit while developer mode and that option are on. Image sharing keeps its own controls.
To share a log, enable Send diagnostics and feature counts, developer mode and manual log sharing on this PC. Choose the game log or a current or previous app log, then select the portion to share. Review the text, edit out anything you want to keep private, then press Send. Each submission contains the selected range information and the exact text you reviewed, along with the app version and installation identity. A preview expires after one hour. Each additional range needs its own review and Send. Requesting access, receiving approval and preparing a preview never upload log text.
The app masks known patterns such as labelled credentials, paths, email addresses and recognized player names. Chat, unfamiliar identifiers and other free text can still identify people. Check each preview before sending.
New game-log lines (off by default)
Settings → Community → Record new game-log lines is off unless you turn it on, and it works only while Share my runs is on. It counts the kinds of game-log lines the app cannot read yet, so a new season can be supported sooner. At most every 6 hours it sends each kind once, with the same random install id and the app version: the line’s leading code name (digits replaced by #), the names of its fields, up to two shapes of the line with every value replaced by ?, and how many lines it saw. A name the app knows as your character’s is never kept, not even as a code name or a field.
Never a whole line, a value, your character name, account or player ids, or anything you typed. Turn the switch off and what was waiting on your PC is forgotten at once. See exactly what’s sent shows the next upload byte for byte while the switch is on.
Names and files
- Community run uploads and daily diagnostic summaries do not include character/account names or player/account ids as fields. A shared game image can show character names or chat.
- The labels you write for your own strategies.
- Community run uploads and daily diagnostic summaries exclude screenshots and files. When private replay sharing is enabled, bundles can include verified game-window images; desktop fallback and unverified captures contribute state only. Send this frame remains a separate manual upload. Bug-report archives stay on your PC until you choose to attach or send them.
- Your IP address: see below.
IP addresses and the install id
For flood limits, the community API uses daily-changing salted hashes of IP addresses. Raw IP addresses are not stored in the community database; Cloudflare can keep them in hosting request logs (see Who handles the data). The database keeps a keyed hash of your install id, never the id itself.
How long it is kept
- Raw shared maps are kept for two seasons, then deleted.
- Shared minigame runs are kept for two seasons too, then deleted, and so are the screen reader’s learned number grids sent with them.
- Daily check-ins: 15 days with the keyed hash of the install id, then only as counts per day, version and language, for 90 days.
- Daily diagnostic summaries and separately sent failure frames: 90 days. Feature-use counts hold no install id and are kept 400 days.
- Private replay bundles: local copies expire after 14 days; uploaded access expires after 14 days, with scheduled cleanup and retries for expired copies. The separate legacy manual-frame policy remains 90 days.
- Manually shared game and app logs are private to the developer. Access lasts up to 14 days from preview preparation and ends sooner if approval expires or is revoked. Scheduled cleanup retries failed deletions. Delete my data in the app erases logs sent by this installation.
- Recorded kinds of log lines hold nothing about who sent them and are kept until no install has seen them for 400 days. The counter that limits uploads per day, kept under your install id, is deleted after 15 days or by Delete my data.
- A sync: until you stop it, or a year after it was last used. A short plan link: two years after it was last opened. An account and its builds: until you delete them; a sign-in ends after 14 days without use. Feature votes: a month’s single votes are deleted 90 days after its vote closes; only the totals stay.
- Gameplay statistics use minimum sample sizes only: season strategy rows and choices need 2 installations and 10 maps; period rows need 2 installations and 15 maps, or 3 installations and 10 maps; equipment shares and mixes need 2 installations and 5 maps; hero rankings need 2 installations and 20 maps, or 3 installations and 10 maps. Ordinary season totals keep their 2-installation/10-map floor. Other tables retain their own contributor and statistical quality minimums. No gameplay result is published from one installation alone, including explicitly published setups. Names, installation IDs and fingerprints are not public. Small groups may estimate each other’s results by comparing tables or releases. Sharing controls, opt-out, withdrawal, deletion and retention are unchanged; historical coverage can have gaps.
- The measured odds on the Odds Lab are totals too (counts, shares and their ranges), each published only once at least 5 players have sent some, with nothing said about how many outcomes there are before that. The advisor results are totals of the same kind: a row needs 3 players and 10 runs, and its numbers 5 players.
Deleting your data
In the app: Settings → Community → Delete my data. Every map sent with your install id is left out of the next published tables (within a day) and removed from storage at the next clean-up, and so are its daily check-ins; its Trade House searches are deleted at once; minigame runs sent with it, and the learned number grids, are deleted at once; its diagnostics and any frame you sent are deleted at once too; the daily counter for new game-log lines is deleted at once too (the recorded kinds hold nothing about who sent them); setups you published from the app are taken down, and a link to your account, if you made one, is removed with its leaderboard entries; the app then makes a new id. The aggregation job keeps a cached copy. Its working mirror applies deletion markers and removes files absent from the source on a successful sync; this is not a fixed expiry for older GitHub cache copies. Reset id starts a new id without deleting anything. For anything else, write to hello@tlitoolkit.com. We keep a deletion marker in the database and object storage: the keyed hash of the old install id and deletion time, with no play data. It has no scheduled expiry and blocks late uploads from that id.
This website
tlitoolkit.com is a static site with no ads. To count visits it uses Cloudflare Web Analytics, which sets no cookies and stores no personal data: it counts visits, pages, referrers, countries and device types. That beacon, and Google Analytics if you accept it, are the only scripts from other sites; fonts and images all come from tlitoolkit.com. The site is in several languages: if you pick one with the language switcher, your browser keeps that choice (and whether it has already offered you a language) in its own storage, and nothing about it is sent anywhere. The build planner saves your draft in this browser. Sync and My builds are optional ways to save it on other devices or to your account (both below). Creating a short link saves the plan’s code on api.tlitoolkit.com under a short code, so the link fits a chat message: with no IP address, install id or account, kept until nobody opens it for two years (this browser keeps a key to delete it; to have one deleted sooner, write to hello@tlitoolkit.com). If the server can’t be reached, the link carries the whole plan in itself, after the #, which your browser never sends to a server. The strategy pages read the published tables, and the item pages the item prices and price history, from api.tlitoolkit.com (plain reads: nothing about you is sent). The Request a feature page talks to api.tlitoolkit.com as well; what it keeps is described in the next section. Downloads come from GitHub, whose privacy statement applies there.
Voting on feature ideas (no account)
On the Request a feature page, your browser makes a random ballot number (43 characters, nothing taken from you or your computer) and keeps it in its own storage on your device, so the page knows your votes are yours. Before your first vote the page also solves a small puzzle in your browser (about a second of work), which keeps bulk ballots from being made for free. The community server stores only a keyed hash of the ballot number (never the number itself), the points you put on each idea this month, and the times of those votes; it stores no name and not your IP address. The address is used for a moment, as a daily-changing salted hash, to slow down floods; to limit how many new ballots one network makes in a day, a count is kept for two days under a daily-changing salted hash of the address (for IPv6, of its network part), never the address itself. A vote is shown only as a number in the totals; nobody can see who voted. If you propose an idea, the text you write and the ballot hash are kept until it is reviewed; it is shown without a name, and links are not accepted. Press Delete my votes on the page to remove every vote of your ballot from the server and the ballot number from your browser; clearing your browser’s site data removes only the number on your device. If you sign in (optional), your votes are kept under your account instead of the ballot number, without the puzzle, so they follow you across devices; Download my data lists them, and deleting your account deletes them. A month’s single votes are deleted 90 days after its vote closes; only the totals stay. To have a proposal removed, write to hello@tlitoolkit.com.
Sync between devices (optional, no account needed)
Sync keeps the app’s settings, Pactspirits and Void Chart, and (only if you turn it on) your farming history the same on your PCs, and the planner’s drafts the same in your browsers. It is off until you start it. Your device makes a random key; everything it syncs is encrypted with that key on your device before it is sent, and our server cannot read it. Another device joins with a one-time pairing code (valid 10 minutes, used once) or the recovery phrase shown once when you start.
- What the server keeps: the encrypted data of each part you sync; a keyed hash of an id your device derives from its key (never the key); when the sync was made and last used, and when each part last changed; each part’s size and change counter. For 10 minutes after you show a pairing code, it also keeps your key locked with that code (it cannot open it without the code, which never reaches it).
- What it never gets: your key, the recovery phrase or a pairing code; your name, account or character names; your IP address (used for a moment, as a salted daily hash, to slow down floods, and not stored in the community database); the install id of community sharing (sync uses a separate key and is never linked to it); game logs, which never sync.
- Farming history (your maps, sessions and loot) is personal data about how you play: it syncs only if you turn on its own switch, which is off by default.
- Stop syncing and delete (in the app: Settings → Sync; on this site: the Sync page) deletes the server copy at once, from any of your devices. A sync nobody uses for a year is deleted. What each device has stays on it.
Sync and the optional Steam sign-in (next section) are separate: sync never needs an account, and a sync is linked to an account only if you press Attach on your account page.
Optional Steam sign-in and My builds
Draft: wording may change.
Steam sign-in is optional. Run sharing, voting and sync need no account and use separate random identifiers. Linking the app joins shared data to your account; signed-in votes belong to your account. Steam handles sign-in; we never see your password. Sign-in is meant for people aged 16 or over, or the age required in their country.
- What we keep while you have an account: your SteamID (the public number of your Steam account, kept as it is so we can find your account when you sign in; never shown to anyone); a random account id; the display name you choose; the build plans you save to My builds (name, the plan’s code, when saved); for each browser you sign in on, a hash of its sign-in token (never the token), when it signed in, was last used and when it expires; when the account was made and last used; and which of your syncs you attached to it, if you did.
- What we never take from Steam or keep: your Steam name, picture, friends, games, inventory or email; your password; your IP address (used for a moment, as a salted daily hash, to slow down floods, and not stored in the community database); the install id of community sharing (an account is linked to it only if you link the app yourself: next section).
- Cookies: only after you click Sign in with Steam, tlitoolkit.com sets a sign-in cookie (a random token; HttpOnly, Secure, SameSite=Lax; it keeps you signed in for 14 days and renews while you use the site) and a small cookie that holds only “1”, so pages can show My account without asking the server. While you are on Steam’s page, a third cookie (10 minutes) ties Steam’s answer to your click. They are needed for the sign-in you asked for; sign-in sets no analytics or advertising cookie.
- Why: to run the feature you asked for, keeping your builds under your account. Your builds are private: only you can see them, unless you publish one (next item). Your display name is also shown on the leaderboards, only if you switch them on (see Linking the app and leaderboards).
- Publishing a build as a guide (your choice, for each build): anyone can then see on tlitoolkit.com your display name, the guide’s title, description and tags, the plan as you published it (hero, trait, gear, skills, talents, notes, by stage) and how many times it was opened in the planner; never your SteamID or account id. A new guide may wait for a moderator, and three reports hide it until a moderator looks. For that we keep each report’s reason, note and time with a hash of the reporter’s account id or of a random id their browser made (never an IP), and for the copy count a hash of the day, the guide and that browser id, deleted after a day. If a moderator bars an account from publishing, a hash of its SteamID is kept so that a new account doesn’t lift it. Unpublish any time on your account page; deleting the build or the account deletes its guide and the reports on it. Current SteamID ban hashes are keyed; legacy bans may use unkeyed SHA-256.
- Your control: on your account page, Download my data gives you a file with everything listed above, with your published guides, linked apps and feature votes; Delete my account deletes at once the account, every sign-in, all of My builds and the guides published from them with the reports on them, the reports you filed, your feature votes, your app links and leaderboard switch, and the link to your syncs (the syncs themselves and everything on your devices stay). After account deletion, reviewed proposals stay without their ballot link; proposals still in review retain the account’s ballot hash. Blocked ballots, publishing-ban rows (account id, SteamID hash, date and reason) and moderation logs can remain. Current bans use a keyed SteamID hash; older bans may use unkeyed SHA-256. Earlier shared app data stays under its pseudonymous install id after the account link is removed. Sign out ends the session in that browser. Expired sign-ins are deleted daily; the account itself stays until you delete it. The data is stored and processed by Cloudflare (Workers and D1). Questions or requests: the contact address below.
Linking the app to your account, and the leaderboards (optional)
Draft: wording may change.
Community uploads use a pseudonymous random install id. You can link the app to your signed-in account using its one-time code, valid for 10 minutes (Settings → Account). Nothing is linked by default.
- What a link joins: everything that app’s install id shared with the community (runs, Trade House searches, minigame runs, published setups), earlier and later, becomes data about your account. Linking adds no upload: the app sends exactly what it sent before. While linked, that shared data is personal data about you, not anonymous.
- What we keep for a link: a row joining the keyed hash of the install id (never the id itself) to your account, with a random id and the time it was made; the short code is kept only as a hash and is deleted an hour after it expires.
- Leaderboards: a separate switch on your account page, off by default, that needs a linked app and a display name. When it is on, the leaderboards show your display name and your numbers (FE per hour over the last 7 days, your best Vorax and Tartarus runs), worked out from that app’s shared runs a few times a day. Never your SteamID, account id or anything else. Switching it off takes you off every board at once.
- What linking never does: it never changes what the app sends, never shows your shared data to anyone unless you switch the leaderboards on, and never links a second app unless you link that one too.
- Unlink in the app or on your account page to delete the join and leaderboard entries. Earlier shared data stays under its pseudonymous install id. Delete my data and Delete my account also remove the link. Download my data lists linked apps and leaderboard entries.
Google Analytics on this website (only if you accept)
On your first visit a banner asks whether we may also count your visit with Google Analytics. Until you click Accept, nothing is loaded from Google and no cookie is set; Decline keeps it that way. If you accept, Google’s script sets its cookies (_ga and _ga_…, kept up to two years) to tell visits apart, and reports the pages you open, where you came from, your country and city (worked out from your IP address, which Google Analytics doesn’t keep) and your browser, device and screen size. We see totals in Google Analytics’ reports, with Google signals and ad personalisation turned off. Your answer is kept in this browser only.
Legal bases and your rights
Draft: wording may change.
- Who is responsible for the data (the controller): the independent developer of TLI Toolkit, reachable at hello@tlitoolkit.com.
- Why we may use it (the legal bases of the GDPR): run sharing, minigame run sharing, Trade House searches, the daily check-in and diagnostics rest on our legitimate interest in building the community tables and prices and keeping the app working, weighed against what they hold (keyed hashes, no names, no IP addresses kept in the community database) and the switch that turns each one off at any time. Usage statistics in the app and Google Analytics on this website rest on your consent, which you can withdraw at any time. Sign-in, My builds, sync, short plan links, publishing, linking the app and the leaderboards rest on giving you what you asked for. The flood limits rest on our legitimate interest in keeping the service safe. Private replay uploads, incident reports and developer log submissions rest on your consent: you can turn them off or withdraw consent at any time. Keeping a SteamID hash for a publishing ban rests on our legitimate interest in preventing abuse.
- Your rights: you can ask for a copy of your data, to have it corrected or deleted, to restrict or object to its use, and for a copy in a machine-readable form. Most of this works by itself: in the app (See exactly what’s sent, Delete my data, the switches) and on your account page (Download my data, Delete my account). For anything else write to hello@tlitoolkit.com; for shared data, include the install id that See exactly what’s sent shows, because we keep only its keyed hash and can’t find your data without it. You can also complain to the data protection authority where you live.
Who handles the data
- Cloudflare hosts this website and the community server (Workers, with R2 and D1 for storage) and provides the website’s Web Analytics. Like any host, it processes each request, including your IP address, to deliver it and keep the service safe. Cloudflare Workers Logs records community API requests for operations and debugging: time, request path, response status and request metadata such as IP address and user agent, as provided by Cloudflare. These logs are kept for a limited period set by Cloudflare. This is separate from the community database and from the website’s visit statistics.
- GitHub hosts downloads, release notes and bug reports, and runs community aggregation. Shared data is copied to its servers with keyed hashes, never install ids or IP addresses. The aggregation job keeps a cached copy. Its working mirror applies deletion markers and removes files absent from the source on a successful sync; this is not a fixed expiry for older GitHub cache copies.
- Valve (Steam) shows the sign-in page when you choose Sign in with Steam, and tells us only your SteamID. Steam’s privacy policy applies there.
- Google provides Google Analytics: on this website only if you accept it, and in the app only while Usage statistics is on. Google’s privacy policy applies to what it receives.
- Public item prices come from TLI Toolkit and TITrack players’ Trade House searches. The community server keeps dated prices to value shared maps.
Cloudflare, GitHub, Google and Valve are based in the United States and may process data there and elsewhere, under their own data processing terms.
Changes and contact
If this policy changes, the date at the top changes and the changelog says what changed. Questions or requests: hello@tlitoolkit.com, or a public question on GitHub issues. See also the terms of use and Safety & privacy.
