Is Send to Kindle safe?
Send to Kindle sends the active page URL, title, and page HTML to Reabble when you click its toolbar button.
When you click the extension button on an HTTP or HTTPS page, Send to Kindle injects a content script that submits a form to Reabble with the current URL, page title, and the page body HTML. The code chooses either the global Reabble backend or the China backend based on the extension setting, timezone, or browser language.
Who publishes itOXYRY - no other listings under this identity, 2 shared hostnames
OXYRY - no other listings under this identity, 2 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 2 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
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 2.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Act on the current tab, but only after you click the extension
activeTab
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Where it sends data
Destinations our analysis observed Send to Kindle 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.
- send.reabble.cn
Send to Kindle sends data to send.reabble.cn. No other extension we have analysed sends data here.
- send.reabble.com
Send to Kindle sends data to send.reabble.com. No other extension we have analysed sends data here.