Why OfferAdd asks for these permissions
Chrome shows these when you install the extension. Here’s what each one is for, in plain words.
Read and change your data on secure.chase.com, deals.merchant-rewards.com, global.americanexpress.com, capitaloneoffers.com and onlinebanking.usbank.com
So OfferAdd can read the offers on your bank’s offers page and, when you click Add all, add them. deals.merchant-rewards.com is Bank of America’s deals site; capitaloneoffers.com is Capital One’s, where OfferAdd only reads offers and never adds them; onlinebanking.usbank.com is U.S. Bank’s online banking, where OfferAdd only works on its cash-back deals page. It only works on these sites, and only on their offers pages: everywhere else on them, it does nothing.
Storage
Keeps your offers, settings and sign-in on your computer, so the Offers page and lookup work without the internet.
Active tab
Lets the popup read the offers page you’re looking at when you open it, so it can show your counts and run Add all on that tab.
Scripting
Starts the offer reader on your bank’s page when you open the popup, if it isn’t already running.
Read your data on all websites (only if you turn on the checkout helper)
Asked only when you switch on the checkout helper, and removed when you switch it off. It reads just the page address to notice a checkout and recognize the store. It never reads what’s on the page or what you type.
What the extension never does
- Read your transactions, balances or account numbers.
- See or store your bank password.
- Add offers on its own. Adding always starts with your click.
- Run analytics, ads or third-party scripts.
- Send anything except your offers (store, deal, card last 4, status) to your own OfferAdd account.
Questions? Email hello@offeradd.app.