Tinder Cleanup
Client
Self
Tools
TypeScript, Vue 3, Quasar, Vite, Chrome Manifest V3
URLs
Project Description
I had been frustrated for a long time by how difficult Tinder makes it to manage your matches. There is no way to bulk-manage them. Unmatching a single person requires finding the match in the list, opening the conversation, clicking the unmatch button, then clicking again to confirm. And this needs to be repeated for what are often very long lists of profiles to unmatch. One morning I got so fed up with it that I decided to do something about it.
I'm sure Tinder has its reasons for not making this easier (like padding the perceived number of available matches) but it just invites frustration. I built Tinder Cleanup initially for my own use, but quickly realised it would probably be useful for others too.
The extension lets users define filter rules (match age, inactivity, unanswered messages, empty conversations) and unmatch in bulk. It runs as a side panel alongside tinder.com, passively reading match data from Tinder's own API responses. No scraping, no additional API calls.
Key design decisions
- Preview-first workflow: nothing is changed until the user has reviewed the list and selects which profiles to unmatch
- Privacy by default: all data stays in the browser via chrome.storage.local; nothing is sent to any external server
- Non-invasive architecture: the extension intercepts Tinder's existing network responses rather than making its own API calls, and staggers unmatch actions with configurable delays to mimic natural usage