I might be misinterpreting your question but I'll try to explain further, hopefully it makes sense:
So the way most email cleaning tools work is:
- Scan your emails for all your subscriptions - via Gmail API
- Each subscription has a link, that link is what is used to unsubscribe the link can either be in the email header or email body - This can be a POST request or a GET request, in some complex cases a mail send to unsubscribe
- With this link for each mailing list, mass unsubscription can happen
So the main difference here is, other tools do this on the third-party servers. InboxPurge does this on your browser/device (specifically the email scanning bit). Making HTTP requests to the Gmail API from your device.
Yes, it's also possible to build a browser extension that does this on a third-party server.
*Other things happen depending on the email cleaning tool but I've tried to simplify to explain better.
So the way most email cleaning tools work is:
- Scan your emails for all your subscriptions - via Gmail API - Each subscription has a link, that link is what is used to unsubscribe the link can either be in the email header or email body - This can be a POST request or a GET request, in some complex cases a mail send to unsubscribe - With this link for each mailing list, mass unsubscription can happen
So the main difference here is, other tools do this on the third-party servers. InboxPurge does this on your browser/device (specifically the email scanning bit). Making HTTP requests to the Gmail API from your device.
Yes, it's also possible to build a browser extension that does this on a third-party server.
*Other things happen depending on the email cleaning tool but I've tried to simplify to explain better.
Hope it was helpful.
You can find the list of browser permissions a Chrome extension can request for here: https://developer.chrome.com/docs/extensions/reference/manif...