DAWNBLOOM / TRANSPARENCY
Transparency Report
We publish reviewed aggregate information where disclosure is legally permitted. No person, request subject, or case detail is identified.
REPORT SCOPE
Scope and status
Transparency reporting starts on October 1, 2026.
Initial period: October 1–December 31, 2026. We plan to report every six months thereafter.
Only human-reviewed aggregate data marked PUBLISHED appears here. Draft entries are never published automatically.
01 / REQUESTS
Government and judicial requests
Formal requests for user data are counted only where disclosure is legally permitted.
| Government and judicial requests | Reviewed count |
|---|---|
| User-data requests received | Complete data not yet available |
| Accounts affected | Complete data not yet available |
| Full responses | Complete data not yet available |
| Partial responses | Complete data not yet available |
| No data provided, rejected, or unavailable | Complete data not yet available |
02 / CONTENT
Content removal and restriction
Covers the website, DAWNBLOOM Community, player community, and official content platforms. Ordinary community reports are not counted as copyright claims.
| Content removal and restriction | Reviewed count |
|---|---|
| Government or judicial content requests | Complete data not yet available |
| Copyright complaints | Complete data not yet available |
| Trademark complaints | Complete data not yet available |
| Personal-privacy requests | Complete data not yet available |
| Community-rule reports | Complete data not yet available |
| Items affected | Complete data not yet available |
| Removed or restricted | Complete data not yet available |
| No action taken | Complete data not yet available |
03 / IP
Intellectual property
Copyright, trademark, piracy, and impersonation reports are tracked separately from valid notices and final actions.
| Intellectual property | Reviewed count |
|---|---|
| Copyright complaints | Complete data not yet available |
| Trademark complaints | Complete data not yet available |
| Piracy or impersonation reports | Complete data not yet available |
| Valid rights-holder notices | Complete data not yet available |
| Final actions taken | Complete data not yet available |
04 / SECURITY
Security incidents
Only confirmed incidents meeting a major-impact threshold are counted. Future incident entries will state occurrence, discovery, remediation dates, scope, and response without exploitable vulnerability details.
| Security incidents | Reviewed count |
|---|---|
| Major personal-data breaches | Complete data not yet available |
| Major account-database incidents | Complete data not yet available |
| Browser signing-key incidents | Complete data not yet available |
| Software-download supply-chain incidents | Complete data not yet available |
| Major service-security incidents | Complete data not yet available |
05 / RELIABILITY
Service reliability
A major outage lasts over 30 minutes and affects a significant share of normal users.
| Service reliability | Reviewed count |
|---|---|
| Major game-website outages | Complete data not yet available |
| Major account-service outages | Complete data not yet available |
| Major browser-download outages | Complete data not yet available |
| Major server incidents | Complete data not yet available |
06 / PRIVACY
Privacy practices
DAWNBLOOM Browser has different data flows from game and account services. These statements describe the browser itself, not every third-party website or component.
| Privacy practices | Reviewed count |
|---|---|
| Browse without an account | Yes |
| Light sync for bookmarks and a few preferences | Your choice |
| Browsing history used for ad profiling | Not used |
| Anonymous aggregate product statistics | No URLs or account IDs |
| Ads operated by the browser | None |
Functional third-party components such as ML Kit may process necessary diagnostic information; anonymous product statistics contain no browsing content. See the Privacy Policy for details. Privacy Policy
07 / METHODOLOGY · V1.0
Methodology and definitions
- Collection begins October 1, 2026; the initial period ends December 31, 2026. Natural half-year reporting is planned thereafter. No unreviewed numbers are published before the first period closes.
- A request is one formally received record. Repeat submissions on the same matter are linked to that record; multiple affected accounts or items are counted separately.
- Content removal includes deletion or restriction of public visibility. Reports received without action are counted separately.
- A major security incident is a confirmed event with material impact on personal data, account databases, signing keys, download supply chains, or core services.
- A major service outage lasts more than 30 minutes and affects a significant share of normal users. Brief individual connection failures are excluded.
- Potential sources include manual legal-request logs, support records, IP case records, security incident records, and reviewed admin aggregates. Raw records, account identifiers, IPs, emails, and internal interfaces are not published.
- Legal confidentiality, privacy, investigations, or limits in the data systems may prevent disclosure of some details or categories. We will describe such limits. Zero would mean no qualifying event was recorded in that period, not that one can never occur.