Library Cleaner

Privacy Policy

This policy explains what information Library Cleaner handles, how that information is used, where it is stored, and the parties with whom it is shared.

Effective and last updated: July 28, 2026

Overview

Winnipeg Wide Web is the developer and publisher of Library Cleaner. Library Cleaner handles only the information required to perform the cleanup that the user explicitly starts. We do not sell user information, use it for advertising, or operate a data-broker service.

Chrome Web Store Limited Use: Library Cleaner’s use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Single purpose

Library Cleaner helps a user delete files from the ChatGPT Library in large groups, continue the cleanup across page reloads, and display progress and deletion totals.

The extension operates only on https://chatgpt.com/library. It does not intentionally read ChatGPT conversations or access other websites.

Library Cleaner is an independent utility and is not affiliated with, endorsed by, or produced by OpenAI. “ChatGPT” and related marks belong to their respective owner.

Information Library Cleaner handles

ChatGPT Library page content and file identifiers

Library Cleaner reads the file entries and internal file identifiers exposed on the ChatGPT Library page. It uses these identifiers to locate the files included in the cleanup and prepare the deletion requests requested by the user. The extension does not send the contents of the user’s files to Winnipeg Wide Web.

Authentication-related request information

After the user starts a cleanup, Library Cleaner performs one deletion through the normal ChatGPT interface and temporarily observes the associated deletion request. It stores a local request template that may include the request URL, HTTP method, request headers, request body, and calibration-file identifier. Depending on how ChatGPT structures the request, the template may contain authentication-related information used by ChatGPT to authorize deletion.

Library Cleaner does not ask for, collect, or know the user’s ChatGPT password. It uses the user’s existing signed-in browser session and sends deletion requests only to ChatGPT.

Local cleanup progress

Library Cleaner stores whether a cleanup is active, the total and current-run deletion counts, completed cycles, recent group counts, no-progress attempts, and the run start time. This allows the cleanup to resume after the Library page reloads and allows the extension to display accurate progress.

How information is collected

The information is handled by code included in the extension package while the user is on the exact ChatGPT Library page and after the user explicitly starts the cleanup. Library Cleaner does not load or execute remote JavaScript or WebAssembly.

How Library Cleaner uses information

  • To identify files available in the currently loaded Library group.
  • To learn the current ChatGPT deletion-request format.
  • To submit the deletion requests explicitly requested by the user.
  • To retry temporary failures or rate limits.
  • To reload the Library and continue with the next available group.
  • To show progress, totals, runtime, and cleanup status.
  • To stop the process when the user presses Stop or leaves the Library page.

Sharing and transfers

OpenAI/ChatGPT: File identifiers and deletion-request information are sent to ChatGPT at chatgpt.com because this communication is necessary to perform the deletion requested by the user.

Winnipeg Wide Web: Library Cleaner does not send Library file identifiers, deletion-request templates, authentication-related request information, progress counters, or file contents to Winnipeg Wide Web or any developer-operated server.

Other parties: We do not sell, rent, or share extension-handled information with advertisers, data brokers, analytics providers, or other third parties. Information may be disclosed only if legally required or necessary to investigate security abuse, consistent with applicable law.

Storage, retention, and security

Library Cleaner stores its progress state and deletion-request template in chrome.storage.local on the user’s device. Progress information remains until it is reset, overwritten by another run, removed when the extension is uninstalled, or cleared through browser controls.

The request template remains locally until it is overwritten by a new cleanup, removed after certain authorization or request failures, cleared through browser controls, or removed when the extension is uninstalled.

Library Cleaner communicates with ChatGPT using HTTPS. No security method can guarantee absolute protection, so users should keep their browser and operating system updated and should not install modified copies from untrusted sources.

Your choices and controls

  • Cleanup does not start until the user presses Start and enters the displayed confirmation phrase.
  • The user may press Stop to end the active cleanup and abort active requests.
  • The user may reset the displayed deletion total while no cleanup is running.
  • The user may clear extension storage through Chrome or uninstall the extension to remove locally stored extension data.
  • The user may avoid all extension data handling by not starting a cleanup or by uninstalling Library Cleaner.

Changes to this policy

We may update this policy when Library Cleaner, applicable laws, or platform requirements change. Material changes will be reflected on this page with a revised effective date. If an extension update introduces materially different data practices, those changes will also be disclosed through the extension or its store listing as required.

Contact

Questions about this policy or Library Cleaner can be sent to [email protected].