Privacy Notice

What we collect

For accounts, MangaMazing stores your email, optional display name, salted password hash, terms acceptance time, session-token hash, subscription status, and Stripe customer/subscription identifiers. We do not store your raw password or full card details.

Why we use it

We use this data to authenticate you, protect the service, provide membership access, process billing status, support account requests, and meet legal obligations. Manga reading and conversion jobs keep their existing browser-scoped isolation.

Cookies and security

The account session uses a Secure, HttpOnly, SameSite cookie. Only a one-way hash of its random token is stored. Transport uses HTTPS. No system can promise absolute security, but payment data remains with Stripe.

Engaged-use metrics

First-party metrics count visible, engaged use after 30 seconds of recent interaction or advancing native playback, not page loads. Signed accounts are deduplicated across browsers; anonymous browser sessions are reported separately and do not identify unique people. Only a keyed pseudonymous identifier, account/browser category, broad activity area and last-signal time are retained for up to eight days. Analytics do not store titles, URLs, emails, IP addresses or device fingerprints and are not sent to third-party analytics providers. The owner sees aggregate counts; the owner’s activity is excluded.

You can disable these metrics in Settings → Usage privacy. Do Not Track and Global Privacy Control are respected. Opting out stops new signals; existing pseudonymous activity expires within eight days. Browser-scoped history and jobs are separate from these metrics.

Processors and external links

Stripe processes subscription payments under its own privacy notice. Catalog pages may link to MyAnimeList, JustWatch, Internet Archive, or future licensed providers; those services receive data only when you choose to visit them.

Retention and your choices

We retain account and billing records while your account exists and as required for security, tax, dispute, and legal purposes. You may request access, correction, or deletion. Active subscriptions must be cancelled before final account deletion so billing is not orphaned.

Contact

For privacy or account requests, contact the project owner through the GitHub profile. We may ask you to verify account ownership before acting.