Last updated: June 2026.
This page lists every cookie that may be set when you visit bobthecarguy.com, who sets it, and what it does. There's no banner or consent flow because nothing on this site requires opt-in consent under our reading of applicable U.S. law. If you'd like a more conservative version of any of this, your browser settings let you reject or delete cookies from any domain.
Cookies we set
- None. Bob the Car Guy LLC does not set any first-party cookies on bobthecarguy.com. We use no session cookies, no preference cookies, no analytics cookies of our own. If we add a feature in the future that requires a cookie (a comments system, a saved-articles button, anything similar), we'll update this page first.
Cookies set by Cloudflare (functional)
The site sits behind Cloudflare for content delivery and security. Cloudflare may set the following cookies in your browser as part of its operation:
- __cf_bm — a "bot management" cookie that helps Cloudflare distinguish humans from automated traffic. Set on the bobthecarguy.com domain. Typically valid for 30 minutes after the last request. Cloudflare's description: developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies.
- cf_clearance — set if Cloudflare presents a challenge (e.g., during DDoS or suspected-bot traffic) and you pass it. Marks your session as cleared. Valid for the duration that Cloudflare configures (typically 30 minutes to a few hours).
These cookies are functional. They don't track you across sites and they aren't used for advertising.
Cookies set by Google Fonts
Font files load from fonts.googleapis.com and fonts.gstatic.com. Google's standard practice is not to set tracking cookies on font file requests. Your browser may cache the fonts according to standard HTTP cache headers, but no cookie is set by Google for the font-load itself when used as we use it (CSS link in <head>).
Cookies set on third-party checkout pages we link to
If you click an advertising call-to-action and proceed to a sweepstakes ticket purchase, you leave bobthecarguy.com and arrive on a checkout page hosted by Funnelish on behalf of our affiliated sweepstakes operator PrizePanda. That checkout page is a different domain (typically join.prizepanda.io) and is governed by Funnelish's and PrizePanda's own cookie practices.
On those third-party pages, you may encounter cookies set by:
- Meta — the standard browser-side Meta Pixel may run on the checkout pages, which sets first-party cookies named
_fbpand (if you arrived from a Meta ad click)_fbc. These are advertising-measurement identifiers. - Funnelish — its own session/cart cookies for the checkout flow.
- The checkout's payment processor — depending on payment method, a card-tokenization service may set cookies necessary for fraud detection.
Those cookies are not set by us and are not set on our domain. They follow the privacy policies of the operators of those pages. We mention them here for completeness because some visitors arrive at those pages by clicking ads we've placed.
What we don't set
- No Meta Pixel cookies (
_fbp,_fbc) on bobthecarguy.com. We use server-side Conversions API instead of the browser Pixel, which means no browser-side Meta cookies originate from our domain. See the Privacy Policy for the full details of what we do send to Meta from our server. - No Google Analytics cookies (
_ga,_gid, etc.). We don't use Google Analytics. - No advertising-network cookies (Google Ads, Microsoft Ads, TikTok, Pinterest, etc.). We do not run third-party advertising on our own pages.
- No cross-site tracking pixels in our HTML.
Local storage and session storage
Our scripts do not write to localStorage or sessionStorage on the safe-site pages of bobthecarguy.com. The mobile menu, image fade-in, and footer year stamp scripts use no browser storage at all.
How to inspect or clear cookies
Every major browser provides controls to inspect, block, or clear cookies for any domain. The relevant settings are typically under "Privacy" or "Cookies and site permissions" in your browser's preferences. Most browsers also offer a "private browsing" or "incognito" mode in which most cookies do not persist between sessions. We won't link to specific instructions because browser UI changes; your browser vendor's help documentation will always be more current.
If our cookie use changes
We'll update this page and note the change at the top. Material changes will also be flagged in a recent article.