You look for a product. Your retriever finds the promo code and gives you back a share of the price. That is the whole idea.
Free. No card. The merchant pays us a commission, we split it with you. That is the whole model.
Wherever you ask, it goes and fetches:
Third-party marks named for identification only; no affiliation or endorsement.
A small card, only when there is a real deal. Dismiss it and it stays away. Illustration with example figures.
It reads the page on your device, and only there. It spots the product you are looking at. Nothing is sent anywhere.
It comes back with the promo code and the cashback. One small card, one click to activate. Not interested? Ignore it.
You buy like always, same site, same price or cheaper. Your share of the price comes back to your wallet.
Most cashback services hide this split. Here it is, in the open.
Illustrative figures. Real rates are shown per offer before you click, and recurring subscriptions turn into monthly cashback.
No hidden coupons, no cookies dropped behind your back, no tricks at checkout. You click, or nothing exists.
Detection runs on your device. Your conversations, your pages and your code are never sent to us. Ever.
Every line that runs on your machine is MIT-licensed open source. The client repository goes public at launch, so you can audit it before you trust it.
Coupon sites give you one of the two. Your retriever brings both, and they stack.
In Claude Code, VS Code and Cursor: cashback on the tools your project already uses, straight in your status bar. One command: npx retrievercash init.
It depends on what you adopt. Amounts are shown per offer before you click, and SaaS revenue-share programs turn into recurring monthly cashback. We publish no fantasy numbers.
Yes, and we say so. Cashback has always been affiliate commission shared with the buyer. The difference is who gets profiled (nobody: detection is local), how activation happens (only your click), and how much of the pipeline you can audit (all of the client).
Merchants have a validation window (typically 30 to 90 days) to account for refunds. Your entry shows the exact unlock date. We release money once the network confirms and pays.
Your cashback accumulates in your wallet, each entry with its own unlock date. Withdrawals open from the wallet once the first merchant payments come through, and the payout method is PayPal (US$10 minimum), straight from your wallet. Nothing expires in the meantime.
No. Detection runs entirely on your device against the cached offer catalog. Nothing you read, browse or write is transmitted, and the client source proves it.
A discount lowers the price at checkout; cashback comes back to you after the merchant confirms the purchase. Retriever shows whichever the offer carries, always with the amount stated before you click. When an offer carries both, you get both: the code cuts the price now, the cashback arrives after confirmation.
From the affiliate networks' own code APIs and feeds, verified at the source. We never scrape codes from the web, never test codes against your cart, and never auto-apply anything: you copy the code and paste it yourself at checkout.
You can, but know the trade: many codes found on coupon sites are tied to another publisher or blocked by the merchant, and using one can break the tracking of your purchase. If the commission is cancelled, there is nothing to split, so your cashback can drop to zero. Codes shown by Retriever are safe to stack with your cashback.
Yes. Everything that runs on your machine (the browser extension, the CLI, the status line) is MIT-licensed open source, and the repository goes public at launch. Our server stays private: it holds the business logic, never your data.
It sleeps. No fake urgency, no noise, no spam. That is the deal.
The browser extension will be submitted to the Chrome Web Store. Leave your email and you get exactly one email the day it is available. Nothing else, ever.
retriever
