Haze Seas source policy keeps codes, release status, platforms, systems, and wiki pages tied to official sources, high-trust sources, or clearly labeled unknowns.
Source hierarchy
Haze Seas source policy uses official sources first: the Roblox game page, Haze Studios Discord, Haze Studios YouTube, and any developer-controlled links. High-trust guide sites can support public code lists, link discovery, and player-task context. Community wikis, community videos, comments, and reposts are treated as leads until checked.
Code policy
Codes are useful only when players can act on them. This Haze Seas source policy requires a checked date, a source note, and a visible boundary for working-code claims. If a code appears in public lists but is not confirmed by an official channel, the page can list it with a public-source note. If a code fails repeatedly and high-trust sources mark it expired, it moves to expired codes.
Wiki page policy
Systems pages can publish when they answer a real player question with source-backed facts. Fruits can publish because the Roblox description lists fruit names and timing. Races can publish because Race Spins are code rewards and high-trust links identify Races as a key topic. Bosses and Weapons can publish as cautious overview pages. Boss drops, maps, builds, rates, and tier lists stay held until evidence improves.
What this site refuses to guess
This site will not invent release dates, exact expiry times, damage values, drop rates, boss respawns, maps, best builds, platform support, or official status for community pages. Haze Seas source policy exists so players can see why a page is missing instead of reading a confident but weak answer.
Update method
When a fact changes, the visible page, related pages, update log, RSS, sitemap date, and source notes should change together. A Haze Seas source policy page is only useful if it shapes the rest of the site, not if it sits apart from it.
Analytics and privacy
This site uses Google Analytics for aggregate traffic measurement. Analytics helps show which Haze Seas pages players use most, but it does not change code status, source confidence, or guide claims. The measurement script is loaded from Google Tag Manager across the shared layout so page tracking stays consistent.
Advertising placement
This site uses a small 320 by 50 display ad slot between the navigation and the page content. The ad slot is reserved before the script loads so the guide does not jump around, and advertising does not affect code status, source confidence, page recommendations, or wiki boundaries.