Legal
Cookie and Tracking Technologies Notice
Effective Date: June 14, 2026
Last Updated: June 14, 2026
This Cookie and Tracking Technologies Notice explains how rskcars.com uses cookies, pixels, tags, SDKs, local storage, session storage, scripts, security tools, analytics tools, advertising tools, and similar technologies.
This Notice is part of the RSK Auto Group Privacy Policy.
1. What Cookies and Tracking Technologies Are
Cookies are small files stored by your browser. Similar technologies, such as pixels, tags, scripts, local storage, and device identifiers, can help websites operate, remember preferences, secure forms, measure traffic, attribute ads, personalize ads, and detect abuse.
Some technologies are necessary for the website to function. Others are used for analytics, advertising measurement, advertising personalization, or social media measurement and can be controlled through .
2. Current Categories
Necessary, Security, and Functionality
Examples: RSK website cookies, privacy-choice storage, Firebase Authentication, Firebase security technologies, Firebase App Check if enabled, Google reCAPTCHA, session tokens, CSRF or anti-abuse tokens, rate-limit records.
Purpose: Operate the website, support navigation, protect forms, reduce spam, secure authentication, remember privacy choices, maintain site integrity, and prevent abuse.
Can this be disabled through the privacy tool? No. Necessary, security, and privacy-choice storage cannot be disabled through the website preference center.
Typical retention: Session to 180 days for preference cookies, unless a different provider-controlled security period applies.
Analytics
Provider examples: Google Analytics 4, Firebase-linked Google Analytics, Google Tag Manager.
Example cookies or identifiers: _ga, _ga_<measurement-id>, analytics event identifiers, consent-mode analytics signals.
Purpose: Measure page navigation, inventory views, vehicle searches, lead-request events, phone clicks, directions clicks, device/browser performance, and website reliability.
Form values sent? No. Analytics events should not include submitted names, emails, phone numbers, Social Security numbers, financing fields, ZIP-code form values, passwords, or free-text finance details.
Can this be disabled? Yes, through where applicable.
Typical retention: Provider-controlled; Google Analytics cookies may persist according to Google settings and browser limits unless rejected, revoked, blocked, or deleted.
Advertising Measurement
Provider examples: Google Ads, Google Tag Manager, Google Consent Mode.
Example cookies or identifiers: _gcl_*, gclid, gbraid, wbraid, campaign identifiers, conversion measurement signals.
Purpose: Attribute advertising visits, measure ad performance, support conversion measurement, and improve campaign reporting.
Can this be disabled? Yes, through where applicable.
Typical retention: Provider-controlled and campaign-dependent; first-party advertising cookies are removed or disabled where technically possible when this category is revoked.
Advertising Personalization
Provider examples: Google Ads, Google advertising signals, remarketing or audience tools if enabled.
Purpose: Personalize ads, build or use advertising audiences, retarget visitors, and improve ad relevance where allowed.
Can this be disabled? Yes, through , Global Privacy Control where applicable, and applicable Google ad settings.
Typical retention: Provider-controlled and dependent on campaign and platform settings.
Social Media Measurement
Provider examples: Meta Pixel.
Example cookies or identifiers: _fbp, _fbc, fbclid, Meta event identifiers.
Purpose: Measure PageView, ViewContent, Search, Lead, and similar events; attribute Meta ad visits; support advertising measurement; support retargeting or audience tools where allowed.
Form values sent? Meta events should not include submitted names, email addresses, phone numbers, Social Security numbers, financing fields, or free-text form values.
Can this be disabled? Yes, through where applicable.
Typical retention: Provider-controlled; first-party Meta cookies are removed or disabled where technically possible when this category is revoked.
3. Google reCAPTCHA and Firebase Authentication
The website may use Google reCAPTCHA or reCAPTCHA Enterprise to protect forms, authentication, and website security. Firebase Authentication may also use reCAPTCHA or similar verification for phone authentication, email/password authentication protection, and abuse prevention.
reCAPTCHA and authentication-related technologies are used to help distinguish legitimate users from bots, spam, abuse, automated attacks, and suspicious activity. These technologies are treated as necessary security technologies and may operate even when analytics and advertising are rejected.
4. Google Consent Mode
The website may use Google Consent Mode to communicate your choices to Google tags.
When consent is denied for a category, Google tags may operate differently, including by limiting cookies or sending limited cookieless measurement signals where supported. Denying consent is not a guarantee that no technical communication with Google occurs; it means the website will signal your choice and restrict covered storage and covered use according to the implemented consent settings.
5. Your Privacy Choices
You can manage nonessential analytics, advertising measurement, advertising personalization, and social media measurement through:
Your choices are stored in your browser. If you clear cookies, change browsers, use another device, use private browsing, or reset your browser storage, you may need to set your choices again.
6. Global Privacy Control
Where required by law, a valid Global Privacy Control signal is treated as an opt-out of sale, sharing, targeted advertising, advertising personalization, and social media tracking for the browser or device sending the signal.
Global Privacy Control does not disable necessary storage, security technologies, authentication technologies, fraud-prevention tools, or all privacy-limited cookieless measurement.
7. Browser Controls
Most browsers allow you to delete or block cookies. Blocking all cookies may prevent parts of the website from working correctly, including saved privacy choices, login, form protection, and account features.
8. Updates to this Notice
We may update this Cookie and Tracking Technologies Notice as website features, vendors, tags, cookies, laws, and provider settings change.