Effective 2026-10-16. This notice covers the personal Ninja Blazing Wiki fan project, maintained by an individual fan in Missouri, United States. The dedicated contact below handles privacy and support requests.
Read without an account
You can read guides, browse the character reference and use the planner without registering. We do not run advertising scripts, behavioral analytics, third-party video embeds or an automated Discord feed on this edition of the site. Our hosting provider necessarily processes requests, including network and technical information used to deliver and secure the website.
Account information
Firebase Authentication processes your email address, chosen display name, account identifier, authentication provider, verification status and sign-in metadata. For email/password accounts, Firebase handles password authentication; this site's operator does not receive your readable password. Google sign-in provides the account information needed for authentication. We do not request access to your Gmail messages, contacts, Drive files or game account.
We use this information to provide sign-in, profile management, account recovery and security. Authorized operator access and Google's processing support those functions. See Firebase privacy information and Google's Privacy Policy.
Browser storage
Firebase uses browser storage to maintain your sign-in session. Planner drafts stay in storage in the browser where you save them. A shared team URL contains the selected character identifiers; anyone with that link can read that lineup. A temporary account notice may be held in session storage. We do not store your date of birth; the registration eligibility control checks your choice in the page.
Support correspondence
If you email us, our dedicated Gmail inbox processes your email address, message, attachments and related email metadata. We use this information to answer the request, investigate corrections or rights concerns, and maintain necessary records. Google provides the email service. Please send only relevant details and avoid passwords, identity documents, payment-card numbers or unrelated personal information.
We retain correspondence for as long as needed to resolve the request and any follow-up, security, legal or recordkeeping obligation. Routine resolved messages should be removed when no longer needed. A limited record of a rights complaint or privacy request may need to be retained to document its handling. You can ask about retention or request deletion through our privacy request process.
Security
The website uses HTTPS in transit, and Firebase handles account authentication. Administrative access is separate from public website access. We do not put private identity documents, payout details or payment-provider secret keys in website code. No internet service can promise perfect security; contact us if you suspect an exposed account or record.
Retention, export and deletion
Your authentication record remains while your account exists. In My account, you can export the profile and metadata available to the site, update your display name, sign out or delete the Firebase authentication account after confirming your identity. Deletion removes that authentication record; it does not promise immediate removal from every provider log, backup or record retained for security or a legal obligation. Provider retention follows its applicable policies. Clear browser drafts separately on each device.
Payments
We currently accept no payments through this site. Stripe is the intended processor for future optional support. Before checkout opens, we will publish the actual offer and explain billing information, disclosures, retention and cancellation. The draft supporter terms do not start a payment or authorize disclosure of your billing information. No payment-card or bank-detail form is embedded here.
Children and eligibility
New wiki accounts are intended for adults aged 18 or older. Reading does not require an account. We do not knowingly collect children's personal information for account registration. Existing account holders can access deletion controls regardless of age. If we learn that an account was created by a child, we will address the information and any applicable parental rights. An age question does not by itself settle every children's-privacy obligation.
Sharing, choices and requests
We do not sell personal information or share it for cross-context behavioral advertising. Because those activities are absent, browser Do Not Track and Global Privacy Control signals do not trigger a separate advertising setting. This does not disable essential hosting or authentication. External links lead to services with their own privacy practices and may process data outside your region.
Contact blazingmechanicsdesk@gmail.com for site support, privacy questions, corrections and copyright concerns.
Depending on applicable law, you may have access, correction, deletion or other privacy rights. The privacy request page explains how to exercise them, request reconsideration or ask for help. Requests may require proportionate identity verification. Do not send sensitive identity documents through an ordinary support email unless a secure, necessary verification method has been agreed.
Changes
We will update this page's effective date when its substance changes. A material change to a future paid service will also be communicated through that service's appropriate channel before it takes effect where required.