Privacy policy
Wishy browser extension · Last updated 17 November 2026
Wishy adds books to your Amazon wishlist. You pick a book photo on X, or select a title on any page, and the extension adds the book. This page explains what the extension handles, where that data goes, and what is kept.
When it does anything
The extension acts when you choose Add book to Amazon wishlist from the right-click menu, or type a book on its setup page. Otherwise it doesn’t read pages in the background or keep track of what you browse, unless you turn on auto-add.
Auto-add from X (version 1.1 and later) is off until you add your own TypeSafe API key and turn it on in setup. While it’s on and you’re on the Following tab of your X home page, the extension reads the posts you scroll past. It checks each one in your browser for words about books or reading, such as “book”, “reading” or “novel”. Posts without such words go nowhere. Posts with them are sent as described below.
On x.com, the extension notes the text of the post you right-click, so it can read a book photo together with what the post says, and who posted it (their name and @handle), for the note described below. This stays in the tab unless you choose the menu item.
What is sent, and to whom
The post, so the book can be identified. This is the text you selected, or the photo you right-clicked together with that tweet’s text.
- By default, it goes to the Wishy server, which is hosted on Netlify. The server passes it to Google’s Gemini API and sends back the book’s title and author. The server doesn’t store or log the post. It uses Google’s paid Gemini service. Google doesn’t use that content to improve its products, and keeps it for a limited time only to detect abuse (Gemini API terms).
- If you add your own Gemini API key on the setup page, the post goes straight from your browser to Google instead, under your own agreement with Google. It never reaches our server. With a free-tier key, Google may use what you send to improve its products, and people at Google may review it.
Posts checked by auto-add. For each post that mentions books, the extension sends its text and its first photo straight from your browser to TypeSafe’s Jev API, a service in the United States, using your own TypeSafe key and under your own agreement with TypeSafe. Jev says how likely the post is to be about a specific book. These posts don’t pass through the Wishy server. TypeSafe’s privacy policy says it doesn’t train models on what it receives. For likely book posts, the extension then identifies the book as described above, through the Wishy server or your own Gemini key, and adds it to the list you chose for auto-add.
Requests to your Amazon account. The extension reads your list names, searches for the book and adds it. It does this by sending requests from your browser to the Amazon store you picked in setup, such as amazon.com or amazon.de, using the Amazon login already in your browser. Wishy only has access to that one store, and only after you allow it. From version 1.1, for a book from X, it also writes a note on the item in your list saying who posted it, such as “Recommended by Jane Doe (@janedoe) on X” with a link to the post, unless the item already has a note. Anyone who can see the list can see its notes, so on a public list the note is public too. These requests go straight to Amazon. We never see your Amazon account, password, lists or orders.
Book photos. Your browser loads them from X’s image server (pbs.twimg.com).
What the server keeps
Free use is limited to 5 books a day, plus a separate daily allowance of books found by auto-add. To enforce that, the server counts each day’s requests against two things:
- a random ID that the extension creates when it’s installed. It isn’t linked to your name, email or any account.
- a one-way, salted hash of your IP address. The address itself isn’t stored.
The counts are deleted after two days. The server also receives the extension’s version number. Netlify, which hosts the server, processes request details such as IP addresses to run the service, under its own privacy policy.
What stays on your device
The extension’s local storage holds:
- the Amazon store and wishlist you picked (the list’s name and ID)
- your last 40 books: title, author, Amazon link, the site each came from (for posts on X, the X handle and a link to the post), the time and the result
- whether auto-add is on and the list it uses, and the IDs of the last 3,000 X posts it has looked at, so none is checked twice
- the random install ID
- your Gemini API key and your TypeSafe API key, if you added them
None of this is sent anywhere except as described above. Removing the extension deletes all of it.
What we don’t do
We don’t sell or share your data, show ads, or use analytics or tracking. We don’t use your data for anything except adding books to your wishlist. Our use of this information follows the Chrome Web Store User Data Policy, including the Limited Use requirements.
Children
Wishy isn’t meant for children under 13.
Changes
If this policy changes, we’ll update this page and the date at the top.
Contact
Questions or requests: thetrendresearcher@gmail.com