Privacy policy

Keepsake is made by Rare Creatures LLC. This policy covers the Keepsake extension for Chrome and other Chromium browsers, Keepsake for Safari on Mac, and the Keepsake app for iPhone and iPad. They work the same way; where one differs, this page says so.

What Keepsake stores, and where

Everything lives on your device: in the browser profile you installed the extension in (Chrome, other Chromium browsers or Safari), or in the iPhone and iPad app's own storage, which it shares only with its Share extension and its widgets. None of it is uploaded by Keepsake.

• Your saves: title, price, retailer, the page address, images or a small local thumbnail, your notes, flags such as favorite and purchased, the collection it went into, and the details Keepsake read from the page or post: a recipe's ingredients and steps, a workout's exercises, a place's address and opening hours, a video's length and channel, an article's author and reading time, a film's year and director, a book's author and pages. For an Instagram post: its caption, creator, date, hashtags, location tag and links.
• Your collections: names, descriptions, keywords, aliases, covers and order.
• What it has learned from your corrections about where things should be filed, and a capped history of your last 200 corrections.
• Your workout goals and check-ins.
• Your settings, including which optional features you have turned on.
• Your AI key, if you added one: in the extension's local storage, or in your iPhone or iPad's Keychain (never synced). It is excluded from exports.
• The AI change log, so you can undo anything the AI changed. Also excluded from exports.
• While an Instagram import is under way, the posts it found and small copies of their thumbnails, until you import them. They are cleared when the next import starts, after the import and when you delete everything.
• On iPhone and iPad, small copies (640 px at most) of your saves' pictures, so a save keeps its picture if the site removes it, and a small summary for the widgets (your active goals and latest save's title).

Keepsake does not store your browsing history, page contents beyond the fields above, cookies, form data, credentials, or anything from pages you did not save from.

What runs on the pages you visit

By default, nothing. No script is left running on any website.

• The toolbar button, the keyboard shortcut and the right-click menu read the current page's title, price, images and structured data at the moment you use them, under the browser's activeTab grant, and then stop. Safari also asks you which sites Keepsake may use.
• On-page save buttons are off until you turn them on, either for sites you choose one at a time or for all sites. When on, a small script shows a Save button next to product cards and reads a card's details only when you hover, focus or save it.
• The Instagram import (Chrome, Chromium and Safari) runs only when you click Import this collection on one of your own Saved-collection pages, and only in that tab. It never reads your feed, profile, messages, followers, cookies or tokens.
• Sharing into the iPhone and iPad app: a page you share from Safari is read in Safari, with the same reader as the extension's toolbar button. The text in a screenshot or photo you share is read on your device, with Apple's own text recognition. Nothing is sent anywhere.

When Keepsake uses the network

Keepsake makes no network requests of its own, with these exceptions. Each is off until you turn it on.

Optional AI: off by default, your own key

When you turn it on and add your own API key, requests go from your device directly to the AI provider you chose, under your account with them and their privacy policy. We never see these requests and have no access to them.

• After each save and each Instagram import, Keepsake asks your provider what the save is (a recipe, workout, place, film, book, video, article, product or link) and fills in that kind's card. It sends the save's title, caption or description, creator, hashtags and location tag, its site and link, the details Keepsake already found, and its thumbnail only when that is a small copy stored on your device (never a link to someone else's image). The Chrome, Chromium and Safari extensions also send the text of the save's own page and of up to two pages its caption links to, but only for sites you have already allowed Keepsake to read, and fetched without your cookies. The iPhone and iPad app reads no linked pages.
• A save that is something to buy also has its price, retailer and the names of your collections sent, so its title can be tidied and it can be filed.
• Only when you start them: Fix with AI (the same for every save you check, plus, if you tick it, the title, price and availability on each product's live page), Check with AI, Find this product online (which shows you exactly what will be sent first), Draft a recipe and Suggest a progression on a workout goal.

What the AI wrote because the save didn't say it (for example a recipe that is only shown in a video) is marked AI draft on the card. A place's street address, phone number and opening hours are kept only when the save itself states them. Saves you filed or moved yourself are never moved, and everything the AI changes is logged so you can undo it.

Instagram

During an Instagram import in the extension, if you allow Read post details, Keepsake requests each imported post's own page from www.instagram.com, as your browser would when you open the post, to read its caption, creator, date, location and links. When you share an Instagram post or reel into the iPhone and iPad app, the app fetches that post's public page once, without cookies or your account. You can turn either off in Settings.

Lookups: each off by default

If you turn a lookup on, Keepsake asks a free public source for a missing detail: nominatim.openstreetmap.org for a place's address, www.wikidata.org for a film's details, openlibrary.org for a book's. Covers and posters load from Wikimedia Commons and covers.openlibrary.org. These are anonymous requests with no account and no identifier attached.

Maps and pictures

Your saves' images load from the sites they came from, exactly as a web page would load them. On iPhone and iPad, the maps of your places are drawn by Apple Maps. Open in Maps and Directions open Apple Maps or Google Maps with the place's name and address, built from what you saved; nothing is looked up until you tap.

What we receive

Nothing. There is no Keepsake server. We cannot see what you save, how many saves you have, or whether you use it. The Chrome Web Store and Apple's App Store give us aggregate install and rating figures, which do not identify you.

Permissions, and why each one exists

• storage and unlimitedStorage: to keep your library on your own machine without a size cap.
• activeTab and scripting: to read the page you are on at the moment you ask it to save.
• contextMenus: for the right-click Save to Keepsake item.
• Access to all sites is an optional permission, requested only if you turn on the on-page save buttons for every site, import from your open tabs, or let Fix with AI read live pages, and revocable in one click. In Safari, you grant each site in Safari's own settings.
• The iPhone and iPad app asks for nothing beyond what you share into it.

Children

Keepsake is not directed at children and collects nothing from anyone.

Your controls

• Export your whole library as a JSON file, and import it back, including into the iPhone and iPad app.
• Undo any change the AI made, from the change log.
• Turn off any optional feature at once; turning off AI or Lookups stops those requests immediately.
• Revoke site access in one click.
• Delete everything in one click. Deleted saves wait 30 days in the Trash first, unless you erase it all.

Changes

If this policy changes, the date at the top changes with it.

Contact

[email protected]
Rare Creatures LLC.