Trust policy

Every important Azur Promilia claim needs a visible source label.

This page explains how the site separates official facts, reliable reporting, beta/test information, community records, unknowns, and editorial context across character, Kibo, release, guide, and news pages.

Last updated: July 21, 2026

HighestOfficial

Official website, publisher posts, official videos, store pages, or direct official announcements.

UsableReliable coverage

Established reporting that points back to official information, events, trailers, or publisher activity.

LimitedBeta / test

Regional tests, closed beta notes, or observed build details that may change before launch.

HoldUnknown

Common questions without reliable confirmation, including launch date, launch rewards, or final gameplay values.

Short rule

Write what can be checked, label what can change.

Official sources can support direct factual statements. Reliable reporting can support summaries when the article clearly points to official activity. Community sources can help discover names or leads, but should not become gameplay facts without confirmation.

For character pages, an official name and a CBT/media profile field are separate claims. A character name can be official while weapon, element, race, role, or skill notes remain reported beta-context or community-listed.

Allowed source types

What counts as a source?

OfficialOfficial website, official social posts, official trailers, official event pages, store listings, and publisher announcements.

Reliable reportingEstablished news sites or databases that report on official announcements, trailers, store pages, events, or publisher activity.

Community recordsFan wikis, screenshots, tables, or community notes. Useful for leads, but not enough for final gameplay claims.

Local editorialOur own summaries, safety guidance, and organization rules. These must be written as analysis, not as official claims.

Label guide

How labels should be used

ConfirmedUse for official information or high-confidence reporting tied to official material.

BetaUse for CBT, demo, event build, regional test, or preview information that may change.

CommunityUse when the page is preserving a community-listed name, element, or note that still needs official confirmation.

UnknownUse when users search for the answer but no reliable current answer exists.

Do not display a mixed official and CBT record as simply confirmed. Use separate labels such as official name, CBT media fields, community fields, or reported beta-context so readers know exactly what is confirmed.

Citation rules

How pages should cite sources

Pages should link to the original official page or strongest available public source. Summaries should be written in original wording, with no copied article body text.

For changing topics such as beta access, release timing, redeem codes, store pages, and platform availability, pages should include a last-updated date and keep unconfirmed details visibly marked.

Speculation boundary

Do not turn release-window speculation into facts

Articles or tool-site posts that discuss possible 2026 windows, expected Q3/Q4 timing, Switch 2 speculation, or inferred platform plans should not be used as confirmed source material unless they point to an official announcement or store listing.

Those posts can be noted internally as leads, but public pages should keep release windows, platform expansions, and store timing marked unknown until official sources confirm them.

Regional test boundary

Official regional test pages do not become global launch facts

Official regional platform pages can confirm their own recruitment windows, test names, and local eligibility rules. For China Journey Test, the Biligame recruitment page is stronger than the general Biligame reservation page; the official Bilibili BW2026 video is Chinese-language official support; Inven is media reporting.

Do not reuse regional test recruitment as a global beta date, global release date, final platform list, launch reward claim, or global availability promise unless a global-facing official source confirms that specific claim.

Community watch boundary

Keep Reddit, Bilibili World, and milestone chatter in the watch lane

Community posts about JP CBT, CN CBT, pre-registration milestones, Bilibili World footage, or new character/gameplay details can help decide what to monitor next. They should not be promoted to official beta, release, platform, or character confirmations unless an official source confirms the same claim.

Reliable media event reports can support event-context notes. They should still be labeled as reports when the report does not itself confirm a launch date, global beta, platform store page, or final gameplay data.

Correction policy

How outdated claims get fixed

If an official source contradicts an older community note or older article, the official source wins. The page should update the claim, keep the source link, and avoid silently preserving outdated wording.

Visitors can use the contact page to report stale links, wrong names, missing official updates, or source labels that should be changed.

Send a correction

Compliance pages

Public trust pages

Before monetization or analytics are added, visitors should be able to review the site disclaimer, privacy policy, and contact policy.

Disclaimer Privacy Contact