MangaGlow Overlay does not send data to its developer, sell data, use analytics, or operate a data-collection server. Its automatic official-release feature does transmit the visible series title to the public MangaUpdates API as described below.


MangaGlow Overlay handles two Chrome Web Store disclosure categories solely to provide its user-facing interface features:

• Website content: Manga titles, links, images, public uploader-profile references, reading-status information, and other content already displayed on supported MangaGo pages are processed in the browser to modernize layouts, provide navigation and organization controls, label configured public uploaders, and locate relevant official-release information.
• Personal communications: Public MangaGo topics, comments, and replies are processed temporarily in the open tab to provide discussion layout, search, filtering, reply, spoiler, emoji, GIF, and media-preview tools. MangaGlow Overlay does not access MangaGo private messages, save fetched comment text, or send comment text to the developer, MangaUpdates, GifSnap, or Openverse.

MangaGlow Overlay does not collect personally identifiable information, health information, financial or payment information, authentication information, location, browser history, or behavioral activity logs. It does not log clicks, pointer movement, scrolling, or keystrokes. Ordinary control events are handled only as needed to operate the interface selected by the user.

The extension reads MangaGo page content only inside the user's browser so it can adjust the page layout and provide local controls. When the user searches topics or comments, the extension requests the title's additional comments directly from MangaGo's existing same-origin comment endpoints, processes them temporarily in the open tab, and does not save the fetched comments. On a visit to the default or Update Date Yaoi catalog, the extension may request the public series page for each title visible on that exact page. It checks the first eight visible titles with up to eight concurrent requests, then uses up to six concurrent requests for the remaining titles, capped at 80 titles total. Up to eight small local snapshots store page keys, title slugs, newest-upload fingerprints, and configured uploader-filter or community-group identifiers so badges survive refreshes and page changes. Snapshots are retained only within the current MangaGo update-hour bucket and a page is rescanned when its visible title set changes; none of this data is sent to the developer. The optional Hide filter matches setting is off by default. When enabled, it may request only the next two same-origin Yaoi Update Date result pages and enough public series pages to refill the visible grid, capped at 48 visible titles and 96 total uploader checks. The scan stops when the grid is full, is reused from local caches when possible, and never runs on a timer or on unrelated pages. When the user starts or updates the full recent Yaoi view, the extension requests the user-configured 1-50 MangaGo Latest Updates pages. The first three are checked in order and deeper pages are requested in batches of no more than four; the scan still stops when a complete page is outside the selected window. It then checks up to 80 matching public series pages, four at a time, and applies configured matches from the newest dated uploader row regardless of displayed chapter number. A tied unmatched row suppresses a configured filter match, and only fully undated tables fall back to the highest displayed chapter. Opening the Community Translation Groups panel requests the two configured public MangaGo uploader pages and locally caches up to three recent links per group for one hour. These labels are local organizational heuristics that may be incomplete or incorrect and do not establish authorship, translation accuracy, quality, availability, legality, authorization, or rights status.

When linked image/GIF previews are enabled, the browser requests qualifying HTTPS media directly from the URL posted in a comment or entered into the reply editor. The media host can receive ordinary network information such as the user's IP address. MangaGlow Overlay sends no referrer with these requests and does not proxy, copy, analyze, or save the media bytes. Users can disable posted-media previews in the extension settings. The reply editor may locally remember up to 18 HTTPS image/GIF URLs the user selected so they can be reused from its GIF shelf; this bounded URL history never leaves browser extension storage and can be removed by clearing the extension's stored data.

When the user explicitly submits a GIF search, MangaGlow Overlay sends only that search phrase, the requested result page, and ordinary network metadata to GifSnap. Results are requested in pages of at most 24 and the picker displays no more than 100 sanitized HTTPS media URLs served by GifSnap or its exact current R2 media host in one search session. MangaGlow Overlay does not censor GifSnap queries or titles and does not describe GifSnap results as guaranteed family-safe. The user may separately choose a clearly labeled safer Openverse search, which requests at most 18 GIF records with mature results excluded and licenses limited to CC0 and the Public Domain Mark; Openverse is not contacted automatically or silently substituted. No MangaGo cookie, account identifier, comment text, or page URL is sent to either service. Sanitized result records are held only in a bounded in-memory cache for up to 15 minutes, and MangaGlow Overlay neither downloads nor stores the GIF bytes. These searches require the declared https://gifsnap.com/* and https://api.openverse.org/* host access and make no request merely because a MangaGo page or editor loaded.

Reading-status and vote requests are sent directly to MangaGo only after the user presses the relevant control. The extension locally remembers quick reading-status selections and votes that MangaGo accepted, including the vote totals returned with an accepted vote, so their visual state can survive a refresh. Settings—including the selected theme, uploader-filter display mode, and whether the Community series sidebar is open—muted terms, explicitly saved titles, statuses, accepted vote selections, returned totals, the bounded media-URL shelf, the bounded page-specific recent-title snapshots, and the community-group feed cache remain in browser extension storage and are not sent to the developer.

When a user opens a MangaGo series page, the Support the author panel sends up to eight visible primary or alternate series titles directly to api.mangaupdates.com using credential-free HTTPS requests. One declarative request rule, restricted to api.mangaupdates.com XMLHttpRequests, removes the Origin, Referer, and Cookie request headers. This prevents the MangaGo page URL, extension origin, and MangaGo account cookies from being transmitted to MangaUpdates and preserves the public API request format used by MangaGlow. The rule does not redirect requests, modify MangaGo traffic, affect advertisements, or operate on unrelated domains. MangaUpdates receives the title query and ordinary network information such as the user's IP address under its own policies. The extension accepts only a confident exact normalized title match, then may request that matched MangaUpdates series record and up to four creator records listed on it. This provides original purchase locations, official translations, publisher records, and available creator social or official-site links. If the API still rejects the request, the extension does not retry through another service and leaves the manual MangaUpdates search link available.

MangaUpdates results are stored only in browser extension storage: successful matches for up to 14 days and unsuccessful lookups for one day, capped at 250 entries. This cache reduces repeat API traffic. A manual MangaUpdates search link remains available when no confident match is found. All displayed third-party destinations must be HTTPS, and MangaGlow Overlay does not preload those purchase or creator websites.

MangaGlow Overlay has no analytics, advertising, developer-operated server, extension account system, or remote code. It does not access browser history, cookie values, passwords, private messages, or chapter image data. The browser may include the user's existing first-party MangaGo login session when it sends a user-requested action to MangaGo.


MangaGlow Overlay uses handled information only to provide or improve its clearly described, user-facing single purpose. It does not sell user data or transfer it outside the limited service interactions described in this policy. It does not use or transfer data for advertising, profiling, unrelated purposes, lending, or determining creditworthiness. The developer does not provide humans with access to user data. MangaGlow Overlay's handling of information follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Removing the extension removes its access. Browser extension data can also be cleared through the browser's extension settings.