TECHNOLOGY

Cookie Policy

A factual description of RareReg’s current cookies and the privacy boundaries for consent-gated dealer-listing analytics.

Effective
September 10, 2026
Last updated
September 10, 2026

Current cookie use

RareReg currently uses technically necessary authentication and session technology supplied through Supabase, a first-party referral-attribution cookie where applicable, and a short-lived first-party password-recovery cookie.

RareReg also stores a first-party analytics preference and, only after that preference is accepted, may create a first-party analytics visitor cookie and a separate first-party session cookie for dealer-listing and site-wide analytics, and load Google Analytics 4.

Why essential cookies are used

  • Authenticate users and refresh sessions.
  • Apply account, owner, and administrator access controls.
  • Protect private offers, uploads, claims, and account pages.
  • Maintain security and basic application operation.

Referral attribution

rarereg_referral is a first-party cookie used to preserve a valid RareReg referral code until account or eligible purchase attribution is completed. It lasts for up to 90 days, is HttpOnly, uses SameSite=Lax and Path=/, and is Secure in production. It is not used for advertising or cross-site profiling.

Password recovery

rarereg-password-recovery is a first-party cookie used temporarily to complete an authorized password-recovery flow. It lasts for 15 minutes, is HttpOnly, uses SameSite=Lax, is limited to the password-reset path, and is Secure in production.

Analytics cookies (dealer-listing analytics, site analytics, and Google Analytics)

rarereg_analytics_preference is a first-party cookie that stores whether analytics has been accepted or rejected. It lasts for up to 180 days, is HttpOnly, uses SameSite=Lax and Path=/, and is Secure in production. The same preference controls RareReg's first-party dealer-listing analytics, RareReg's first-party site-wide analytics, and whether Google Analytics 4 loads.

rarereg_analytics_visitor is a first-party analytics/performance cookie used to measure qualifying public vehicle-detail views for authorized dealer listing-performance reporting, and is also reused to identify a pseudonymous visitor for RareReg's own site-wide analytics. It has an absolute 90-day lifetime with no sliding renewal and is Secure, HttpOnly, SameSite=Lax, and available on Path=/. It has no cross-site advertising or third-party ad-targeting purpose.

rarereg_analytics_session is a first-party cookie used only for RareReg's own site-wide analytics, to group page views into a single session. It uses a 30-minute sliding inactivity window—each qualifying page view extends it, and it expires after 30 minutes of inactivity, after which the next page view starts a new session. It is Secure, HttpOnly, SameSite=Lax, and available on Path=/, and has no cross-site advertising or third-party ad-targeting purpose.

RareReg creates the analytics visitor and session cookies and collects dealer-listing or site-wide analytics only when collection is separately enabled and the analytics preference is accepted. A Cookie preferences control is available in the site footer.

Google Analytics 4 is a third-party analytics service operated by Google. RareReg does not load Google Analytics 4, and Google does not receive analytics data from RareReg, unless the analytics preference is accepted. Once loaded, Google Analytics sets its own cookies (for example, cookies in Google's _ga family) to distinguish visitors and sessions; their names, purposes, and durations are set by Google, not RareReg. Google Analytics 4 is used only to measure aggregate site traffic and usage and is configured with Google's advertising signals and ad personalization features turned off.

Hosting and technical records

Vercel and Supabase may process request information, IP address, browser/device attributes, security events, and diagnostic logs in operating the application. The contact endpoint also uses a host-forwarded IP address temporarily in server memory to enforce a short abuse limit. These operations do not add an advertising profile in RareReg’s application database.

Browser and consent controls

You can block or remove cookies using browser settings, but disabling essential session cookies can prevent sign-in and account features from working.

The Cookie preferences control in the site footer lets you accept or reject first-party dealer-listing analytics, first-party site-wide analytics, and Google Analytics 4 together, using one preference, and change that choice later. Rejecting analytics removes the analytics visitor cookie and the analytics session cookie, prevents dealer-listing and site-wide analytics collection, and keeps Google Analytics 4 from loading. Accepting loads Google Analytics 4 and enables first-party analytics collection without requiring a page reload.

Changes and contact

RareReg will update this Policy if its cookie behavior or purposes materially change. Advertising or cross-site tracking would require separate disclosure and review and is not part of the approved dealer-listing analytics, site analytics, or Google Analytics 4 design.

Questions: info@rarereg.com. For broader information practices, see the Privacy Policy.