Privacy Policy

Catchery（应云小笺）　·　Last updated: 2026-09-07

Catchery is a browser extension for saving pages into categories and syncing them across your own devices. This policy explains what data the extension handles and, more importantly, where it goes.

If you have questions, contact: [email protected]

The short version

We have no server. Catchery never sends your data to us, because there is no "us" to send it to. Everything you save goes to a storage bucket that you own and configure yourself (any S3-compatible service). Your storage credentials stay in your browser's local storage on your own machine.

What the extension stores, and where

Data	Where it lives	Who can read it
Categories and saved items (titles, URLs, descriptions)	Your S3-compatible bucket, as a single object {prefix}/state.json	You, and anyone you give the bucket to
Thumbnails (page screenshots), uploaded images and PDFs	Your bucket, under {prefix}/thumbs/ and {prefix}/files/	Same as above
Your endpoint, region, bucket, access key and secret key	Your browser's local storage (chrome.storage.local) on your device	Only you, on that device
A device identifier and device name (used to resolve sync conflicts between your own devices)	Inside {prefix}/state.json in your bucket	Same as the first row

That is the complete list. There is no other storage and no other recipient.

What the extension does not do

• It does not collect analytics, telemetry, or usage statistics.
• It does not use cookies or any tracking mechanism.
• It does not have an account system, and you never register with us.
• It does not run or fetch remote code.
• It does not sell, share, or transfer data to any third party.
• It does not read your browsing history. It only accesses a page when you explicitly click "Add current page".

Permissions, and why each one is needed

Permission	Why
storage	Save your configuration and keep a local copy for offline use
activeTab	Take a screenshot of the page you are looking at, and only when you click "Add current page"
tabs	Find and focus the tab you asked to open
scripting	Injected into bing.com/saves only, to read the collection list you already see on that page, when you start an import

About <all_urls> in host permissions: this is required so that the extension can (1) capture a screenshot of whatever page you choose to save, and (2) reach the S3-compatible endpoint you configured, which may be any host. Catchery does not contact any host other than the endpoint you entered yourself.

About file:// access: disabled by default. It is only used if you enable "Allow access to file URLs" on the extensions page yourself, in order to save a local image or PDF from your own disk.

Importing from Bing Collections

This is an optional, one-time import that you trigger manually.

It runs entirely in your browser: the code reads the collection data that the Bing page itself has already loaded, using your own logged-in browser session. Your Bing session cookies never pass through the extension's code — the reading happens inside the page context, and the extension never requests or receives them. (The extension does not request the cookies permission at all, which you can verify in the extension's details page.)

The imported items, and their thumbnails, are then written to your bucket.

Note: this import relies on the Bing web interface as it currently exists. If Bing changes how its collections page works, the import may stop functioning.

Data security

• Your credentials are stored only in your browser's local storage on your device. They are never uploaded, and never sent anywhere other than to the endpoint you configured, as part of standard S3 request signing.
• Transfers to your bucket use HTTPS when you configure an HTTPS endpoint.
• Because your data lives in a bucket you control, its security also depends on how you configure that bucket. We recommend using a private bucket and a dedicated access key with the minimum permissions needed.

Your control over your data

• View or delete your data: it is in your own bucket — use your storage provider's console or any S3 tool.
• Stop syncing: clear the configuration in the extension's settings page, or uninstall the extension.
• Remove local data: uninstalling the extension removes its local storage. Data already in your bucket is unaffected, since it belongs to you.

Children

Catchery is not directed at children under 13, and does not knowingly collect any information from them.

Changes to this policy

If this policy changes, the updated version will be posted at this URL and the "Last updated" date above will be revised.

Contact

Questions about this policy: [email protected]