Cookie notice

This page is written for karanjotfootwear at karanjotfootwear.site. It was prepared for this storefront on 11 November 2026. It is a shopper-facing explanation, not a certificate and not a lawyer’s opinion. Where a live business detail is still missing, the page says so in plain words.

What this notice means by cookies

Visitors talk about cookies when they mean small files a site leaves behind. On karanjotfootwear.site, the shop you are using stores its cart, account, wishlist, orders, and contact notes in the browser’s local storage, and it stores an offer code in session storage. Those are not images, and they are not advertising cookies. This notice uses the word cookie in the broad sense a shopper expects, and then it names the actual storage, so you are not left looking for a banner that loads a tracker.

karanjotfootwear does not set a third-party analytics cookie, a social plugin, or a retargeting file. There is no social-media logo and no social-media list on the pages. There is no scan-to-pay code. A search of the site files should not find a payment barcode. If you see one, it is not part of this storefront and you should not scan it.

Your browser may still keep its own settings, such as a language or a password manager you installed. Those belong to the browser, not to a script we wrote. This notice covers what the shop’s own pages write.

The records the pages write

The cart record holds product handles, size labels, and quantities. It is written when you add a pair, change a quantity, or remove a line, and it is read when the header count updates or the cart page opens. It survives a refresh. It is the reason a pair is still in the cart after you close the tab and come back on the same browser.

The account list holds the name, email, password, and optional phone number you saved. The session record holds the name, email, and phone of the person who is logged in. Logout removes the session record only. The wishlist holds product handles you marked with the heart. The order list holds confirmations you placed. The message list holds contact-form notes. The offer code sits in session storage so checkout can show the same ten percent line the cart showed.

Search queries can sit in the address bar of the search page because you submitted them. That is a URL on your device, not a cookie we share. The header search suggestions are calculated from the catalogue that shipped with the page. They do not call an outside search engine.

What we do not write

We do not write a cookie that follows you to other websites. We do not embed a video host that sets its own cookies. The watch-before-you-buy control opens a photograph that is already part of the site. We do not load a font from a third-party font service at browse time. The typefaces used for headings and body text are files stored with the site.

We do not store card numbers, UPI PINs, or bank passwords, because the checkout page does not ask for them. If you type those secrets into a comment box, you are placing them into the contact note yourself. Please do not. The note is local, but it is still the wrong place for a secret.

We do not use storage to decide a personalised price. Everyone sees the same selling price for a style. The ten percent offer depends on the cart quantity or on PAIR10, not on a hidden profile.

How long the records last

Local storage lasts until you delete the site data, until the shop’s script removes a particular record, or until the browser evicts it. Session storage for the offer code is meant to last for the browsing session and may disappear when the session ends. The cart is deliberately in local storage so a refresh does not empty it. Orders remain in local storage so the account page can list them.

You can remove a cart line without clearing everything. You can turn a wishlist heart off. You can log out. You cannot, from a shop button, delete the whole account. Clearing site data for this origin is the thorough reset. It removes orders as well. Copy any order id you still need before you do that.

We do not keep a second copy on a server. A cookie notice that promised a one-year server log would be describing a different shop. This one does not have that log.

Your choices

You can browse the catalogue, the size chart, and the policy pages without creating an account and without adding a pair to the cart. In that case the shop still loads its pages, but it does not need to store an order. If you add a pair, you are asking the page to remember it. That is the storage’s purpose. If you do not want a cart remembered, do not add a pair, or clear the site data afterwards.

You can refuse to register. Placing an order asks you to log in so the order can be tied to an email on this device. If you do not want an account record, do not place the order. There is no guest-checkout path that writes an order without a session. The login step is deliberate.

Browser controls that block all storage may stop the cart, the login, and the contact confirmation from working. The pages are built to use that storage. If you block it, the catalogue can still be read, and the interactive shop will not remember you. That is a fair trade if it is the trade you want.

Similar technologies

The pages use ordinary JavaScript to open the menu, the search panel, the account menu, and the image preview. They use the address bar to pass a search phrase or an order id. They do not use a hidden pixel. They do not fingerprint a canvas to identify you across sites. A decorative effect is not part of this shop’s design. The layout is a straightforward storefront.

The announcement strips rotate text that is written into the page. They do not record which slide you paused on. Size buttons and quantity fields change the product form on the page. The chosen size is stored only when you add the pair to the cart.

If a later version of the shop adds a measurement tool or a chat service, that version needs a new notice before it loads. This notice would be incomplete if those tools appeared silently. They are not in this version.

Children

The storage is for the adult who is shopping. Do not type a child’s school, health information, or full date of birth into the address or the comment. A size band is enough for the order. The shop does not need a child profile, and it does not create one in storage.

Product photographs are not cookies. They do not become more identifying because a browser cached the image file. Clearing the browser cache removes cached images. Clearing site data removes the records described above. They are different controls in most browsers.

Changes and contact

If karanjotfootwear starts using a real analytics tool, a real payment page, or a real support chat, this notice has to name it before it runs. The commercial rules of the shop — free shipping, the seven-day unworn window, the ten percent offer, cancellation before dispatch — are not cookie rules. They live on the other policy pages. This page should not be read as changing them.

Questions can go through the contact form on karanjotfootwear.site. The reply channel is still a sample storefront detail. Nothing in this notice claims a certification, a seal, or a registration with a regulator. It describes the storage this storefront actually uses.

The header cart count, the account menu, and the heart on a product card are the visible signs that storage is in use. They update from the records named above. They do not phone home. A refresh is a good test: the count you saw before the refresh should be the count you see after it, as long as you did not clear site data and did not remove the line. If the count returns to zero after a refresh, storage is blocked or the browser is dropping it. In that case the interactive parts of the shop cannot keep a cart, and the honest result is to browse without relying on a saved bag.

Offer memory is narrower than cart memory. PAIR10 typed on the cart page is kept for the session so the checkout summary can show the same ten percent, rounded to the nearest rupee. Closing the session may drop the code even though the pairs remain in the cart. The two-pair offer does not need the code. It is recalculated from quantities whenever the cart or the checkout summary is drawn. That is why a second pair changes the total even if you never typed PAIR10, and why removing the second pair removes the offer. None of that calculation is sent to an advertising network.

If you copy a product link to send to another adult in the family, you are sharing a page address, not a cookie. The other person does not inherit your cart. Their browser starts empty unless they add a pair themselves. That separation is useful on a shared tablet: log out when you finish, and expect the cart to be visible to the next person until it is cleared, because the cart is stored for the browser profile rather than for a password-protected server account.