Data protection 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.

How to read this page

This is a data-protection notice for the karanjotfootwear storefront at karanjotfootwear.site. It explains, in plain language, how a browser-only shop treats personal information. It is not a claim of certified compliance. It is not a seal, an audit letter, or a registration number. The page exists because shoppers ask what happens to a name, an email, a phone number, and an address. The honest answer is that those fields stay on the device unless and until the operator connects a service, which this version does not do.

European data-protection law uses words such as controller, processor, and lawful basis. Indian shoppers are the people this store is built for, and deliveries are inside India. Some visitors still want those words mapped to what the site does. The mapping below is descriptive. It is not a statement that a regulator has approved the shop. Where the operator has not confirmed a registered office, this page says sample storefront detail instead of inventing one.

The cookie notice describes the storage keys. The privacy notice describes the same practices at greater length for a general reader. This page focuses on purpose, choice, and the limits of a frontend shop. The commercial rules — rupee prices, free shipping, three to seven working days after dispatch, a seven-day unworn return or size exchange, a ten percent offer, cancellation before dispatch — are not changed by this notice. They stay aligned with the other policy pages.

Who decides the purposes

karanjotfootwear, as the operator of karanjotfootwear.site, decides why the pages ask for a name and an address: to remember a cart, to keep an account on the device, and to record an order the shopper chose to place. There is no separate processor taking those fields to a server, because there is no server in this storefront. A future courier or a future mailbox would be a processor or a separate controller for the fields they actually receive. They are not appointed yet. Naming them would be a fiction.

The operator has not supplied a street address, a telephone number, or a monitored email. The footer marks that gap as a sample storefront detail. A data-protection contact must be a real channel. Until it is confirmed, the contact form stores your note locally and tells you so. Do not send identity documents to it.

If you use a shared device, you and the other people who know the password of that device can read the same local records. The shop cannot distinguish you from them. That is a reason to log out and, on a public computer, to clear site data after you finish.

The information and why it is there

Account fields identify the session on this browser so the account page can show the right orders. Checkout fields identify the recipient and the place a parcel should go, once a parcel is real. The mobile number is there so a courier can call about a gate or a missed attempt. The email is there so an order can be matched to a session and, later, so a person could write about that order. The contact comment is there so you can ask for a return, an exchange, or a cancellation with an order id.

The cart and wishlist are there so the shop remembers what you selected. They are not there to score your household or to set a different price. Order records are there so the confirmation can be opened again on the same browser. Offer codes are there so the ten percent line is stable between the cart and the checkout summary.

We do not ask for a government identity number, a child’s date of birth, a health condition, or a payment-card number. Please do not add those to the address line. A size band and a foot length from the chart are enough to choose a pair. The shoes are not a medical device, and the forms are not a clinic record.

Choice and the logged-in order

You can read the catalogue without an account. You can leave the site and clear storage. Placing an order is optional, and it asks you to log in first when you are signed out. That step is how the shop avoids writing an order that has no email on the device. If you do not want an account stored, do not complete registration. The forms show errors when a field is missing or mistyped. They do not hide extra required fields.

Forgot-password works only for an email that already exists on this device, and it lets you set a new password locally. It is not an email reset link. Registration rejects a second account with the same email on this device. Those are form rules, not a national identity check.

You may ask, in the contact form, for a note about your order. On this version the practical way to erase the account, the orders, and the notes is to clear site data for this origin. There is no server copy for us to delete. A right of access is met, today, by looking at the account page and the cart while you are on the device. We cannot produce a portable file from a data centre we do not run.

Sharing and transfers

The pages do not transfer your fields to another country, to an advertising network, or to a payment company, because they do not transmit the order at all. A sync feature in your own browser, if you turned it on, is your browser’s feature. Consider turning sync off on a computer you do not control.

We do not sell local records. We do not share them with a social network. There is no social login. Product brands and style names that appear on the catalogue are names of goods, not recipients of your address.

When a courier is eventually appointed, the recipient name, address, PIN, and phone number will need to be shared with that courier for the pairs you still want delivered. That sharing is not switched on here. The shipping policy says the operator must confirm the courier first. The same is true of a mailbox that would receive your contact notes. This page should be updated at that moment, before the first real transfer, to name the recipient of the data and the purpose.

Keeping and securing the records

The records remain in the browser until you or the script removes them. That may be longer than a shop with a server retention schedule would keep a card token. The difference is that the record is on your device. You control the retention by clearing it. We do not promise a 30-day server deletion, because that promise would invent a server.

The password is not hashed. That is a weakness of a frontend demonstration, and it is stated on the privacy page as well. Do not reuse an important password. Do not use this account system as if it had been audited. Nobody has issued a certificate for it. A public computer is the wrong place to type even a casual password.

Order ids, totals, and addresses sit beside the account. Anyone who can open the browser profile can read them. Use the device lock your operating system provides. We cannot add a lock the operating system does not have.

Children’s information

The buyer should be an adult. The products are for small feet. A photograph of a child in a catalogue is not a customer file. Do not submit a child’s sensitive information in a form that asks only for a delivery address and a shoe size. If you believe a comment accidentally includes more than a delivery needs, clear the site data. There is no separate children’s database to update.

Age bands on the size chart are fitting labels. They are not a record that a particular child is two years old. The shop does not build a profile from them.

Complaints, changes, and the boundary of this notice

If you are unhappy with how the device stores an order, start with the contact form and with clearing site data if you want the record gone. A formal complaint to a regulator is your own step, and this page does not pretend to be the regulator’s form. We also do not pretend that a certificate has been granted. Words like compliant, certified, or approved are the wrong words for this storefront, and we do not use them as a claim.

We will revise this notice if data starts to leave the browser, if the offer or the return window changes, or if a real privacy contact is confirmed. The commercial pages must be revised in the same pass so the seven-day window, the free Indian shipping aim, the ten percent offer, and the cancellation-before-dispatch rule do not diverge. The date to read with this wording is 11 November 2026.

Business details that still need confirmation are the registered contact, the packing address, the courier, the doorstep collection method for cash and for UPI, and whether any outside firm will ever hold a copy of an order. Until those are confirmed, karanjotfootwear will not print a fictional office on karanjotfootwear.site in order to look complete.