Privacy policy

First-party catalog activity and recommendations

Personalized recommendations are off by default. Signed-in users can opt in with the recommendation setting. When enabled, we store selected catalog activity: part views, search-result opens, slicer opens, and vehicle-generation and category selections. We use catalog identifiers, timestamps, site context, and limited technical labels, not raw search text, full URLs, email addresses, IP addresses, or authentication tokens.

Timestamped first-party catalog-activity coverage begins only after event capture is deployed and enabled. Historical lifetime counters do not contain event timestamps, so they cannot reconstruct exact historical 7-, 28-, or 90-day activity from before capture begins.

Turning the setting off stops new client-observed catalog history and uses non-personalized suggestions. Downloads, saves and likes still work; their business totals may be retained without account attribution. Anonymous visitors do not receive a persistent first-party behavioral profile. Prior history is not used for personalized suggestions while the setting is off.

Raw catalog events are eligible for bounded cleanup after 365 days by default. Pending analytics delivery records are held until delivery or reconciliation; essential business and retry records may remain longer. Account deletion removes catalog-event ownership while preserving non-identifying totals. Deleted catalog objects lose their links in this history.

PostHog mirroring uses separate analytics consent, not the recommendation preference alone. Approved mirrors are sent asynchronously; absent an explicit consent context, server mirrors are withheld. Recommendation requests use our own database and do not query PostHog. Changing personalization does not by itself change your analytics cookie choice or erase previously delivered analytics.

Analytics consent

Analytics consent is separate from personalized recommendations. You can change that choice without changing your recommendation setting.