PRIVACY
Privacy, in plain language.
How we handle Awin affiliate attribution, limited click records, transactional price-alert email and infrastructure logs.
Operational draft for owner review before public launch. This text is not legal advice and is not a claim of compliance with any particular jurisdiction.
Browsing the comparisons
Eligible public comparison pages load Awin’s Publisher MasterTag when enabled to support affiliate attribution; eBay shopping pages exclude it. Awin receives technical request information, such as your IP address and browser information, and may process the referring page and affiliate-link interactions. Pages use self-hosted fonts. Our hosting infrastructure also processes technical logs to operate and secure the service.
Following an affiliate link records the offer or merchant identifier and a limited source-page or campaign label on our server. Awin Tracking Optimisation may add attribution parameters or direct you to an eligible merchant while sending a tracking request to Awin. No customer account is required. See Awin’s privacy policy at https://www.awin.com/gb/privacy for its practices; merchants also have their own policies.
eBay shopping links include a fixed label for the catalog, search view or selected GPU model so affiliate reports can distinguish those shopping routes. These labels contain no visitor identifier or typed search text. Our own eBay referral counters store daily totals by these fixed labels; they do not establish unique visitors, purchases or earnings.
Email alerts are opt-in
The Awin tag is excluded from price-alert forms, confirmation and unsubscribe pages, and administrative pages. When email delivery is enabled, an alert request supplies an email address, product, target price and explicit consent. A confirmation link must be deliberately submitted before the alert is verified. Merely opening a confirmation page does not activate an alert.
The database stores the alert and transactional email-delivery records needed to run it. Confirmation and unsubscribe tokens are stored as hashes. Email delivery uses the configured provider. No newsletter or marketing subscription is included in the alert consent.
An unsubscribe page asks for a deliberate confirmation and then stops that alert. Technical retention and deletion settings must be reviewed by the operator before public launch; this draft does not promise that unsubscribing instantly erases all operational records.
Security and contact
Requests are bounded and rate-limited, and state-changing public forms require the configured site origin. Administrative access is separate and requires authorization. These controls reduce risk but are not a promise of absolute security.
Use the Contact page for the operator’s configured contact channel. If no contact channel is configured, the page says so rather than supplying a nonexistent address. Provider identities, retention periods, operator details and applicable privacy rights require owner review before launch.
Related information
Methodology · Data accuracy · Affiliate disclosure
PriceQuarry · Recorded observations, with their limits in view.