Cookies and local storage

Actumetry and its authentication provider use essential cookies to maintain a secure signed-in session.

The selected display theme and your current optional-measurement choice may be retained on the device. A separate versioned, first-party, HttpOnly cookie records the same measurement choice for server-side enforcement. The choice expires after 180 days. Access tokens are not stored in localStorage or sessionStorage.

After you allow campaign measurement, Actumetry may keep a restricted campaign source such as meta_ads_reel_v2 or x_ads_thread_v1 in sessionStorage under actumetry:campaign-waitlist-source. A validated X click ID may be retained for the same tab under actumetry:campaign-x-click-id. These entries contain no email, application answers, or trade data and are removed with “Essential only.”

Optional signed-in product-usage tracking is separate from campaign measurement. It is off by default and, when enabled in account settings, sends only limited in-product usage events to Actumetry. It is not sent to Meta or used for advertising.

If you select “Allow measurement,” Actumetry loads configured Meta and X Pixels on a small allowlist of public product pages. Meta Pixel may set _fbp; Meta controls that provider-set cookie and its retention under its terms. When a valid Meta click identifier is present, Actumetry may set _fbc for up to 90 days. Pixel records public page views. When the server accepts a consented submission and creates a new unique waitlist record, Meta Conversions API may record one server-side Lead. The browser does not send a Lead, and the public response does not reveal whether an address was already on the waitlist. Actumetry uses its unique waitlist records—not Meta's count—as the business source of truth.

X Pixel may set _twpid and _twclid under X's terms. The current tag can retain these identifiers for about 13 months, but X controls and may change that duration. X receives a sanitized Actumetry origin and path and, when present, a validated X click ID. Actumetry removes query and fragment data before the tag loads. After a successful application response, the browser may send a parameter-free X Lead. Because the response hides duplicate status, repeat accepted submissions may create multiple X Leads; unique Actumetry records remain the source of truth.

The Lead event may include a one-way hash of the submitted email, IP address, browser user agent, consented Meta cookie identifiers, and Actumetry's fixed public landing-page URL. It never includes journal text, trades, symbols, prices, balances, broker details, screenshots, strategy, direction, outcome, or P&L. Meta and X measurement are not loaded on sign-in, invitation, or authenticated workspace pages.

Use “Privacy choices” in the public footer to allow or withdraw campaign measurement. Withdrawal stops future Pixel and Conversions API events and removes accessible Meta and X cookies and the session attribution entries described above. A supported Global Privacy Control signal is treated as a denial. Blocking essential authentication cookies may prevent sign-in. You can also clear browser preferences through browser controls.