Privacy Policy

2. Information we currently handle

• Account and identity information: first and last name, email address, sign-in identifier and an optional phone number when you use available account services.
• Authentication information: passwords submitted for registration, sign-in or password reset, together with essential security and session records. Readable passwords are not placed in the browser-local cart or wishlist and are not stored in Vruddhi.Store session records.
• Cart and product information: product identifiers, selected options, quantities, prices and cart reconciliation results needed to display and prepare the current cart.
• Checkout and delivery information: name, email address, phone number, billing or delivery address, selected shipping information and confirmed totals when the relevant checkout step is used.
• Order information: order number, products, amounts, address and fulfilment status where an existing order is available through account services.
• Support information: information you choose to send by email, which may include an order number, product details, a description of the issue and supporting photographs or videos.
• Vendor enquiry information: full name, business name, mobile number, email address, city or state, business type, product category and a product description if you attempt to use the online vendor form.
• Technical and security information: limited request, network-source, session, rate-limit and service-event metadata needed to operate and protect available services.

The online vendor-enquiry delivery service is not currently connected. Submitted fields are validated for the request, but the form reports that the details were not sent and does not accept them as a delivered enquiry.

3. Information we do not currently require

For an ordinary customer journey, Vruddhi.Store does not intentionally ask for:

• date of birth or gender;
• precise device location;
• government identity documents;
• GST or other business-registration details; or
• a separate convenience-only address book.

Billing or delivery details may still be associated with customer or order records where account or order services are used. The wishlist is not maintained as a server-side customer profile; the browser may send selected product identifiers to retrieve current catalogue information when the wishlist is displayed.

4. How we use information

• to provide catalogue, cart, wishlist and available account functions;
• to authenticate customers, protect sessions, limit abuse and support password recovery;
• to reconcile current product facts and prepare shipping, tax and payable information;
• to display existing customer and order information to the authenticated customer;
• to respond to support, grievance and legal requests;
• to send service messages when transactional email is configured; and
• to diagnose failures, maintain security and comply with applicable law.

We do not use the audited storefront to build a deliberate server-side browsing or search-history profile for recommendations.

5. Cart, wishlist, search and browser storage

The current cart and wishlist are saved in local storage in your browser so that they can remain available on that device. Stored cart data is limited to product snapshots, options, quantities and selection state; stored wishlist data is limited to product identifiers. It does not include account passwords, checkout contact details, delivery addresses, payment credentials or order records.

Cart facts are sent to Vruddhi.Store servers to retrieve current catalogue data, reconcile the cart and, where available, prepare checkout. Wishlist product identifiers may be sent to retrieve current product facts. Search text is used for the current search request and may appear in the page URL, but the application does not deliberately persist it as a customer search-history profile. No recently viewed history is currently maintained.

You can clear this browser data using your browser controls, but doing so will remove the saved cart and wishlist from that browser.

6. Essential cookies and session technology

Vruddhi.Store uses essential, security-focused cookies when account or checkout services are available. These support pre-authentication protection, authenticated sessions and a secure checkout connection. The account and checkout cookies are HTTP-only and do not intentionally contain readable profile, address, password or payment information.

Current application limits allow an authenticated session to last no more than seven days and expire after twelve hours of inactivity. The checkout-session cookie has a maximum life of two hours. Security metadata may be retained until an associated password-reset or revocation state is safely resolved. Blocking essential cookies can prevent sign-in or checkout preparation from working.

7. Accounts and authentication

When account services are configured, customer identity and profile data are processed through the store account system. Server-issued session authority, rather than a customer identifier supplied by the browser, controls access to profile, address and order information. Password-reset links are time-limited, and existing sessions may be revoked following a password change.

If an account or transactional-email feature is unavailable, merely visiting the website does not cause you to use that feature.

8. Orders, billing and delivery addresses

The checkout interface asks for contact and delivery details needed to prepare delivery and shipping information. These form values are kept in the active checkout interface and are not added to the browser-local cart or wishlist. Delivery details may be sent to the store platform to calculate shipping when that function is available.

The current storefront does not execute payments or create WooCommerce orders. When order creation is activated in the future, the policy will be reviewed before activation. Existing WooCommerce customer or order records may still be displayed through configured account services and may contain billing, delivery and fulfilment information.

9. Payments

Payment execution is not active in the current storefront. Vruddhi.Store therefore does not currently collect or process payment-card or payment-account credentials through this website. A future payment service would process its required payment information under its own privacy terms, and this policy must be updated before that service is enabled. No payment provider is identified here because none is currently active.

10. Service providers and sharing

We may disclose only the information reasonably necessary to:

• website hosting and security services that receive and protect requests;
• the WordPress and WooCommerce store/account platform where those services are configured;
• transactional-email services when customer service email is configured;
• delivery, logistics or payment providers only when the relevant commerce service is activated; and
• regulators, courts or other parties where disclosure is required by law or needed to protect legal rights.

We do not sell customer personal information. A service is treated as a recipient only when it is configured and used for the relevant feature.

11. Analytics, advertising and marketing

Vruddhi.Store does not currently include a web analytics SDK, advertising pixel, behavioural-advertising tracker or deliberate customer-profiling system. We also found no active customer-marketing subscription flow in the storefront. Ordinary hosting, network and security systems may still process technical request records needed to deliver and protect the service.

If analytics, advertising or marketing tools are introduced, this policy and any required consent controls must be updated before they are used.

12. Retention

We retain personal information only for as long as reasonably necessary for the purpose for which it was handled, to maintain account and security integrity, to resolve support matters, or to meet legal, tax, accounting and consumer-protection obligations. Browser-local cart and wishlist data remains until you change it, clear the site data or the browser removes it.

Account, order and support retention can depend on the configured service and applicable legal duties. The unconnected online vendor form has no configured delivery destination that accepts or persists an enquiry. Hosting and security services may retain operational request records according to their configured retention settings and applicable legal or operational needs. We do not claim a shorter deletion period where the current implementation or law does not establish one.

13. Security

Vruddhi.Store uses safeguards including server-side authorization, HTTP-only and secure production cookies, same-origin and request-forgery controls, bounded request validation, rate limiting, restricted server credentials and fail-closed behavior for unavailable security services. No internet service can guarantee absolute security.

Please do not send passwords, payment credentials, government identity documents or other unnecessary sensitive information by email.

14. Your choices and requests

• You can clear browser-local cart and wishlist data through your browser settings.
• You can review or correct available profile and address information through authenticated account services.
• You may contact us to ask about access, correction or deletion of personal information, subject to identity verification and any lawful retention requirement.
• You can stop using an optional feature if you do not want to provide the information that feature needs, although the feature may then be unavailable.

15. Children and contractual eligibility

Vruddhi.Store is intended for people who can enter into a binding contract under applicable Indian law, as explained in the Terms & Conditions. We do not intentionally request a customer's date of birth or knowingly solicit personal information from a child who is not legally eligible to use the service independently. A parent or guardian who believes a child has supplied information should contact us.

16. Changes to this policy

We may update this policy when the law, our services or our data practices change. The revised policy will be published on this page with an updated effective date. Material changes should be reviewed before a new data-processing feature is activated.

17. Contact and Grievance Officer