Mostly essential cookies
Most cookies used on this store help keep cart, guest continuity, account, and checkout features working.
Policy
Cookie Policy
This page explains how Onkar Electronics uses cookies, session identifiers, and similar browser storage to keep the storefront functional, preserve shopping context, support guest and signed-in continuity, understand first-party shopping behavior, and complete checkout-related flows.
Need help?
If you have questions about cookies or browser storage on this site, contact us and we will help.
Last updated March 16, 2026First-party cookie inventory
What this page covers
The main cookies and browser storage used across cart, guest browsing continuity, account, fitment, and sign-in.
Third-party services
Checkout and Google sign-in can also use their own cookies or browser storage while those services are active.
Questions about cookies?
If you need help, contact us and we will explain how these tools are used.
Overview
How cookies are used on this storefront
Onkar Electronics uses cookies and similar browser storage to keep key storefront features working, including cart continuity, guest browsing continuity, sign-in, fitment, delivery estimates, and checkout.
Used to keep shopping features working
Most cookies used on this storefront help preserve cart contents, maintain signed-in sessions, remember selected vehicle fitment, and protect account sign-in.
Some first-party cookies also help preserve guest browsing continuity so cart activity, delivery context, support requests, and guest order access can stay connected before an account is used.
If these cookies are blocked, some store features may stop working properly.
Cookies, sessions, and similar storage
This page uses the word "cookies" broadly. Some features may also rely on session identifiers, browser storage, or storage used by payment and sign-in services.
These tools help the storefront remember key information across pages and visits.
First-Party Use
What the storefront itself uses cookies for
The first-party cookie behavior visible today falls into a few clear buckets.
Cart continuity
A shopper can add products, leave a page, and continue browsing without rebuilding the cart from scratch. That continuity depends on a cart session identifier stored in a first-party cookie.
Guest browsing continuity
The storefront can keep one first-party guest visitor identity and one guest session so support requests, cart activity, browsing analytics, and guest order access can stay connected before an account is used.
Customer accounts
Signed-in sessions rely on a secure first-party authentication cookie so account pages, order history, and saved shopping features remain available between requests.
Vehicle and delivery context
The storefront can remember a selected year, make, and model while a customer browses products. It can also keep a confirmed delivery destination or rough guest delivery area so shipping estimates stay relevant between pages.
Authentication safety checks
A short-lived security cookie is used during Google sign-in to validate that the OAuth callback matches the sign-in request that started from the storefront.
Inventory
Current first-party cookie inventory
These are examples of the main first-party cookies and storage items used on the storefront today.
Cookie / storage item
cart_sid
Set by the cart API when a shopper starts a cart session. This cookie is not exposed to storefront JavaScript.
Purpose
Preserves cart state between requests so items remain in the shopper's cart.
Category
Essential commerce cookie
Typical duration
Up to 14 days
Access and security
HTTP-only, first-party cookie
SameSite=Lax
Cookie / storage item
onkar_guest_vid
Used only by Onkar Electronics to recognize the same browser over time and connect first-party analytics, support, and cart continuity without requiring an account.
Purpose
Keeps one first-party guest visitor identity in the browser so cart, browsing, support, and order context can stay connected between visits.
Category
Essential guest continuity cookie
Typical duration
Up to 90 days
Access and security
HTTP-only, first-party cookie
SameSite=Lax, Secure on the live site
Cookie / storage item
onkar_guest_sid
This session identifier refreshes as the storefront is used and helps distinguish one browsing session from a later return visit.
Purpose
Tracks the current guest browsing session so page views, cart actions, and checkout starts can be grouped into one visit.
Category
Essential session cookie
Typical duration
Up to 7 days
Access and security
HTTP-only, first-party cookie
SameSite=Lax, Secure on the live site
Cookie / storage item
vehicle_session
This cookie is readable on the client because the fitment UI needs the stored vehicle selection.
Purpose
Stores the selected year, make, and model so the storefront can keep fitment context during browsing.
Category
Preference / browsing-state cookie
Typical duration
Up to 30 days
Access and security
Browser-readable, first-party cookie
SameSite=Lax
Cookie / storage item
shipping_destination / shipping_guest_location
A confirmed postal code gives the firm estimate. A guest city/province guess may also be stored temporarily to improve delivery timing before postal code entry.
Purpose
Stores a confirmed delivery destination or a rough guest delivery area so shipping estimates can stay relevant between pages.
Category
Preference / browsing-state cookie
Typical duration
Short-lived to 30 days depending on source
Access and security
Browser-readable, first-party cookie
SameSite=Lax
Cookie / storage item
Customer session cookie
The exact cookie name is configured by environment variable rather than hard-coded, but the behavior is consistent across the account flow.
Purpose
Keeps authenticated customers signed in across account, wishlist, and order-related storefront pages.
Category
Essential authentication cookie
Typical duration
Until the configured session expiry
Access and security
HTTP-only, first-party cookie
SameSite=Lax, Secure on the live site
Cookie / storage item
onkar_google_oauth_state
Used only while a Google sign-in is in progress and cleared once the OAuth callback is processed.
Purpose
Temporarily validates the Google OAuth handoff and return path during account sign-in.
Category
Short-lived security cookie
Typical duration
Up to 10 minutes
Access and security
HTTP-only, first-party cookie
SameSite=Lax, Secure on the live site
Third-Party
Third-party services used during checkout and sign-in
Some parts of the shopping experience rely on third-party services that use their own cookies or browser storage.
Stripe checkout and payment handling
The checkout flow uses Stripe payment infrastructure. When a customer proceeds through payment, Stripe and related payment tooling may use their own cookies, scripts, or browser storage for payment confirmation, fraud prevention, and secure transaction handling.
Those Stripe-managed tools are separate from the storefront cookies listed above.
External authentication flows
If Google sign-in is used, both the storefront and Google's services can take part in the sign-in process.
That means customers may see a mix of storefront cookies and Google-managed storage during sign-in.
Controls
What customers can change and what may stop working
Browsers usually let customers clear, block, or limit cookies and site data. Those controls are useful, but they can also affect the storefront's core functionality.
Typical customer controls
- Clear existing cookies and site data for this storefront.
- Block all cookies or restrict them to first-party use only.
- Use private browsing modes that isolate or shorten stored state.
- Delete saved site data after each browsing session.
Likely effects of blocking storage
- Cart contents may not persist between pages or return visits.
- Signed-in sessions may not stay active.
- Vehicle fitment context may be lost and need to be reselected.
- Google sign-in or checkout flows may fail, reset, or require the customer to start again.
Cookie controls
You can manage cookies and site data through your browser settings.
Updates
How this policy stays current
We update this page when the storefront changes in ways that affect cookies or browser storage.
What may change
- The list of cookies and storage items used on the site.
- The third-party services involved in checkout, analytics, hosting, or sign-in.
- Any on-site cookie controls or preference tools added later.
- Any new embedded tools or personalization features.
Why this matters
This page is most useful when it reflects how the storefront actually works, so customers know what to expect.