QuiteInbox

QuiteInbox

Take back control of your inbox

146 followers

Unsubscribe from unwanted emails in seconds. No servers. No tracking. Everything happens locally in your browser. 100% free and open source.
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
QuiteInbox gallery image
Free
Launch Team
Unblocked AI Code Review
Unblocked AI Code Review
High-signal comments based on your team's context
Promoted

What do you think? …

Koushith B.R
I wanted to clean up my inbox, unsubscribe from dozens of newsletters but every “unsubscribe tool” I found wanted full read/write access to my entire Gmail inbox… on their servers. As a dev, that was a hard no. I don’t want a random SaaS scraping my mail, storing it, “anonymizing” it, monetizing it, or getting breached someday. So I built a tool that does the opposite: ✅ Runs 100% locally in your browser ✅ No backend, no database, no tracking, no analytics ✅ Your emails never leave your device ✅ Free + open source (MIT) It just uses the official Gmail API in your session, unsubscribes, and exits. That’s it. I made it for myself then realized everyone has this problem, so I open-sourced it. ⚠️ Google will show an “unverified app” screen (because there’s no company behind it and I don’t send data to a server). You can safely continue or clone the repo and use your own keys if you’re extra cautious. Repo: https://github.com/Koushith/quit... Would love feedback, PRs, issues, ideas, anything 🚀
Sanskar Yadav

Congrats on launching QuiteInbox! Love the focus on privacy with local processing and open source approach.

What made you decide to go the completely local route instead of offering a cloud option for syncing across devices?

Koushith B.R

@sanskarix Thanks so much! 🙌

I went fully local for a simple reason: I wanted something I could trust with my inbox and for me, that meant no servers, no accounts, no data leaving my machine. I originally built this just to fix my own inbox mess, and the idea of routing emails through a cloud service felt like recreating the same privacy problem I was trying to escape.

Cloud sync could happen later, but only if it can be done in a way that keeps the same guarantees (maybe via optional, encrypted self-hosted sync). For now, local-only keeps the code, the privacy model, and the trust story very clean.

If you have thoughts or a use-case where sync matters, feel free to open an issue on GitHub. I’m building this solo, so real-world input helps a ton! 🚀

Viktor Shumylo

Congrats on the launch! Does it work with Gmail only for now, or are there plans to support Outlook or ProtonMail later on?

Koushith B.R

@vik_sh Thank you so much. yes, i do have a plan to extend for other mail providers. will spend some time on coming weekend. feel free to open any issues/ feature requests on github.

https://github.com/Koushith/quite-inbox

Lilou Lane

Love that you built this out of personal frustration — and the fact it’s open-source and local makes it even better. Refreshing to see privacy-first tools done right 👏

Alexandru Rada

congrats for launching? Why would one use quiteinbox instead of default unsubscription provided by gmail?


Or other tools like actordo.com / clean.email foxclean and other doing similar?

Ian Corvin

Really wanted to use, but this threw me off course. Can you fix this first please? Not giving it access to my data unless it at least looks secure:

Savvas Konsta

Like this product!