Is Henry Luxe Rewards safe?
Henry Luxe Rewards sends serialized extension storage, including Supabase session tokens, to henry.social API requests.
When it contacts its Henry tRPC API, the extension serializes most chrome.storage.local entries into an x-plasmo-storage header. Because the Supabase auth session is stored in the same local storage, Henry API requests can include the user's Supabase access and refresh tokens.
Who publishes ithenry-dev - no other listings under this identity
henry-dev - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 0.0.46. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every secure site you visit
https://*/*
Read and change your data on every site you visit
http://*/*
Store data in your browser
storage
Where it sends data
Destinations our analysis observed Henry Luxe Rewards contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- henry.social
Henry Luxe Rewards sends data to henry.social. No other extension we have analysed sends data here.