Hopper Privacy Policy

Effective 8 November 2026 · Hopper Chrome extension by the WeLearn WD Team

In short: Hopper keeps everything on your own computer. It does not send any data to us or to anyone else, it has no account or server, it does not track you, and it never reads or stores passwords.

What Hopper does

Hopper is a Chrome extension for people who sell courses on Kajabi and register those offers in Salesforce. On a Kajabi offer page you open, it reads the offer's details so you can check them. On a Salesforce New Product form or Add Standard Price dialog you open, it fills those details into the form. You review the form and save it yourself. Hopper never clicks Save, submits a form or publishes anything.

Information Hopper handles

Only when you click Hopper's buttons, and only on the pages you have open, Hopper reads:

Hopper does not read or store passwords, payment card details, customer or student data, browsing history, or anything from pages other than the Kajabi and Salesforce pages described above.

Where the information is kept

Everything Hopper saves is kept in Chrome's local extension storage (chrome.storage.local) on your computer. It is not synced to other devices and is never sent to the developer, to WeLearn's servers or to any third party. Hopper has no analytics, no advertising and no remote code.

How the information is used

Saved details are used only to show them to you for checking and to fill them into the Salesforce forms you open. They are not used for any other purpose, and they are not sold, shared or transferred.

Keeping and deleting your data

Saved offers stay on your computer until you remove them. You can delete one offer or clear the whole list from Hopper's toolbar popup at any time. Removing the extension from Chrome deletes everything it stored.

Permissions

Changes to this policy

If Hopper's handling of data changes, this page will be updated and the effective date above will change.

Contact

Questions about this policy can be raised with the WeLearn WD Team through the issues page of this policy's repository.