# Privacy Policy Version: 0.2-review Last updated: 2026-10-07 Effective date: [Approved effective date — to be confirmed] REVIEW DRAFT — NOT A FINAL POLICY. Unconfirmed placeholders require completion before public launch. ## 1. Who we are and how to contact us The Kisan Farm is the trading name used by this application. Legal seller: [Legal seller / owner name — to be confirmed]. Business address: [Complete business address — to be confirmed]. Our website is https://thekisanfarm.com. Privacy contact: [Working privacy email — to be confirmed]. Grievance Officer and contact details are listed in Business and Grievance Contacts. ## 2. What this policy covers This policy explains how we handle personal information when you visit our website, create or use an account, check delivery availability, place an order, make a payment or contact us. It also explains your choices and how to raise a privacy concern. External services, such as Google sign-in and your chosen bank or UPI application, also have their own privacy notices covering their activities. ## 3. Information we collect We collect information you provide, records generated through the service and information supplied by authentication or location providers. Passwords are stored as salted scrypt hashes. Google customer sign-in does not grant access to your Gmail inbox; outgoing verification email uses a separate sender account. We do not collect UPI PINs, bank passwords, card numbers or CVVs through checkout. Category | Information and purpose Account and verification | Name, email, delivery mobile, password hashes, email verification records/attempts and linked identities; to manage and secure account access. Google sign-in | Google identifier, name, email, verification status and profile picture URL; to authenticate/link an account. Delivery and serviceability | Address lines, city, PIN code, optional landmark, coordinates and boundary-check results; to assess eligibility and fulfil orders. Cart and orders | Items, kilograms, stock reservations, price totals, saved delivery dates and immutable order address/item snapshots; to process orders. Payments | Order-linked UPI URI/QR, payment status and administrator-entered bank reference/review notes; to reconcile transfers manually. Customer checkout currently submits a payment acknowledgement, not a payment-reference or screenshot upload. Security and support | Session identifiers, user-agent/device labels, hashed IP-related security identifiers, timestamps, audit events and request information shared through confirmed support channels. ## 4. Why we use your information • Create, verify and manage your account; authenticate access and prevent misuse. • Maintain your cart, reserve stock, check delivery availability and fulfil orders. • Send verification emails and communications about purchases or delivery. • Reconcile payments and administer cancellations or refunds. • Respond to enquiries, complaints and privacy requests. • Investigate fraud, security incidents and operational problems. • Maintain records needed for accounting, applicable law and dispute resolution. ## 5. Your choices and consent Providing information needed for a requested function is necessary for that function: for example, a verified email for ordering and an address/contact number for delivery. Viewing a policy is not blanket consent to unrelated processing. Withdrawal or questions may be sent to [Working privacy email — to be confirmed] once that channel is confirmed. The current application sends email verification and recovery codes. It has no implemented promotional subscription, SMS OTP delivery or WhatsApp order/update service. Any future marketing requires separate, appropriate choices and a working opt-out. ## 6. Who receives your information Authorised administrators can access relevant order and customer details. The reported deployment uses Hostinger hosting and MySQL; outgoing verification emails use a configured Gmail/Google SMTP sender with OAuth2. Google customer sign-in is optional. Address checks can use Google Maps Geocoding and Nominatim, depending on configuration and fallback behavior. Banks/UPI apps process the transfer outside the website. Delivery operator: [Delivery team / logistics provider — to be confirmed]. Hosting/database/backup regions: [Provider processing regions and safeguards — to be confirmed]. Business practices concerning sale, advertising or unrelated sharing: [Business data-sharing practices — to be confirmed]. Provider contracts and any required safeguards must be confirmed before final publication. ## 7. Delivery addresses and location The server can send address line 1, optional line 2, city and PIN code to a geocoding provider. The current Nominatim path sends the assembled address as a search query to its configured endpoint; a Google-primary setup can fall back to Nominatim. Coordinates/results are used to assess the Bengaluru boundary and may be cached. Browser device-location permission is not requested by the current application. This implementation needs provider-policy review and correction before public launch; naming a provider here does not make restricted use acceptable. Do not put unnecessary sensitive information in address fields. ## 8. Cookies and browser storage The application uses cookies, local storage and session storage for carts, customer/admin authentication, Google callback security and navigation/checkout continuity. Some authentication tokens are script-readable in local storage even though corresponding cookies are HttpOnly. Expiry of a server session does not prove browser or database deletion. See Cookie and Browser Storage Policy for the inventory. No analytics or advertising SDK or optional-cookie preference mechanism was found in application source. Deployed hosting/CDN injections and actual cookie attributes still require verification. ## 9. How long we keep information Approved category-specific retention and purge periods: [Category-specific retention and purge schedule — to be confirmed]. The code expires access codes, sessions and reservations, but this does not automatically erase their records. No complete account-erasure or backup-deletion workflow is implemented. Deactivation disables account access and releases active cart holds while retaining historical orders, payments and other stored information. Order snapshots are not overwritten when profile details change. Backup rotation/restore handling: [Backup retention and restore handling — to be confirmed]. Retention reasons and any limitations must be explained when handling requests. ## 10. Privacy requests and account closure Signed-in customers can update their name, verify/change contact details, manage saved addresses and deactivate their account through Profile & Security. Deactivation also revokes sessions; it is not erasure. Requests for correction, deletion or withdrawal may be sent to [Working privacy email — to be confirmed] once the channel is confirmed. No self-service erasure request submission is currently implemented. Request owner, proportionate identity checks, tracking and legal response deadlines: [Privacy request ownership and response procedure — to be confirmed]. Do not send passwords, bank OTPs, UPI PINs or unnecessary identity-document copies. Historic transaction records may require retention or an accompanying correction rather than silent rewriting. ## 11. Security and incidents Implemented source safeguards include salted scrypt password hashes, hashed session/OTP tokens, verification-attempt limits, session revocation and separate administrator/customer permissions. Gmail SMTP enforces TLS. These facts are not a claim that deployed HTTPS, backups or all organisational safeguards have been independently verified. No system guarantees absolute security. Operational incident handling and legally required notifications: [Incident response procedure — to be confirmed]. ## 12. Processing outside India Hosting, database, email, geocoding and backup processing locations and applicable cross-border safeguards: [Provider processing regions and safeguards — to be confirmed]. Do not assume that all providers process data only within India. ## 13. Children Adult/child eligibility and any appropriate consent or age-control process: [Approved age eligibility and controls — to be confirmed]. No age field or age-verification gate is currently implemented. A final adult-only or child-data statement must match the approved business rule and working controls. Privacy concerns can be raised through the contact directory once its details are confirmed. ## 14. Complaints and policy updates Privacy grievance owner and applicable response process: [Privacy request ownership and response procedure — to be confirmed]. Consumer grievance handling is described separately in the contact directory. We do not treat a privacy request as automatically subject to a consumer-complaint timetable. The policy version and last-updated date are shown on this page. Effective date: [Approved effective date — to be confirmed]. Any material new processing must be reviewed, communicated and supported by appropriate consent where required. Mandatory rights are not reduced by policy wording.