NeatBox

A Gmail inbox cleaner — unsubscribe, delete, categorize, and optionally automate cleanup with recurring rules.

Last updated:

What NeatBox can access

NeatBox asks for three Gmail permissions, all used only for the features described in the extension itself:

• Read and modify mail (gmail.modify) — to find subscription senders, move messages to Trash, and restore them if you undo a deletion.
• Manage filters (gmail.settings.basic) — reserved for block-via-filter, and scoped so NeatBox only ever touches filters it created itself, never a filter you set up yourself.
• Your email address (userinfo.email) — to know which Google account is signed in, nothing more.

Where processing happens

All sorting, categorizing, and decision-making runs locally in your browser. Sender lists, categories, protected domains, and recurring rules live in your browser's own storage — either on your device, or synced through your own Google account via Chrome's built-in sync, the same way your bookmarks sync. That data never passes through a server we operate, because we don't operate one.

Your own Google API access

NeatBox doesn't use a shared Google API client. Each person sets up their own free Google Cloud project during a one-time setup step, and pastes their own credentials into the extension. This means:

• Your Google API credentials are stored only in your own browser, never sent anywhere.
• We have no server-side access to your Google account, your credentials, or your mail — there's no infrastructure on our end capable of holding any of it.
• This is also why NeatBox is distributed as a direct download rather than through the Chrome Web Store — it avoids a costly verification process that exists for apps operating a shared backend, which NeatBox deliberately doesn't have.

What we don't do

• No analytics, no tracking, no third-party scripts.
• No account, no sign-up, no data collected about you by us at all.
• NeatBox is free — there's no paid tier, no subscription, and nothing to buy.

The one exception: unsubscribing

When you unsubscribe from a sender, your browser sends a request directly to that sender's own unsubscribe service — the same request your browser would send if you clicked the link yourself. That request goes straight from your browser to them; it never passes through us either.

Removing your data

Uninstalling the extension removes everything NeatBox stored locally. To fully revoke access, also remove NeatBox's OAuth client from your Google Account's connected apps — since you created that OAuth client yourself, you're the one who controls and can delete it.

Questions