Privacy Policy
Last updated: June 19, 2026 · Applies to Jewell Made products, including SharedSave and Advertisement Ends Here!
About this policy
Jewell Made is an independent software company. This Privacy Policy covers the Jewell Made products described below. Each product section explains what that product collects, how it is used, and who it is shared with. The Contact and Changes sections at the end apply to all of them. Products that are not listed here are governed by their own policy or store listing.
SharedSave (web app and AI connector)
SharedSave is a grocery shopping web app that tracks real prices at your local store, finds the deals worth grabbing, and scores the health of what goes in your cart. It includes an optional connector that links your own AI assistant to your SharedSave account.
Information SharedSave collects
SharedSave may store your account details (including your email address), shared list membership, grocery list items, your selected store and location, Fry's/Kroger price-refresh metadata, cached coupon and product records, public nutrition records, food health-score outputs, recommendation history, and the operational logs needed to run and troubleshoot the service.
How SharedSave uses information
Information is used to authenticate you, preserve shared lists, cache retailer data you select through the authorized workflow, generate shopping and savings recommendations, compute food health scores, show your savings history, and maintain reliability.
Connecting your own AI assistant
SharedSave offers an optional connector that lets you link your own AI assistant — such as Anthropic's Claude — over the Model Context Protocol (MCP). The connector is off until you choose to enable it. Connecting uses OAuth: you sign in to SharedSave and approve access on a consent screen, and an access token scoped to your account is issued. While connected, the assistant can read your grocery lists, product and coupon context, and nutrition data, and can submit enriched search terms, product matches, and nutrition evidence back to your account to improve your shopping results. That data is sent to and processed by the AI provider you choose (for example, Anthropic), under that provider's own privacy policy. You can disconnect at any time, which revokes the token.
Third parties SharedSave shares data with
SharedSave shares data with third parties only as needed to provide the service: Kroger and Fry's (retailer prices, coupons, and product data accessed through your authorized session); Microsoft Azure (text translation for Spanish-language content, when enabled); and, only if you turn on the AI connector, the AI provider you connect, such as Anthropic (Claude). Public nutrition sources such as Open Food Facts and USDA FoodData Central are used by server-side refresh jobs. SharedSave is not affiliated with or endorsed by Kroger or Fry's. Each third party processes data under its own privacy policy.
Data retention
SharedSave keeps your account and list data for as long as your account is active. Cached retailer prices, coupons, and product records are refreshed and superseded over time. Operational logs are retained for a limited period for troubleshooting and security. AI connector tokens are kept until you disconnect or they expire. When you ask us to delete your account, the associated personal data is removed, except for limited records we must retain to comply with law.
Your choices and rights
You can review and edit your lists in the app, disconnect the AI connector at any time, and request an export or deletion of your account data by emailing [email protected]. We will respond within a reasonable time. SharedSave food health scores are general nutrition guidance, not medical advice.
Advertisement Ends Here! (browser extension)
Advertisement Ends Here! is a local-only tool. It has no backend, no telemetry, no analytics, no accounts, and no cloud sync. Nothing the extension records ever leaves your device unless you explicitly export a report file and share it yourself.
What the extension processes on your device
To block trackers and record evidence of tracking attempts, the extension processes, locally:
- Network request metadata (URLs, hosts, resource types) to match requests against its registry of known tracker endpoints and its behavior-based detector.
- Page tracking API calls (for example
fbq,gtag,dataLayer.push) observed in pages, with arguments redacted before storage. - Cookie names and consent-manager storage keys on sites you visit, to record your privacy and consent state.
- Search form submissions, recorded as a hashed label (the search text itself is not stored unless you explicitly enable plain-text evidence).
What the extension stores
Evidence events are stored locally in your browser's extension storage. Values are redacted by default before storage: email addresses, phone numbers, and long opaque tokens are replaced with hashes; credit-card-like numbers are removed entirely; page URLs are stored without query strings. Plain-text evidence is off by default. Stored events are capped (oldest pruned) and can be erased at any time with the Clear button.
What the extension transmits
The extension sends no data about you anywhere. It makes two kinds of network request of its own, and neither carries any information about you beyond the request itself.
Loader transparency. When it blocks a known tag-manager loader (for example Google Tag Manager), it may fetch that same public script file — without cookies or credentials — solely to tell you which tracking companies the blocked loader would have installed. This is cached and never includes your browsing history.
Blocklist updates. It periodically downloads an updated tracker blocklist — a public file listing
tracker domains — from https://jewellmade.com/advertisement-ends-here/trackers.json, as a plain
request with no cookies, no credentials, and no query string. This only refreshes which domains the extension
blocks; it sends nothing about you and no browsing history. The list is treated strictly as data, never executed
as code, and if the download fails the extension keeps using the list it already has.
Outbound effects you configure are performed locally by the browser: blocking requests, removing tracking
parameters, removing tracker cookies, and attaching the Sec-GPC: 1 (Global Privacy Control) header
when that setting is on.
Permissions
declarativeNetRequest,webRequest— block tracker requests and observe outcomes for evidence.cookies— remove known tracker cookies when you start a recorded test.storage— store settings and the local evidence log.activeTab— read the current tab's address when you open the popup, to show that site's card and offer per-site disable.- Host access — required to observe and block tracker requests on the sites you browse.
Data sharing and sale
No data is shared with, sold to, or transmitted to anyone. There are no third-party analytics or advertising services involved — that would be ironic.
Exported reports
When you download a report or diagnostics file, a JSON file is saved to your device. These files can contain the redacted evidence described above. Treat exported files as sensitive and share them only deliberately.
Paid plans (planned)
A paid tier is planned. When it launches, payments will be handled by a payment processor (you would buy on their checkout page, not inside the extension), and the extension would validate an anonymous license token — never your browsing data, never the evidence log. This policy will be updated with specifics before any paid plan goes live, and the local-only promise above will not change.
Contact
Privacy questions, data export or deletion requests, and security or vulnerability reports for any Jewell Made product can be sent to [email protected].
Changes
Material changes will be reflected here with a new "Last updated" date and, for extensions, in the store listing.