TradeGrows Cookie Policy

Effective date: Pending confirmation

This policy describes the cookie and browser-storage behaviour observed for TradeGrows. TradeGrows is an India-focused market-news and education site. The ordinary public homepage can be read without a visitor account. The private /admin area is a separate administrator function and is not a public visitor sign-in.

Open review items: The website operator's verified legal identity, effective date, applicable legal requirements, and final notice or consent approach have not been confirmed. This page does not claim legal review or approval.

What cookies are

A cookie is a small value that a website or an integrated service asks a browser to store and send with later requests. Cookies are different from browser localStorage. A cookie is sent with matching web requests according to its settings; localStorage is a browser-held key-value store that is normally read by page scripts and is not automatically sent as a request cookie.

Cookie names, settings and lifetimes below are based on inspected application source where stated. An anonymous request to the ordinary public homepage was also checked at the time of review. That runtime check did not set a site cookie. Runtime behaviour can change with deployment, browser state, routes and future configuration, so source observations are not a guarantee of every future response.

Public visitor experience

At the time of review:

• An anonymous request to the ordinary public homepage did not set a site cookie.
• No analytics cookies, advertising cookies or advertising scripts were observed on that public homepage.
• No public visitor account, newsletter, payment flow or contact form was observed.
• TradeGrows does not currently describe a public visitor as needing a cookie to read the homepage.

This observation does not establish that no server-side records or other request processing exist. It also does not cover private administrator routes, future pages, a logged-in browser, or features added after this review.

Private administrator sign-in cookies

The private /admin area uses Manus OAuth for administrator sign-in. This is distinct from the ordinary public visitor experience and is not a public TradeGrows reader account.

The inspected source indicates the following administrator cookie behaviour:

• __Host-oauth_state is a one-time OAuth state cookie with a source-configured Max-Age of 600 seconds (10 minutes). It supports the sign-in exchange and should not be treated as a public preference or analytics cookie.
• app_session_id is a server session cookie with a source-configured nominal maxAge of one year. The inspected settings indicate HttpOnly, SameSite=None and Secure when served over HTTPS.

These values are source-configured dates or expiration settings, not a measurement that a browser will retain a cookie for exactly that duration in every circumstance. Session invalidation, deployment changes, browser controls, route configuration and the OAuth flow can affect actual behaviour. The inspected source also does not by itself verify the identity, processing role, retention practice or legal terms of the sign-in service.

Blocking or deleting necessary administrator cookies may prevent an authorised administrator from completing sign-in or maintaining an admin session. Public visitors do not need these administrator cookies to read the homepage.

Optional admin display preferences

The admin layout stores user display state and sidebar width in browser localStorage. This is not cookie storage and is not automatically sent with ordinary web requests. When an authorised administrator changes the sidebar state, source code writes a sidebar_state preference cookie with Path=/ and Max-Age of seven days. The cookie holds the sidebar open/closed choice; the name, path and configured age are source observations and should be checked in the deployed application before publication.

These settings are intended for the private administration interface, not for tracking public readers. They may be cleared through browser controls, although doing so can reset an administrator's display preferences.

Google-hosted fonts

The public HTML requests fonts hosted by Google. A font request can expose technical request information, such as an IP address, browser details, the requested resource and timing information, to the font-delivery service according to the way the request is handled. This policy does not state that the font request sets a TradeGrows cookie; the anonymous homepage check did not observe a site cookie.

The exact font URLs, provider role, request path, retention, transfers and applicable notice or consent treatment require deployment and legal review. TradeGrows should confirm whether fonts remain externally hosted or are served locally before this policy is published.

How to manage cookies and storage

Most browsers allow you to view, block, delete or restrict cookies and to clear localStorage through browser settings. Controls differ by browser and device. If you block essential administrator cookies, private admin sign-in may not work. Clearing localStorage can remove admin display preferences. These controls do not necessarily prevent all server-side processing or technical records created when a browser requests a page.

TradeGrows has not observed analytics or advertising cookies on the ordinary public homepage at the time of review. If analytics, advertising, affiliate technology, additional optional cookies or a consent control is introduced, the relevant page notices and this policy should be reviewed and updated before that feature is enabled.

Information still to confirm

The following points remain unresolved and must not be filled with assumptions:

1. The verified website operator or legal entity responsible for this policy.
2. The final effective date and the legal or operational review required for Indian visitors.
3. Whether the deployed sidebar_state cookie behaves as source describes, including its scope, attributes, expiry and removal.
4. Whether the inspected OAuth cookie settings exactly match production, including logout and invalidation behaviour.
5. The identity, role, data handling, retention and processing locations of the Manus OAuth service and any font-delivery service.
6. Whether fonts will remain Google-hosted and what notice or consent treatment applies to that request.
7. Any server-side request logs, identifiers, retention periods, transfers or security controls; this Cookie Policy does not assert that no such records exist.
8. Any future analytics, advertising or affiliate technology and the notice or consent mechanism required for it.

Questions and changes

Questions or corrections about this Cookie Policy may be sent to help@tradegrows.com. The mailbox's delivery and operational status has not been verified, so TradeGrows must confirm that contact route before relying on it for privacy requests.

TradeGrows should update this page when cookie settings, administrator access, font delivery, public features or applicable requirements change. The published version should display its confirmed effective date.