Last updated: October 17, 2026
Inbox Cleaner has several separate surfaces. The Chrome extension works inside an already-open Gmail tab. The optional legacy browser app on this website uses Google OAuth and Gmail API. The local planning tools and waitlist have the distinct behavior described below. A statement about the extension’s data path does not mean this website makes no network requests.
The packaged extension reads sender names, sender email addresses and displayed dates from Gmail’s rendered conversation rows. It also reads category and result-count information to build the sender view. It does not request message bodies, subject lines or attachments. Gmail’s own interface can contain other information; the extension’s current source is designed to use the rendered metadata needed for its cleanup purpose.
The extension has no OAuth sign-in, Gmail API client, model API or independent network client. You must already be signed into Gmail in an open tab. It navigates Gmail and uses Gmail’s own controls, so Gmail itself continues communicating with Google. The developer does not receive your mailbox data through the extension.
Scan results are cached on your device in chrome.storage.local under inboxCleanerData, including sender information, counts, categories and scan timing. Clear the extension’s local storage or remove the extension to remove its local cache. Removing the extension does not reverse changes already made in Gmail.
Declared permissions are storage for the local cache, tabs to locate and communicate with your Gmail tab, and host access to https://mail.google.com/* for the content script. These permissions do not make the legacy website OAuth flow part of the extension.
You choose senders and confirm before the extension drives Gmail’s move-to-Trash action. Sender-wide cleanup can include archived mail and does not inherit age, size, category or starred exclusions from a separate search. The extension does not unsubscribe you or permanently empty Trash. Gmail normally allows recovery for up to 30 days unless mail is permanently removed sooner.
The website’s separate Connect Gmail flow uses Google OAuth and requests the Gmail read-only and modify scopes. Its browser code lists messages and requests From and Date headers plus label IDs. It uses those results to build sender counts and category information, and sends user-confirmed move-to-Trash requests to Google’s Gmail API. The requests cross the network to Google; this is different from the extension’s DOM automation.
The browser app caches sender results locally in localStorage under inboxCleanerData. Its OAuth access token is held in running-page memory in the current source. Signing out clears the local result cache and requests token revocation. You can also clear this website’s browser data or revoke the app’s Google-account access through Google account permissions. Revocation does not undo completed Gmail actions.
The application code does not upload mailbox results to a developer server, and the current metadata requests do not request bodies, subjects, recipients or attachment contents. The declared OAuth scopes grant broader access than those metadata fields, so review Google’s consent screen before connecting. This policy describes the code path; it does not certify a live OAuth deployment or every installed package version.
The Gmail search builder and storage troubleshooter use information you enter into their pages. They do not authenticate to Google, inspect your mailbox or delete email. When you choose an Open Gmail link, your browser sends the resulting search query to Gmail. Avoid entering sensitive content in a search you do not want sent to Google.
Loading this website contacts its hosting provider. Pages may load fonts from Google Fonts and the homepage loads Google’s sign-in library for the optional browser app. Those services receive normal web requests, which can include network and browser information. No claim that the whole website is offline or free of third-party requests is made.
If you submit the waitlist form, the homepage sends the email address you enter to a Google Apps Script endpoint for the waitlist. This is an explicit network submission and is separate from mailbox metadata. The repository does not establish the endpoint’s server-side retention schedule; no automatic deletion period is promised here. Contact us to ask about removal of a waitlist entry.
The extension and browser app are designed to process mailbox results locally and do not include a mailbox-data sale or sharing workflow. Google receives the Gmail actions or API requests described above. The waitlist address is submitted separately to its Google-hosted endpoint. Local caches remain until cleared through the applicable surface or browser controls. Organization retention policies can apply to work accounts independently of these controls.
For privacy questions or a waitlist-removal request, email pushpendra.singh@freed.care.