Privacy by design
As little data as possible.
You can search, compare deals, view retailer profiles and click through without an account. Hikeventory does not use full IP addresses, precise locations, full user-agent strings, fingerprinting or cross-site advertising IDs for retailer click tracking.
Price alerts without an account
For a product alert we only ask for the email address you enter, the product you want to follow and the alert settings. We also store the price and stock status at sign-up and later observations needed to determine whether something changed that you asked us to notify you about.
A product alert does not create a traditional account and does not automatically subscribe you to a newsletter or general marketing. Each alert has its own unsubscribe link. Using it disables that alert.
Essential referral logging
When you click through to a retailer, we record a one-time click ID, date and time, retailer, internal source page, limited context such as category or button position, device class, browser family, broad country code when supplied by the hosting platform, bot classification and redirect status. Without consent, no persistent session profile is created.
External traffic attribution
To understand whether visitors arrive through search engines, social media, email, referral sites or campaign links, Hikeventory can record a privacy-minimised acquisition event when the public site is opened. We keep only the landing path on Hikeventory, the external referrer domain when available, a broad acquisition channel and bounded UTM source, medium and campaign tokens. We do not store the full external referrer URL, search terms, gclid, msclkid, fbclid or other advertising click identifiers.
A one-time acquisition ID may be kept in browser memory during that visit and sent with a retailer click so the acquisition event can be connected to that outbound click. This ID is not stored in localStorage or sessionStorage and is not a persistent visitor identifier. A hard reload can therefore break that event-level connection.
Optional analytics
Only after explicit consent may a pseudonymous session ID be used for up to thirty days to measure returning visits and funnels. An internal account ID is only connected to click analytics when the user is signed in and that consent is active. Names and email addresses are not stored in the click log.
Retention periods
Raw click records are designed for a maximum retention period of ninety days. After that, only aggregated counts without account or session references may be retained. Product-alert data remains while the relevant alert is active or as long as technically necessary to handle unsubscribe and abuse prevention correctly. Financial records only become relevant when monetisation is explicitly activated.
Your rights
You can stop a product alert directly through its unsubscribe link; no sign-in is required. Once configured, the account environment can additionally support access, export, correction and deletion. Audit and financial records are only retained longer when there is a demonstrable legal basis.