Madhukosha
Consent Policy and Consent Notices
Operated by Madhukosha Apiary Services Private Limited
Effective 11 October 2026. Until then, version 1.0 applies.
This Consent Policy explains how Madhukosha Apiary Services Private Limited (“Madhukosha”, “we”, “us”) asks for, records, honours and withdraws consent under section 6 of the Digital Personal Data Protection Act, 2023 and Rule 3 of the Digital Personal Data Protection Rules, 2025. Part A is the standard that binds us. Part B contains the standalone Consent Notices we present at the point of collection. It forms part of, and must be read with, the Privacy Policy, the Cookie Policy and the Terms of Use.
Scope
- This Policy applies to every processing activity for which we rely on your consent. Processing that rests on a legitimate use under section 7 of the Act is described in the Privacy Policy and does not require your consent.
- We rely on consent for four things, and only these four: marketing and promotional messages; the inclusion of your contact details in advertising audiences; promotional push notifications; and analytics cookies on the website.
- Everything else rests on section 7(a) — the specified purpose for which you voluntarily provided the data. That includes registering your interest, recording the location of your farm or site, giving you a Registration ID, answering anything you write to us, verifying your mobile number, letting you see and delete your own registration, and sending you service messages about your registration or about a cluster forming in your area.
The Standard We Apply
- Free. No consent is a condition of anything. Registration and everything else on the Platform work with every optional box left blank.
- Specific — one consent, one purpose. We ask separately for each purpose, and we do not bundle two purposes under one box. In particular, consent to receive marketing messages from us is asked for separately from consent to place your contact details in an advertising audience, because those are different things with different consequences and a person may reasonably want one and not the other.
- Informed. The relevant Consent Notice in Part B is shown at or before the moment we ask.
- Unconditional and unambiguous, by clear affirmative action. An un-pre-ticked box, or a distinct selection on a banner or permission screen. Silence, inaction, scrolling, continued use and a pre-ticked box are not consent.
- Limited to what is necessary. We ask only for the data the stated purpose requires, and the consent extends no further.
- Withdrawable as easily as given. Every route in has a route out of no greater difficulty, and each consent may be withdrawn on its own without disturbing the others. We act within seven (7) days.
- Provable. Section 6(10) of the Act puts the burden of proving notice and consent on us. We therefore keep the consent record described in clause 5, and we do not activate any consent-based processing for a person whose consent record does not exist.
- No dark patterns. Accept and decline carry equal visual weight. Nothing is pre-selected. The decline path is never longer than the accept path. We do not repeat a request that has been declined in the same session, and we do not use confirmshaming language.
Where and How We Ask
| Consent | Where it appears | Mechanism | Notice |
|---|---|---|---|
| Marketing and promotional messages | On the registration form, in a block separated from the submit action | Its own un-pre-ticked box | Notice 2 |
| Advertising audiences | On the website registration form only, immediately below the marketing box | A second, separate un-pre-ticked box | Notice 3 |
| Promotional notifications | In the application, on first launch after registration, and in settings thereafter | A separate un-pre-ticked toggle, distinct from the operating system notification permission | Notice 4 |
| Analytics | A banner on the website on first visit, before any non-essential cookie is set | “Accept analytics” and “Reject” with equal prominence | Notice 5 |
- Advertising audiences are asked for on the website only. The applications do not ask for this consent, and the contact details of anyone who registers through an application are not placed in any advertising audience. If that ever changes, the applications will carry Notice 3 and this Policy will be republished first.
- Why marketing and advertising audiences are two boxes and not one. Receiving a message from us and having your mobile number and email address handed to an advertising platform are different acts with different consequences: the second is a disclosure to a third party which processes the data outside India for its own matching. A single box would mean that anyone who wanted to hear from us had also to accept that disclosure, which would make the second consent neither specific nor freely given; it would leave us unable to show which of the two a person actually agreed to; and it would make withdrawal incoherent, because unsubscribing from an email would have to withdraw the advertising consent as well.
- Push notifications — two different things. The operating system permission to show notifications is not consent under the Act; it is a device setting. Allowing notifications lets us send service messages about your registration or about a cluster forming near you, which rest on section 7(a). Promotional push is separate, needs the toggle in Notice 4, and is off unless you turn it on.
- One-time passwords are not marketing and need no consent. A one-time password sent to verify your number is a transactional message tied to the action you have just taken, and rests on section 7(a). At the point you enter your number we tell you: “We will send a one-time code to this number to verify it. Standard message charges may apply.” We do not use the verification channel to send anything promotional. Separately, our sending of SMS in India is subject to the telecom commercial-communication regime, including registration of our sender header and our message templates, and the scrubbing of promotional traffic against the preference register.
- No consent for children. The Platform is not directed at children and we do not process a child’s personal data, so we operate no verifiable parental consent flow. If any part of the Platform is ever directed at children, this Policy must be revised before that happens.
Withdrawal
| Consent | How to withdraw | Effect |
|---|---|---|
| Marketing messages | The unsubscribe link in any marketing email; reply STOP to any marketing SMS or WhatsApp message; or email us | We stop within seven (7) days. This does not by itself withdraw the advertising consent, which is separate — tell us if you want both stopped |
| Advertising audiences | Email us with the subject “Withdraw advertising consent” | Within seven (7) days we remove you from the audience lists we control and instruct the advertising platforms to delete you from theirs |
| Promotional notifications | Turn the toggle off in the application | Immediate. Service notifications continue |
| Analytics | “Manage preferences” on the banner, and clear cookies in your browser | Immediate for future collection |
- Every withdrawal may in every case be sent to hello@madhukosha.org. If you tell us to stop everything, we will treat that as withdrawing all of them, and confirm what we have done.
- Withdrawal does not affect the lawfulness of processing carried out before it.
- What withdrawal does not stop. Service messages about your registration, and messages telling you that a cluster is forming in your area, do not depend on consent and continue. If you no longer want those either, delete your registration in the application or ask us to delete it.
- The limit of withdrawal for advertising audiences. An advertising platform holds its own copy of an audience list. On withdrawal we remove you from the list we control and instruct the platform to delete you. We cannot guarantee the moment at which it acts, and we do not promise you that we can.
Consent Records We Keep
- For every consent given or withdrawn we record: the identifier (Registration ID, mobile number or email address); which consent it is; the version of the Consent Notice displayed; the date and time; the method; and, where applicable, the date, time and method of withdrawal.
- The consent record is kept separately from the record of acceptance of the Terms of Use. Accepting the Terms is not consent under the Act, and neither record substitutes for the other.
- Consent records are kept for as long as the consent stands and for three (3) years after withdrawal. They survive deletion of a registration, because they are the evidence of what was asked and what was answered.
- Operating rule. No consent-based processing is activated for any person unless the consent record for that specific purpose exists. In particular, no contact detail is placed in an advertising audience unless the record shows the advertising consent, taken on the website, with the Notice version and the timestamp — the marketing consent alone is not enough.
Review
- This Policy and the Notices in Part B are reviewed whenever a new purpose, provider, channel, application surface or advertising platform is introduced, and at least once every twelve (12) months.
- A new purpose requires a new Notice and fresh consent. Existing consents do not carry over to a new purpose.
PART B — CONSENT NOTICES
Each Notice below is presented independently of every other document and is understandable on its own, as Rule 3 of the Digital Personal Data Protection Rules, 2025 requires.
In every Notice: who is asking is Madhukosha Apiary Services Private Limited, #305, 1st Floor, Heritage Street, 6th Block, Banashankari 6th Stage, Bangalore, Karnataka 560060, India, hello@madhukosha.org; how to exercise your rights is to email hello@madhukosha.org with the subject “Data Principal Request”, quoting your Registration ID, to which we reply within thirty (30) days; and how to complain is to the Data Protection Board of India if our answer does not satisfy you.
Notice 1 — Your farm location
What this is. This is a notice, not a request for consent. Your farm location is required to register.
The data, itemised. Coordinates for your farm or site. We already have your pincode, from which we work out your district and State.
Why we need it. To judge whether registered farms are close enough together for a pollination cluster to be viable in your area, and, if you later take a service from us, to deliver it to the right place. A pincode is not precise enough for either.
How you can give it. By placing a pin on a map; by typing the name of a place, choosing from the results and confirming the position; or, if you allow it, by letting the application read your device’s location. You can refuse the device location permission and still register by placing the pin yourself.
What happens when you search for a place. The text you type is sent to our mapping provider’s places service so that it can return results. It goes through our own server, so the provider does not receive your device’s network address for that search. We store the location you then confirm. We do not store what you typed.
Who sees the location. Only Madhukosha and our records provider. It is never published, never shown on the Platform, and never shared with other users.
How long. Three years from your last contact with us, or until you delete your registration.
To remove it. Delete your registration in the application, or email hello@madhukosha.org. Your farm location is deleted with it.
Notice 2 — Marketing messages from Madhukosha
What we are asking for. Your permission to send you marketing and promotional messages.
The data, itemised. Your name; your mobile number; your email address.
What this enables. We may send you emails, messages and SMS about the PolliHab, about services as they become available, about seasonal pollination guidance and about offers.
What you get without ticking this. You will still receive messages about your own registration, and we will still tell you if a pollination cluster forms in your area. Those do not depend on this permission.
Who sees it. Madhukosha, our records provider and our messaging providers. Your data is not given to any advertising platform under this permission — that is a separate permission, in Notice 3.
How long. For as long as your permission stands. We keep a record of the permission itself for three years after you withdraw it.
To withdraw — as easily as you gave it. The unsubscribe link in any marketing email; reply STOP to any marketing SMS or message; or email hello@madhukosha.org. We stop within seven days.
☐ I agree that Madhukosha may send me marketing and promotional messages. This box is not pre-ticked. Leaving it blank does not affect your registration.
Notice 3 — Advertising audiences
This Notice appears on the website registration form only. The applications do not ask for this permission.
What we are asking for. Your permission to give your contact details to Meta and Google so that they can show you Madhukosha advertising.
The data, itemised. Your mobile number; your email address.
What this enables. We may upload your mobile number and email address to Meta and to Google, so that those companies can match you to their own users, show you Madhukosha advertising, and find other people similar to you to show it to.
This is a disclosure to other companies, and outside India. Your mobile number and email address are transferred to Meta and Google, which process data in the United States and Ireland. Once they hold a copy we cannot control what they retain, beyond instructing them to delete you when you withdraw.
This is a separate permission from Notice 2. You may agree to marketing messages and refuse this; you may agree to this and refuse marketing messages; or you may refuse both. Refusing either has no effect on your registration.
How long. For as long as your permission stands. We keep a record of the permission itself for three years after you withdraw it.
To withdraw. Email hello@madhukosha.org with the subject “Withdraw advertising consent”. Within seven days we remove you from the lists we control and instruct Meta and Google to delete you from theirs. We cannot guarantee when they will act, and we do not promise that we can.
☐ I agree that Madhukosha may give my mobile number and email address to Meta and Google for advertising audience targeting, as described above. This box is not pre-ticked and is separate from the box in Notice 2.
Notice 4 — Promotional notifications
What we are asking for. Your permission to send you promotional notifications on your phone.
The data, itemised. The push token your device issues, and your notification preference.
What this is, and is not. This covers promotional notifications — offers, new services, general updates. It does not cover service notifications about your own registration or about a cluster forming in your area, which we send regardless and which you can stop by turning notifications off in your device settings.
Who sees it. Our notification providers for Android and iOS, in the United States.
To withdraw. Turn the promotional toggle off in the application. It takes effect immediately.
☐ Send me promotional notifications. This toggle is off unless you turn it on.
Notice 5 — Analytics
What we are asking for. Your permission to measure how the website is used.
The data, itemised. Your network address, device and browser information, the pages you view, where you arrived from, and the date and time — collected through cookies on the website.
Why. To see what people use and what they do not, so that we can decide what to improve. We do not use it to identify you personally and we do not build a profile of you.
Who sees it. Our analytics provider, in the United States.
How long. No more than fourteen months.
Strictly necessary cookies are different. Those keep the Platform working and secure, are limited to what that requires, and are set without consent. The Cookie Policy lists them.
☐ Accept analytics ☐ Reject Both choices are shown with equal prominence, and neither is pre-selected.



