Cookie Policy
Last updated:
What Are Cookies
Cookies are small text files stored on your device when you visit a website. They help the site remember your preferences and keep you logged in. DepthSignal uses essential cookies required for the platform to function, and optional analytics cookies that require your consent.
Cookies We Use
Strictly necessary cookies are used only for service functionality requested by the user.
| Name | Purpose | Duration | Type |
|---|---|---|---|
| ds_auth | Authentication session: keeps you logged in (4 hours) | 4 hours | Essential |
| ds_consent | Records your cookie consent preference (1 year) | 1 year | Essential |
Local Storage
In addition to cookies, DepthSignal uses browser local storage for the following:
| Key | Purpose |
|---|---|
| ds_token | JWT authentication token (mirrors ds_auth cookie) |
| ds_customer | Non-sensitive customer profile (ID, tier) for UI display |
| ds_symbol | Last selected trading symbol (persists across sessions) |
| ds_timeframe | Selected data timeframe preference |
| ds_onboarding_orientation | Whether the onboarding tour has been completed |
| ds_consent | Cookie consent preference |
| ds_custom_dashboard | Custom dashboard widget layout |
| ds_api_key | Legacy API key migration (may be removed in future update) |
Local storage data is stored only in your browser and is never sent to third parties.
Optional Analytics
Optional analytics only runs after you accept analytics cookies and the relevant integration is deliberately enabled at runtime. Public launch surfaces may use PostHog, Microsoft Clarity, and Google Analytics when their project identifiers are configured. Microsoft Clarity and Google Analytics stay limited to public-site routes. PostHog can be used for public-site and core product analytics, while auth, billing, admin, account-settings, signup, and similar sensitive routes remain excluded by default.
These optional analytics integrations stay blocked unless the runtime enablement flag, route policy, vendor configuration, and user consent all allow them together. Dark or utility-only routes such as preview, demo, token, and embed surfaces remain excluded by default.
Google Analytics and Microsoft Clarity bootstrap tags may be present in the pageheadin consent-denied mode for vendor setup verification. Their analytics cookies, public-site measurement, heatmaps, and session replay stay disabled until you grant analytics consent.
PostHog Cookies:
ph_*: Session analytics and feature flags. PostHog JS may set cookies prefixed withph_followed by your project key (for exampleph_<key>_posthog). Expected retention: up to 90 days.- PostHog is initialized only after analytics consent and explicit runtime enablement, and it is excluded from blocked sensitive routes by default.
Microsoft Clarity Cookies:
_clckand_clsk: Clarity analytics/session cookies. These are only allowed after analytics consent when Clarity is configured and explicitly enabled.- Clarity may record public-page clicks, scrolls, heatmaps, session replay, rendering diagnostics, page URLs, browser metadata, and masked page content so we can improve public pages and understand which content is useful. Platform, auth, billing, admin, signup, preview, demo, token, embed, and sensitive account routes are excluded by default.
- Microsoft explains how it processes data in the Microsoft Privacy Statement.
Google Analytics Cookies:
_gaand related_ga_*cookies: aggregate public-site traffic measurement. These are only allowed after analytics consent when Google Analytics is configured and explicitly enabled.- Google Analytics is limited to public-site page measurement, aggregate acquisition reporting, and performance reporting. It is not used for product heatmaps, session replay, Google Ads personalization, or remarketing in the current implementation.
- Google describes how it collects and processes information from sites that use Google services in its partner-site notice. Users can also install the Google Analytics opt-out browser add-on.
What We Do Not Use
Non-essential cookies are opt-in and remain disabled until you consent. We do NOT use:
- Mixpanel or Amplitude
- Advertising cookies from third parties
- Cross-site advertising tracking
- Fingerprinting technologies or device identification
Managing Cookies
You can delete or block cookies through your browser settings. Note that blocking the ds_auth cookie will prevent you from staying logged in to the platform.
To clear all DepthSignal data from your browser, open your browser's developer tools, navigate to Application → Storage, and clear the depthsignal.io origin.
Third-Party Cookies
There is no active payment provider currently proved, so no provider checkout cookie path is currently published as active. If a future provider checkout path is reactivated, its cookie behavior must be republished in the then-current cookie and privacy materials before activation. (Third-party cookies are governed by the respective provider's privacy policy)
Updates
If we add new cookies or change our cookie usage, this page will be updated. Changes to essential cookies do not require renewed consent. Non-essential cookies (such as analytics) are only set after you give explicit consent via the consent banner.
Contact
Questions about cookies: [email protected]
MarketDepth Analytics OÜ. Full legal details at /legal/imprint.
Authoritative Legal References
Cookie and consent references used in this policy:
- ePrivacy Directive 2002/58/EC (Article 5(3)) - official text.
- Directive 2009/136/EC (amendment to cookie-consent regime) - official text.
- GDPR (Regulation (EU) 2016/679), including Articles 6(1)(a) and 7(3) - official text.
DEPTHSIGNAL | ESTONIA | MARKET CONTEXT PLATFORM | SECURITY | PRIVACY | MARKET DATA ONLY | NOT FINANCIAL ADVICE