We keep support simple and public: everything runs through GitHub Issues, where reports are visible, searchable, and answered in the open.
If a scan fails, a result looks wrong, or a page misbehaves, open an issue in our GitHub repository with the public @username you scanned (if relevant), the page you were on, and what you expected versus what happened. Screenshots help. Most tool-side issues can be reproduced and fixed within a day because every result carries its coverage and timestamp metadata.
We do not publish a support email. Public issues keep answers reusable: when one person reports a provider hiccup, everyone sees the status.
Questions about how results are computed — coverage, partial scans, why follower counts and fetched lists differ — are answered in each tool page's FAQ section. If something there is wrong or unclear, file an issue quoting the FAQ line and we will correct the documentation or the behavior, whichever is at fault.
For account owners: if you are the owner of a public account listed in a result and have concerns, note that we only process information Instagram already publishes to everyone. You can switch your account to private at any time and it immediately stops being scannable by this or any similar tool.
The roadmap is deliberately small until the MVP proves itself in search: the nine current tools cover the unfollow/follower relationship questions with real search demand. Requests that fit that scope — better filtering, exports, more history — are welcome as GitHub issues with a short use-case description.
Requests that do not fit — private-account scanning, story viewing, downloading, anything requiring an Instagram login — will be closed as out of scope by design.
· Reviewed by the Instagram Unfollow Tracker team
Instagram Unfollow Tracker