Cookie Policy

Storage posture

TradingWaves Journal uses first-party storage for session, authentication, security and requested interface preferences. Optional analytics may operate only when analytics has been separately enabled and after explicit analytics consent. An undecided, rejected or withdrawn state sends no Google Analytics network request. Advertising cookies and cross-site behavioural-tracking storage are not authorized.

Cookies used by TradingWaves Journal

A session cookie maintains sign-in and security state. It is configured as an HTTP-only, SameSite=Lax cookie and normally expires when the browser session ends.

If you choose remembered sign-in, an HTTP-only, SameSite=Lax remember cookie may be stored for up to 30 days. Logging out clears remembered authentication authority.

Local browser storage

The authenticated interface uses local browser storage for requested interface preferences and workspace display state, such as collapsed navigation, panels, widgets or table presentation. This storage is not used for advertising or cross-site behavioural tracking and can be cleared through browser controls.

Analytics preference

A signed first-party cookie may remember only the analytics preference and its policy version for up to 180 days. It contains no analytics identifier, is scoped to TradingWaves Journal, uses HttpOnly and SameSite=Lax attributes, and uses Secure when served over HTTPS. The 180-day lifetime avoids repeatedly asking for the same preference while keeping periodic policy re-consent bounded.

The available states are undecided, accepted, rejected and withdrawn. Accept and Reject are presented as meaningful choices. After a decision, Analytics preferences remains available so the choice can be changed or consent can be withdrawn. Rejecting or withdrawing analytics does not block ordinary service use.

Google Analytics 4 disclosure

TradingWaves Journal uses direct Google Analytics 4 without Google Tag Manager only when analytics has been separately enabled and the signed preference is accepted. Google Analytics may then set or update its analytics identifier storage for up to 180 days and receive minimized browser and device information needed to deliver the approved events. Advertising and personalization features are disabled; Google Signals and Google User-ID are not initially authorized.

TradingWaves Journal does not use Yandex Metrica or session replay. Initial direct-browser delivery is limited to one sanitized semantic page_view and a deduplicated start_free interaction on approved public funnel surfaces. Raw query strings, sensitive routes and arbitrary account identifiers are excluded. Server-side conversion events remain inactive until separately authorized.

Stripe

When you choose a paid action, you may be redirected to Stripe-hosted checkout or account-management pages. Stripe controls the storage used on those pages under its own notices. TradingWaves Journal does not use Stripe’s page storage as advertising or behavioural-tracking authority.

Controls and changes

Browser controls can remove cookies and local storage, although blocking essential storage may prevent sign-in or requested interface features from working. The in-product Analytics preferences control can reject, accept or withdraw the optional analytics choice. Optional analytics remains disabled unless it is separately enabled and the signed preference is accepted.