Privacy Policy
How Hajima AI handles the limited data needed for manga reading and reader accounts.
Data we collect
Anonymous manga browsing does not require an account. If you sign in, we may store your email, profile identifier, favorites, latest visible manga page, reading timestamps, session data, and necessary security logs.
How we use data
We use this data to authenticate you, synchronize favorites and reading history, operate the site, prevent abuse, answer support requests, and maintain service reliability.
Storage and sharing
Service providers may process data only to host, authenticate, deliver assets, monitor reliability, or provide support. We do not sell reader profile data.
Two-step hiding and retention
Step 1 hides generation inputs and outputs while keeping usage and billing summaries visible. A separately confirmed step 2 also hides those summaries. Account closure applies the same two steps and revokes normal sessions. These actions hide records; they do not physically erase database records or private files. Ordinary hiding has no scheduled cleanup. Records are retained for recovery, fulfilment, accounting, security and disputes while those purposes remain necessary. Lawful data requests are reviewed separately; unnecessary data is erased or de-identified as required by applicable law.
Email processing · version 2026-10-04.v3
Resend continues to deliver verification codes. YNOT Mail processes recipient email, selected language, subscription proof and delivery status for lifecycle messages. Emails do not include private generated media, prompts or wallet data. Optional marketing is separate from essential order notices. Manage language and consent in Billing; unsubscribe links work without signing in and require confirmation. We retain consent and suppression evidence to honor your choices.
Code verification and transaction evidence
When a supported code is used, its issuer and participating service exchange only the code's stable identifier, payment environment, product face value, financial status, redemption facts and minimal fulfilment summaries, including usage, cost status and amounts. This code-level information is pseudonymous, not guaranteed anonymous. Account identities, emails, devices, prompts, input files, outputs and original media URLs are not exchanged through this mechanism. The payment merchant shown at checkout handles payment, refunds and disputes. Unknown or blocked financial status prevents new redemption and consumption; locally authorized history remains readable.
Original-owner recovery
A code locates records; it alone does not authorize private content access. Recovery requires the original account identity or verified original payment-email authority. Each step is explicitly confirmed in reverse order, 2 to 1 to 0. Restoring an account does not restore independently hidden records. Recovery, replacement codes and resending never issue benefits again or reset balances, billing or expiry. Missing or lawfully erased files cannot be restored. Authorized staff may retain and export minimal transaction and fulfilment evidence without prompts or works.
Automatic purchases and activation
Before paying, choose your plan and explicitly confirm automatic activation. The confirmed plan, price and consent are frozen. After trusted payment confirmation, the purchased code is unlocked and its validity starts, and your local plan is issued once. A shared private transaction store holds random order identifiers, product face value, payment environment, financial status and minimal fulfilment evidence. Account identity, email, device data, prompts, input media, outputs and original media URLs remain separate. A return page or closed tab does not prove payment. Keep uncertain payments pending for verification rather than paying again. Recover these orders through the original initiating account; a code alone never authorizes private content.