Privacy Policy

Account information. When you register with an email and password, we store your email address, display name, an account identifier, and a password hash. We also keep your email verification status, sign-in method, account status, and account creation, update, and last sign-in times. Your password is checked using its hash rather than stored as readable text.

Email verification. We send a verification code to the address you provide. Verification records include a protected hash of the code, its expiry, attempts, sending times, and whether the challenge has been used or invalidated. An email registration does not provide an authenticated session until verification succeeds.

Google sign-in. When Google sign-in is available and you choose it, we request basic sign-in information through Google’s OpenID, email, and profile permissions. We use your Google account identifier, email address and verified status, and, where supplied, your name and profile picture URL to create or identify your MangaVerse account and display your profile. These permissions do not request access to Gmail messages, Drive files, or contacts.

Session and security information. We keep session identifiers, hashed refresh credentials, and session creation, expiry, last-use, and revocation times. We use your network address and email address for abuse prevention, with hashed identifiers and counters used for sign-in and verification rate limits. The service also processes operational information such as request outcomes, access decisions, processing failures, and resource identifiers to maintain and protect the application.

MangaVerse stores files you upload and associated information such as file name, format, size, checksum, ownership, book title, and language choices. Processing can produce extracted page images, detected text regions, recognized text, translation context, translated text, cleaned images, and localized page renders. These materials and processing records are stored so the service can display your library, continue processing, and let you read and edit the result.

Optical character recognition (OCR), text-region detection, and image cleaning run in the application’s processing infrastructure. For AI translation, extracted text and relevant context, such as nearby dialogue, glossary terms, language settings, and region identifiers, are sent to the translation services described below. The application also records model usage, timing, errors, and cost information associated with processing.

Any personal information present in your uploads or extracted text can be included in this processing. Upload only material you are authorized to share and process, and avoid including unnecessary personal or confidential information.

We use information to create and authenticate accounts, verify email ownership, maintain sessions, associate books with their owners, store and localize uploaded material, save edits and reading preferences, and deliver the reader and library features you request.

We also use operational and security information to diagnose failures, manage processing limits, prevent unauthorized access and abuse, and respond to inquiries or applicable legal requirements. Where a legal basis for processing is required, it depends on the activity and applicable law, including providing the requested service, protecting its security, meeting legal obligations, or obtaining consent where required.

Hosting and storage. MangaVerse’s deployed infrastructure uses Amazon Web Services (AWS) for hosting. Account and processing records are stored in databases, and uploaded and processed files are held in object storage operated as part of the service.

Email delivery. Verification emails are delivered through Amazon Simple Email Service (SES). Email delivery involves providing the recipient address and verification message to the delivery service.

AI translation. The translation integration uses Google Gemini and Groq, including fallback processing when a translation request cannot be completed by the first service. Extracted text and translation context can therefore be processed by either provider. Routing software within MangaVerse coordinates these requests. A provider’s handling of information is also subject to the terms and privacy practices applicable to that provider’s service.

Google authentication. If you choose Google sign-in when it is enabled, Google handles the Google authentication step and supplies the basic account information described above. Google’s own privacy policy applies to your use of Google.

Information may be handled in countries other than the one where you live, depending on hosting and provider operations. We may also disclose information where required by applicable law or where reasonably necessary to investigate misuse or protect users’ rights and the security of the service. This policy does not promise that external providers never retain submitted data.

We use authentication and refresh cookies to maintain your session. Temporary cookies support the Google sign-in flow when you use it. These technologies serve sign-in and security purposes. Blocking or clearing them can prevent sign-in or end your session.

Browser local storage remembers preferences such as theme, language, reader settings, and background intensity. It can also hold account-associated reading progress, a recent book reference, and text edits. Account-associated reading state is cleared when the active account changes or you sign out. You can clear browser storage through your browser settings; doing so does not erase files or account records stored by MangaVerse.

First-party visit counting uses a random session key in browser storage. A new visit starts after 30 minutes without activity. The counting database stores only a daily one-way session hash and date, without account identifiers, page addresses, or IP addresses. The dashboard shows measured sessions rather than individual people; blocked scripts and browsers requesting Do Not Track or Global Privacy Control are not counted. Older counting keys are pruned during normal collection. Admin pages are excluded.

Account information, uploaded files, processing artifacts, and saved results are retained to support the service. There is currently no published fixed retention period covering all of these records. Session and verification credentials have expiry controls, but expiry does not mean every associated database record is erased.

Deleting a book from your library marks it as deleted and removes it from normal library access. This action does not itself confirm permanent erasure of original files, generated artifacts, or related records. Signing out revokes your current session; it does not delete your account or books.

There is currently no self-service account deletion feature. Requests concerning account or data deletion require individual handling. Any retention required by applicable law or necessary to address a security incident or dispute may affect what can be removed. We do not promise an automatic purge or a specific deletion deadline that the service does not currently provide.

The public service uses HTTPS, protected authentication cookies, password hashing, expiring verification challenges, and checks intended to restrict access to the account that owns a resource. Rate limits and session revocation help protect against misuse. These measures reduce risk, but no internet service can guarantee absolute security.

Keep your credentials private, protect access to your email account, and sign out on shared devices. Do not send passwords or verification codes in a privacy inquiry.

You can choose whether to upload material, manage browser storage and preferences, sign out, and remove books from your library as described above.

Depending on the law that applies to you, you may have rights to request access to, correction of, or deletion of personal information; request a portable copy; object to or restrict certain processing; or withdraw consent where processing relies on consent. These rights depend on the circumstances and may be subject to exceptions. You may also be entitled to raise a concern with the relevant data protection authority.

For an inquiry, identify the account or material concerned and explain your request. We may need information to verify that you are entitled to make the request, and will address requests in accordance with applicable law.

We may update this policy as the service or applicable requirements change. The current version will appear on this page with its last-updated date. Where applicable law requires additional notice or consent for a change, we will follow that requirement. Our Terms of Service explain the conditions for using MangaVerse.

For privacy questions, account or data deletion requests, and other legal inquiries about MangaVerse, email alijontoshbul@gmail.com. Include enough information to identify your account and explain your request. Do not include your password or verification codes.