Privacy Policy
Last updated: 30 September 2026
1. About PureSave
PureSave is a browser extension and comparison service that helps users check whether a matching product may be available from another retailer at a lower price.
2. Information processed by the extension
Only after you click the scan button, the extension may read product information needed to prepare a comparison. It does not scan before that action. On that page, subsequent DOM changes trigger a debounced local re-extraction after 1.2 seconds only when normalized product details change. These updates refresh tab-session data and clear stale deals; another API comparison requires another click. Disabling the site or leaving the page stops observation. The extension temporarily keeps the normalized product details and comparison status in browser session storage for the current tab.
PureSave does not read the page's full HTML, shopping account details, payment details, passwords, unrelated form entries, or general browsing history. Product colour, size and similar variant selections are read only from explicitly identified product-option containers and recognized variant controls. Generic selects, checkboxes, delivery, account, payment and marketing controls are excluded.
3. Information sent to the PureSave service
After you request a scan, the extension sends a normalized comparison payload to the PureSave backend. It can include the retailer's domain, the displayed price and its explicit currency, product identifiers (such as GTIN, brand, model or manufacturer part number, product title, variant details and retailer SKU), and ranked match candidates. It does not include the page URL path or page HTML. Debug-only extraction details are not sent.
Each new comparison also requires a short-lived Argon2id proof-of-work challenge bound to the exact payload bytes. The challenge service processes a SHA-256 digest; the submission service verifies the proof before admitting the comparison. Proof of work is an abuse-control measure, not account authentication. The poll credential is sent in a request header and is not placed in the URL.
Like most internet services, the server and infrastructure providers may process technical information associated with a request, such as an IP address, timestamps and request metadata, for security, operation and rate limiting.
4. Browser storage
PureSave may use browser storage for functionality such as remembering websites where you have disabled PureSave and temporarily storing prepared product details, the page origin/path to avoid reuse on another page, the latest comparison result, a short-lived polling credential and status for the current browser tab. Query strings and fragments are not stored. These tab records are cleared on navigation or tab closure; disabled-site preferences use Chrome sync storage.
5. Retailer and comparison data
Comparisons currently use locally stored Awin product offers; the comparison request does not cause the server to fetch a retailer URL or send your product details to a retailer. PureSave does not intentionally send your payment information, account credentials or form data to Awin or other offer providers.
6. Affiliate links
Some retailer links shown by PureSave may be affiliate links. If you choose to follow an affiliate link and make a qualifying purchase, PureSave may receive a commission from the retailer or affiliate network. This does not increase the price you pay.
7. How we use information
Information processed by PureSave is used to provide price comparisons, operate and secure the service, prevent abuse, diagnose problems, maintain service reliability and improve the comparison experience.
8. Selling or unrelated use of data
PureSave does not sell personal information. Data handled by the extension is not used for creditworthiness or lending decisions and is not intended to be used for unrelated advertising profiling.
9. Data retention
The server stores only normalized matching fields needed for the job (GTIN, brand, MPN, model, product title and variant attributes where supplied, currency and integer price), the result, and short-lived challenge and poll records. It does not retain the retailer domain, page URL, SKU or raw request body in comparison jobs. Challenges expire after two minutes and polling credentials after 20 minutes. Completed jobs and associated identity records, expired challenges and polling records become eligible for cleanup after a one-day retention margin; removal occurs during later challenge issuance, so expiry does not imply immediate deletion. A completed result may be reused for up to 10 seconds after it is first computed. Technical server logs and security information may be retained by infrastructure providers for operational and security purposes. PureSave aims to retain information only for as long as reasonably necessary for the purpose for which it is processed.
10. Children
PureSave is not directed at children and is not intended to knowingly collect personal information from children.
11. Changes to this policy
This policy may be updated as PureSave develops, adds retailers or changes infrastructure. The latest version will be published on this page with an updated date.
12. Contact
Questions about this policy can be sent to [email protected].