The man behind the articles
Our blog articles are written by Evripides Kyriakou, Researcher & Editor @ Suprascribe.
Everything published on the blog is written from working on the product itself - reading how real billing emails are structured, how providers word renewal notices, and where automatic detection succeeds or fails. Where a guide describes a limitation of Suprascribe, that limitation is real and stated rather than omitted. Cancellation steps are walked through on the actual provider before they are published, and corrected when a company quietly moves the button. Nothing here is written to fill a keyword slot - each piece answers a question that came up while building or using the thing.
The articles keep returning to the same three things, because they are the reasons this product exists at all. Every one of them comes down to information being power: the subscription economy runs on you not knowing what you pay, not knowing what is collected, and not knowing where the exit is - so writing it down plainly moves that power back to the person paying.
Freedom - a subscription is easy to start and deliberately hard to leave. Cancellation is buried behind support chats, retention offers, and settings pages that move. The how-to-cancel guides exist to hand that back: know what you pay for, know exactly where the cancel button is, and leave when you decide to rather than when the friction finally wears off.
Privacy - the standard way to find your subscriptions is to hand a company read access to your entire bank history. That trade is presented as the only option, and it is not. Writing about email-based detection, data minimisation, and what these apps actually collect is a way of showing that the convenient answer and the invasive one are not the same answer.
Transparency - privacy claims are marketing copy until someone can check them. That applies to the tools reviewed here and to Suprascribe itself, which is why the comparisons name what competitors do well, why the pricing is stated in full, and why the code is open.
The source code is public on our Github repository, so any claim made here about how email scanning works can be checked against the code that does it.