Progress stays in your browser
Where a tool saves a route or checklist, it uses local browser storage unless a future feature clearly says otherwise.
PRIVACY AND DATA USE
Useful OSRS tools without an account-data trade.
LootPath is designed to work without a LootPath account and without access to your Jagex or Steam credentials. This policy explains the limited information involved when you browse the site, use a calculator, save local progress or choose optional analytics.
Editorial review
Analytics storage requires consent
The Google tag uses Consent Mode on every page. Analytics cookies remain denied until you accept.
No game credentials
LootPath never asks for a Jagex password, Steam password, Bank PIN, authenticator code or game session.
01
Information used by the website
The hosting provider may process routine request information such as IP address, browser type, requested URL, timestamp and security logs so the website can be delivered and protected. Retention and infrastructure location depend on the selected production host.
Interactive calculator inputs are processed in the browser where possible. LootPath does not send skill levels, budgets, setup values or planning choices to Google Analytics. Saved planner and Diary progress remains in local browser storage in the current release.
02
Optional Google Analytics
LootPath places the Google tag on public pages with analytics storage denied by default. Before acceptance, Google Consent Mode may send limited cookieless page-view and consent signals. Accepting enables analytics storage so GA4 can measure page views and understand which public tool pages are useful.
Advertising storage, ad user data and ad personalization remain denied. LootPath does not intentionally attach a player name, Jagex account identifier or calculator input to an analytics event. Cookie preferences in the footer can change the choice, which is stored locally with a policy version.
03
Hiscores and external data requests
A Hiscores search sends the entered display name and selected account mode to LootPath's server route, which requests the public Jagex Hiscores service. The result is returned for the current lookup and is not turned into a permanent public player-profile page or added to the sitemap.
Grand Exchange tools request public community price data from the OSRS Wiki service on the server. Clicking an external source link takes the visitor to that publisher, whose privacy practices then apply.
04
Your choices and requests
You can clear local LootPath progress and consent values through browser storage controls. You can also decline or revoke optional analytics through Cookie preferences. Browser privacy tools may block additional storage or measurement.
For access, correction or deletion questions about information controlled by LootPath, use the localized Contact page. Some infrastructure logs may need to be retained temporarily for security, fraud prevention or legal obligations.
05
Children, changes and scope
LootPath is a general fan-made game utility and does not knowingly collect account credentials or create profiles for children. A parent or guardian can contact the site if they believe personal information was submitted improperly.
This policy applies to LootPath pages and server routes, not to Jagex, Steam, the OSRS Wiki or other linked services. Material changes receive a new reviewed date and, when analytics choices are affected, a new consent-policy version.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
OSRS DPS Calc privacy policy — This policy explains what happens when someone opens OSRS DPS Calc, uses a public calculator, saves progress locally, searches public Hiscores or permits audience measurement. It distinguishes browser storage, server requests, infrastructure logs and external services.
Use it to understand which information leaves the browser and which remains on the device. Calculator values and manually saved planning progress are local unless a page explicitly states otherwise; a Hiscores query necessarily sends the public display name to the lookup route. Progress stays in your browser, Analytics storage requires consent, No game credentials.
Never submit a Jagex or Steam password, Bank PIN, authenticator code, session token or payment information. OSRS DPS Calc does not need those credentials to calculate DPS, XP, prices, progress or public ranks.
Review the Cookie page for the exact analytics choice and reopen Cookie preferences when you want to change that choice.
Treat public display names as searchable game records, not as identity verification. Hiscores results are displayed for the lookup and are not published as permanent profile URLs in the sitemap.
External source links leave this site and become subject to the destination publisher's privacy practices. Verify the domain before entering any account information.
A correction or privacy request should include the affected public URL and enough technical context to reproduce the issue, while excluding credentials and unrelated personal information.
OPERATIONAL PROMISES
What each principle requires in a working OSRS tool
A principle matters only when its effect is visible in the interface, evidence trail or missing-data behaviour.
Progress stays in your browser
Where a tool saves a route or checklist, it uses local browser storage unless a future feature clearly says otherwise.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
Analytics storage requires consent
The Google tag uses Consent Mode on every page. Analytics cookies remain denied until you accept.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
No game credentials
LootPath never asks for a Jagex password, Steam password, Bank PIN, authenticator code or game session.
Apply this principle to the nearby result, reviewed date, status and source. If the page cannot show how the promise works, clarify the claim before it influences an account decision.
REVIEW CHECKPOINTS
Four questions to ask before trusting a result
The answer should be visible on the landing page or one clearly linked methodology or source page.
Identify Jagex data, community market signals, a deterministic formula, reviewed reference or illustrative model.
Read inputs and exclusions. A bounded correct answer can still be wrong when applied to a different question.
Separate live request time from editorial review. Market signals age faster than stable formulas.
Use the in-game GE for fills, official services for accounts and current references before risking GP or time.
PAGE GOVERNANCE
A published policy needs an owner, a trigger and a visible correction path
This page is reviewed as part of the same system as the calculators and guides. The review is not complete merely because the page renders, contains a recent date or reaches a target word count. It must still describe the current implementation, use language a player can understand and lead to a practical action when the statement is wrong.
Search engines and AI systems should be able to identify the same relationship a player sees: this page states a defined policy or editorial process; linked tools apply it; page-specific evidence supports it; and the Contact and Changelog pages provide a correction trail. That structure is more useful than repeating a brand or keyword without operational detail.
The review outcome for “Useful OSRS tools without an account-data trade.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections Information used by the website, Optional Google Analytics, Hiscores and external data requests, and the related-page links. If one changes without the others, the page can mislead a player or compete with another landing page. A correction should update the shared source of truth, preserve the change history and request a new Google crawl only after the published version is verified.
Scope owner
The page owner checks that the title, main heading, description and body describe one primary topic. Related subjects can be linked, but they should not quietly expand the promise beyond what the current product, data source or contact process can support.
Review the Cookie page for the exact analytics choice and reopen Cookie preferences when you want to change that choice.
Material review trigger
A review is required when a data provider, formula, analytics configuration, hosting behaviour, account-link process, legal purpose or public contact route changes. Styling, dependency updates and routine deployments do not by themselves prove that the policy content was rechecked.
Treat public display names as searchable game records, not as identity verification. Hiscores results are displayed for the lookup and are not published as permanent profile URLs in the sitemap.
Evidence record
The reviewed date, linked source, visible interface state and changelog entry should agree. If a live implementation differs from this text, the discrepancy is treated as a correction task rather than hidden behind a broad disclaimer or an automatically refreshed timestamp.
External source links leave this site and become subject to the destination publisher's privacy practices. Verify the domain before entering any account information.
Localized parity
English, Brazilian Portuguese and Latin American Spanish pages share the same product boundary but are reviewed as separate landing pages. Each version keeps official OSRS terminology where players need it and explains the surrounding obligation, risk and next step in locally natural language.
A correction or privacy request should include the affected public URL and enough technical context to reproduce the issue, while excluding credentials and unrelated personal information.
TRACE THE CLAIM
Move from summary to supporting detail
These sections establish the page-specific scope. Continue into the full text whenever an exception matters.
Information used by the website
What it establishes: The hosting provider may process routine request information such as IP address, browser type, requested URL, timestamp and security logs so the website can be delivered and protected. Retention and infrastructure location depend on the selected production host.
How to use it: Review the Cookie page for the exact analytics choice and reopen Cookie preferences when you want to change that choice.
Optional Google Analytics
What it establishes: LootPath places the Google tag on public pages with analytics storage denied by default. Before acceptance, Google Consent Mode may send limited cookieless page-view and consent signals. Accepting enables analytics storage so GA4 can measure page views and understand which public tool pages are useful.
How to use it: Treat public display names as searchable game records, not as identity verification. Hiscores results are displayed for the lookup and are not published as permanent profile URLs in the sitemap.
Hiscores and external data requests
What it establishes: A Hiscores search sends the entered display name and selected account mode to LootPath's server route, which requests the public Jagex Hiscores service. The result is returned for the current lookup and is not turned into a permanent public player-profile page or added to the sitemap.
How to use it: External source links leave this site and become subject to the destination publisher's privacy practices. Verify the domain before entering any account information.