Privacy
We collect what it takes to post you a parcel. Not much else.
One advertising pixel, no analytics suite, no newsletter you didn't ask for. This page is short because there isn't much to say.
Last updated 19 August 2026
In one paragraph. We collect your name, address, phone and email so we can deliver your order, and we share those with the courier and with Razorpay. We run the Meta Pixel, which sets a cookie and tells Meta which pages you viewed and whether you bought — you can switch it off, and we explain how below. We never see your card details, and your cart lives in your own browser, not on our server.
What we collect
- Order details — your name, delivery address, phone number, email address, and what you bought.
- Correspondence — anything you send us by email, including photos attached to a refund claim.
- Payment confirmation from Razorpay: whether a payment succeeded, the amount, and a transaction reference.
- Pixel data — the Meta Pixel records the pages you view on this site and the value of any order you place, and sends that to Meta. We see it only as aggregate numbers in the ad tools; we can't identify you from it.
What we don't collect
- Your card, UPI or netbanking details. These go directly to Razorpay and never touch our servers. We couldn't see them if we wanted to.
- Analytics. There is no Google Analytics or equivalent on this site.
- Anything you type other than what you enter at checkout. The pixel records pages viewed and purchase value, not form contents.
The Meta Pixel, and how to turn it off
We run Meta's advertising pixel so we can tell whether our ads are working. It sets a cookie in your browser and reports to Meta which of our pages you looked at, and the value of an order if you place one.
If you'd rather it didn't: use your browser's tracker blocking (Safari and Firefox block it by default), any ad blocker, or Meta's own ad preferences. Nothing on this site depends on it — the shop and checkout work identically with it blocked.
Your cart is stored in your browser's own local storage so it survives you moving between pages. It stays on your device and is never sent to us until you check out. Clearing your browser data clears it.
Why we have it, and for how long
We use your details to process and deliver your order, to contact you about it, and to handle any refund or replacement. We keep order records as long as tax and accounting law requires, and correspondence for as long as it's useful to resolve a query.
We do not sell your data. We do not share it for advertising. We won't email you marketing unless you separately ask us to.
Who else sees it
- Our courier — your name, address and phone, because a parcel can't be delivered without them.
- Razorpay — to take the payment and issue any refund. Razorpay has its own privacy policy governing what it does with that.
- Meta — pixel data only, as described above. Never your name, address or order contents.
- Anyone we're legally required to disclose to, such as a tax authority or a court order.
That's the complete list.
Security
The site is served over HTTPS. Order data is kept on access-controlled systems. No system is perfect, and we won't pretend otherwise — but the most sensitive thing in a transaction, your payment credentials, is one thing we deliberately never hold.
Your rights
You can ask us to show you what we hold about you, correct it, or delete it. Write to the grievance officer below and we'll respond within 30 days. Where we're required to keep a record for tax purposes we'll tell you, and delete the rest.
Children
This site isn't directed at children, and we don't knowingly collect data from anyone under 18.
Grievance officer
As required under India's Information Technology Rules and the Digital Personal Data Protection Act:
- Name: The Grievance Officer, Jaggu Jaggery Co
- Email: jaggusjaggery@gmail.com
- Address: Mesa School of Business, WeWork Bannerghatta, Arekere Main Rd, Bangalore – 560076, Karnataka, India
Changes
If we add anything — analytics, a newsletter, a chat widget — we'll update this page and change the date at the top before it goes live, not after.