Correction reports
Send the affected URL, item or formula input, observed result and supporting source.
CONTACT AND CORRECTIONS
Report the exact page, value and source.
Useful reports make a correction faster. Include the page URL, what appears wrong, the expected result, the date observed and a current source where possible. Never send a Jagex password, Steam password, Bank PIN or authenticator code.
Editorial review
Privacy requests
Identify the browser or request involved without sharing game-account credentials.
Accessibility
Describe the device, browser, assistive technology and step that is blocked.
01
Public contact channel
The public contact email has not been configured in this local build. Set CONTACT_EMAIL in the production environment before launch; the launch check treats a missing address as an error.
Do not send account credentials, session tokens, payment details or information that is not needed to understand the report.
02
What to include in a correction
For a Grand Exchange issue, include the item, displayed timestamps and whether the problem affects high, low, volume, tax or margin. For a calculator, include non-sensitive inputs, the displayed result and the formula reference. For a quest, boss, gear or Diary page, link the current source that changed.
Hiscores reports should not include a password or proof-of-ownership document. A public display name and selected mode are enough to reproduce a public lookup problem.
03
Response and publication
LootPath may reproduce a technical issue in a test environment and update the shared data or model. Material corrections should appear in the changelog and update the affected page's reviewed date.
Sending a report does not guarantee a response time or publication. Spam, credential submissions, account-sale requests and requests to manipulate rankings or market data may be ignored.
04
Security reports
Use the contact address for a concise, responsible report that identifies the affected URL, impact and safe reproduction steps. Do not access other users' data, degrade the service or disclose an unpatched issue publicly before reasonable review.
LootPath does not currently operate a paid bug-bounty programme. A good-faith report is still welcome and should avoid collecting more data than necessary.
HOW TO READ THIS PAGE
Use the policy at the point where a decision is made
contact OSRS DPS Calc — The contact page defines a reproducible path for reporting an OSRS data correction, calculator defect, accessibility barrier, privacy request, attribution issue or responsible security concern.
Use the public contact channel with the exact page URL, observed result, expected result, date, non-sensitive inputs and a current supporting source. That information lets one shared data record or formula fix every affected localized page. Correction reports, Privacy requests, Accessibility.
Do not send account credentials, session tokens, payment details or identity documents. A public display name and account mode are enough to reproduce a Hiscores lookup problem.
For Grand Exchange issues, include the item, high and low timestamps, volume state, tax or margin field and the price observed in game.
For calculators, include visible non-sensitive inputs, the output, the expected formula step and the cited mechanic that appears inconsistent.
For quests, bosses, gear or Diaries, name the requirement or recommendation that changed and link the most specific current reference.
For accessibility, include browser, device, assistive technology and the blocked interaction. For security, provide safe reproduction steps and minimize any collected data.
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.
Correction reports
Send the affected URL, item or formula input, observed result and supporting source.
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.
Privacy requests
Identify the browser or request involved without sharing game-account credentials.
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.
Accessibility
Describe the device, browser, assistive technology and step that is blocked.
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 “Report the exact page, value and source.” must stay consistent across five places: the title promise, the H1 topic, the search description, the sections Public contact channel, What to include in a correction, Response and publication, 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.
For Grand Exchange issues, include the item, high and low timestamps, volume state, tax or margin field and the price observed in game.
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.
For calculators, include visible non-sensitive inputs, the output, the expected formula step and the cited mechanic that appears inconsistent.
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.
For quests, bosses, gear or Diaries, name the requirement or recommendation that changed and link the most specific current reference.
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.
For accessibility, include browser, device, assistive technology and the blocked interaction. For security, provide safe reproduction steps and minimize any collected data.
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.
Public contact channel
What it establishes: The public contact email has not been configured in this local build. Set CONTACT_EMAIL in the production environment before launch; the launch check treats a missing address as an error.
How to use it: For Grand Exchange issues, include the item, high and low timestamps, volume state, tax or margin field and the price observed in game.
What to include in a correction
What it establishes: For a Grand Exchange issue, include the item, displayed timestamps and whether the problem affects high, low, volume, tax or margin. For a calculator, include non-sensitive inputs, the displayed result and the formula reference. For a quest, boss, gear or Diary page, link the current source that changed.
How to use it: For calculators, include visible non-sensitive inputs, the output, the expected formula step and the cited mechanic that appears inconsistent.
Response and publication
What it establishes: LootPath may reproduce a technical issue in a test environment and update the shared data or model. Material corrections should appear in the changelog and update the affected page's reviewed date.
How to use it: For quests, bosses, gear or Diaries, name the requirement or recommendation that changed and link the most specific current reference.