Official website, publisher posts, official videos, store pages, or direct official announcements.
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: September 4, 2026
Established reporting that points back to official information, events, trailers, or publisher activity.
Regional tests, closed beta notes, or observed build details that may change before launch.
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?
Label guide
How labels should be used
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, pre-registration rewards, 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 global store timing marked unknown until official sources confirm them. Store-listed expected dates should be labeled by region and store, not rewritten as global launch dates.
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, local eligibility rules, and whether a recruitment page has closed or moved into a dated test window. For China Journey Test, current CN official context dates the test for September 17, 2026 at 11:00 UTC+8, with pre-download from September 15 at 15:00 UTC+8. TapTap official posts and Weibo-indexed official posts are the freshest timing sources; older Biligame recruitment and reservation pages remain regional source history.
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.
Regional pre-registration boundary
Nexon Korea confirms regional pre-registration, not global release timing
Nexon Korea's official Azur Promilia page can support Korea-region pre-registration and store-link statements. GameMeca's August 11, 2026 report can support a reliable-report note that Nexon opened pre-registration and described milestone campaign rewards.
Those sources should not be reused as a global release date, global beta date, global launch reward list, active redeem-code list, or final worldwide store timing unless a global-facing official source confirms the same claim.
Regional store boundary
JP App Store and Google Play entries confirm Japan-region pre-registration, not global release timing
The official JP pre-registration page can support statements that Japan-region users have App Store and Google Play pre-registration entries. The JP App Store expected date should stay labeled as regional store wording, and Denfaminicogamer's August 25, 2026 coverage should be used as official-linked media context because it also notes that the release date will be announced later.
The 20 million global pre-registration milestone can be cited as a campaign milestone when linked to the JP official coverage, but it should not be rewritten as an active redeem code, a final launch reward list, or a global release countdown.
Regional store boundary
China App Store dates stay regional until a launch announcement confirms them
The China App Store page can support China-region iOS/iPadOS pre-order availability, provider, compatibility, language, and store-listed expected-date statements. It should not be reused as a confirmed global release date, global beta date, worldwide platform schedule, or launch countdown.
TapTap's official app page can support China-region Journey Test history and current app-page platform context. TapTap character or Kibo posts should remain regional official-community notes unless global-facing official pages confirm the same names and profile details.
Official update boundary
JP improvement-policy posts are development context, not dates
The official JP X account can support statements that the team published improvement and update priorities toward official release, such as controller-operation optimization and system/content revisions. That wording should not be reused as a release date, launch window, platform schedule, or global beta confirmation.
Community watch boundary
Keep Reddit, Bilibili World, and milestone chatter in the watch lane
Community posts about JP CBT, CN CBT, Korea pre-registration milestones, Bilibili World footage, App Store date screenshots, or new character/gameplay details can help decide what to monitor next. They should not be promoted to official beta, release, platform, countdown, 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.
Regional community boundary
TapTap official posts and Biligame wiki rows need separate labels
The official TapTap community topic can support regional Journey Test notes when the post comes from the official Azur Promilia community account or official forum area. These posts are still regional context and should not become global release, global beta, final gameplay claims, or a global launch database.
Biligame wiki pages can help cross-check Kibo names and list coverage, but they remain community reference material unless the same name, artwork, type, or gameplay field is also visible in official material.
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 correctionCompliance pages
Public trust pages
Before monetization or analytics are added, visitors should be able to review the site disclaimer, privacy policy, and contact policy.