What we collect
The information needed to run the store, process orders, and support your account.
Policy
Privacy Policy
This page explains what information Onkar Electronics uses to run the storefront, complete checkout, fulfill orders, support customer accounts, and improve search and catalog browsing.
Need help?
If you have questions about how your information is handled, please use our contact page and we will help.
Last updated March 16, 2026Canada storefront context
How we use it
Checkout, shipping, account access, support, and improving how the store works.
When we share it
With payment, shipping, hosting, and support partners when needed to operate the store.
Questions about privacy?
If you need help with privacy-related questions, contact us through the support page.
Overview
How we approach privacy
We collect the information needed to run the store, complete orders, support your account, and help you shop with confidence.
Information used to run the store
We collect information where it is needed to run the store, including cart activity, checkout details, account access, saved addresses, order history, wishlist activity, and site performance monitoring.
This page explains the main types of information used across the Onkar Electronics storefront in plain language.
Questions about your information
If you need help with a privacy-related question or request, contact us and we will assist you.
We aim to keep this page clear and up to date so you know what information is used and why.
Collection
What information may be collected
Different parts of the storefront collect different categories of information depending on what the customer chooses to do.
Information you provide directly
- Name, email address, phone number, and marketing preference submitted through checkout or account flows.
- Shipping-address details, saved-address labels, and contact information used to create and fulfill orders.
- Account profile edits, sign-in details, wishlist activity, and order-history interactions when an account is used.
Shopping and browsing signals
- Search queries, opened searches, viewed results, clicked results, page visits, product interactions, cart actions, and wishlist saves.
- Vehicle-selection or fitment context used to make browsing more relevant where fitment-aware shopping is enabled.
- Session identifiers and first-party guest visitor records used to preserve cart contents, storefront state, guest order/support continuity, and similar short-term browsing context.
Checkout and order records
- Order totals, line items, shipping charges, tax calculations, payment status, fulfillment status, and shipment/tracking records tied to an order.
- Checkout uses Stripe for payment confirmation. The storefront receives order and payment-intent status data needed to complete the purchase flow, rather than collecting raw card details directly in storefront forms.
Technical and operational information
- Browser storage and session cookies used for cart state, selected vehicle context, delivery estimates, guest sessions, account sessions, and similar operational behavior.
- Error, reliability, cart-recovery, and operational event data used to debug issues, monitor storefront stability, understand first-party shopping behavior, and reduce misuse.
Use
How information may be used
The information above is used to run the store and improve the shopping experience around real storefront tasks.
Core business and storefront uses
- Process checkout, create orders, calculate shipping and tax, confirm payment status, and support fulfillment.
- Maintain customer accounts, saved shipping addresses, wishlist state, and order history.
- Preserve guest continuity for carts, delivery estimates, guest order access, and support context before an account is used.
- Improve search relevance, product discovery, navigation paths, and merchandising decisions based on how customers use the catalog.
- Monitor for instability, misuse, fraud risk, operational problems, and abandoned-cart activity that could affect transactions or storefront availability.
- Keep records related to orders, support cases, payments, fulfillment, bookkeeping, and store operations.
Retention
Retention, access, and safeguards
Different records have different lifespans. Order and compliance records generally need to last longer than short-term session or browsing context.
Retention approach
- Order, shipping, payment-status, and accounting-related records may be retained as long as reasonably needed for fulfillment, support, bookkeeping, tax, fraud review, and legal obligations.
- Session and browsing data may be shorter-lived when it is only needed for storefront operation, guest continuity, cart recovery review, or analytics review.
- Retention periods can vary based on legal, tax, payment, and customer-service requirements.
Safeguards
- The storefront is designed so access to operational data is limited to the systems and personnel who need it to run checkout, support customers, or manage fulfillment.
- Payment collection is routed through Stripe-hosted payment tooling, and the storefront code focuses on payment-intent status rather than raw card data capture.
- Administrative access, session handling, and operational logging are used to support accountability and store reliability.
Choices
Customer choices, related policies, and future updates
Customers should be able to understand how the site works, adjust what they can control, and see when the notice changes.
Practical choices available now
- Marketing consent can be managed in the flows where it is explicitly requested.
- Browser cookie and storage controls can be managed through the browser, although some core storefront features may stop working properly if all storage is blocked.
- Signed-in customers can review account profile details, saved addresses, orders, and wishlist information through the account area.
Updates to this policy
We may update this policy when checkout, account features, shipping operations, or service partners change.
The date at the top of this page shows the latest revision.