Local tool settings
Browser storage can remember a consent choice or progress that the visitor explicitly saves on that device.
COOKIE AND STORAGE CHOICES
Analytics stays optional. Tool progress stays local.
LootPath separates storage needed for a visitor's own settings from optional audience measurement. The site does not currently use advertising cookies, cross-site behavioural profiles or a Jagex login cookie.
Editorial review
GA4 storage
The Google tag is present, but analytics cookies remain denied until an affirmative choice.
Change the choice
Cookie preferences in the footer can reopen the consent panel at any time.
01
What LootPath stores
The current site uses localStorage for the analytics consent choice and for selected tool progress such as manually checked Diary tasks or planning state. localStorage is tied to the browser and device; it is not automatically synchronised to another computer.
Strictly necessary hosting or security cookies may be added by the selected deployment platform, load balancer or abuse-protection service. Their names and retention should be verified in the live production response after the domain is connected.
02
How optional analytics works
If a valid GA4 Measurement ID is configured, the Google tag and consent panel are present on every public page. analytics_storage, ad_storage, ad_user_data and ad_personalization default to denied. Before acceptance, Consent Mode may send limited cookieless page-view and consent signals; accepting enables analytics storage while advertising-related consent remains denied.
Page-view events include the public page URL and title. LootPath deliberately avoids sending Hiscores display names, calculator inputs, budgets, skill levels or Jagex identifiers as analytics parameters.
03
Accept, decline or remove
Accept Analytics enables analytics storage for the current browser. Decline keeps that storage denied and limits measurement to cookieless signals. Cookie preferences in the footer reopens the panel so the visitor can change that choice.
Clearing site data in the browser removes the stored choice and any locally saved tool progress. Browser extensions, private browsing and tracking prevention can also restrict Google Analytics independently of the site's controls.
04
Policy changes
The consent record includes a policy-version key. If LootPath materially changes what analytics measures or introduces a new storage purpose, the version should change so visitors are asked again.
A production launch check must confirm the real domain, GA4 ID and privacy contact before deployment. The live site should then be inspected for host-added cookies that are not visible in the local build.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
OSRS DPS Calc cookie policy — This policy separates storage required for a visitor's own local settings from Google Analytics measurement. It explains what the current public site can store, which consent signals are sent and how the choice can be changed.
Use it to inspect the difference between localStorage used for tool progress or a consent choice and cookies or cookieless signals used by an analytics provider. Browser privacy features can independently restrict either mechanism. Local tool settings, GA4 storage, Change the choice.
Advertising storage, ad user data and ad personalization are not enabled by the current implementation. A future change in purpose requires a revised policy version and a new consent decision.
Open Cookie preferences from the footer to accept, decline or update optional analytics for the current browser.
Clear site data when you also want to remove locally saved planner or Diary state; this may remove useful progress together with the consent record.
Inspect production responses after hosting changes because security, load-balancing or abuse-prevention infrastructure can add strictly necessary storage that is not visible in a local build.
Do not attach Hiscores display names, skill levels, gear setups, budgets or calculator inputs to analytics events. Public page URL and title are sufficient for page-level measurement.
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.
Local tool settings
Browser storage can remember a consent choice or progress that the visitor explicitly saves on that device.
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.
GA4 storage
The Google tag is present, but analytics cookies remain denied until an affirmative choice.
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.
Change the choice
Cookie preferences in the footer can reopen the consent panel at any time.
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 “Analytics stays optional. Tool progress stays local.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections What LootPath stores, How optional analytics works, Accept, decline or remove, 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.
Open Cookie preferences from the footer to accept, decline or update optional analytics for the current browser.
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.
Clear site data when you also want to remove locally saved planner or Diary state; this may remove useful progress together with the consent record.
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.
Inspect production responses after hosting changes because security, load-balancing or abuse-prevention infrastructure can add strictly necessary storage that is not visible in a local build.
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.
Do not attach Hiscores display names, skill levels, gear setups, budgets or calculator inputs to analytics events. Public page URL and title are sufficient for page-level measurement.
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.
What LootPath stores
What it establishes: The current site uses localStorage for the analytics consent choice and for selected tool progress such as manually checked Diary tasks or planning state. localStorage is tied to the browser and device; it is not automatically synchronised to another computer.
How to use it: Open Cookie preferences from the footer to accept, decline or update optional analytics for the current browser.
How optional analytics works
What it establishes: If a valid GA4 Measurement ID is configured, the Google tag and consent panel are present on every public page. analytics_storage, ad_storage, ad_user_data and ad_personalization default to denied. Before acceptance, Consent Mode may send limited cookieless page-view and consent signals; accepting enables analytics storage while advertising-related consent remains denied.
How to use it: Clear site data when you also want to remove locally saved planner or Diary state; this may remove useful progress together with the consent record.
Accept, decline or remove
What it establishes: Accept Analytics enables analytics storage for the current browser. Decline keeps that storage denied and limits measurement to cookieless signals. Cookie preferences in the footer reopens the panel so the visitor can change that choice.
How to use it: Inspect production responses after hosting changes because security, load-balancing or abuse-prevention infrastructure can add strictly necessary storage that is not visible in a local build.