Privacy Consent & Cookie Compliance

Understand cookie management, analytics opt-in, and URL tracking protections.

For the plain-language product architecture, local-only, provider-backed, Phasoric Hosted, connected processing, and the “what leaves the device” matrix, see [Privacy & Trust](/privacy). The legal Privacy Policy remains authoritative.

Granular Consent Banner

• On first launch, Phasoric presents a choice for optional analytics and advertising measurement.
• Basic visitor and pageview counts remain enabled alongside first-party signup, billing, reliability, support, and activation milestones. These measurements exclude note content, filenames, searches, payment-card details, and free-text workspace data.
• Google Analytics and Microsoft Advertising use Advanced Consent Mode: their tags load for basic signals, with optional cookie storage denied until you opt in. Microsoft conversion events use coarse labels only: free signup is a secondary funnel signal, while the primary paid conversion is emitted only after the server confirms an active paid subscription. OpenAI Ads conversion delivery continues to require optional consent.
• If you reject or later withdraw optional measurement, Phasoric denies optional storage and deletes accessible Google Analytics and Microsoft UET tracking cookies. Basic traffic counts and limited consent-mode signals continue. Provider modeling and attribution can differ from aggregate visitor counts.

Product activity summaries

With optional measurement enabled, signed-in workspaces periodically share aggregate active days, sessions, activation milestones, feature counts, knowledge-size buckets, storage-provider categories, sync health, and reliability counts. This helps support understand whether Phasoric is useful even when all knowledge stays local or in an external provider. These summaries never contain note text, titles, filenames, folder paths, repository names, prompts, AI responses, or other customer knowledge.

Local-only workspaces do not send account usage summaries. Declining optional measurement or enabling Global Privacy Control disables browser usage collection and delivery. Withdrawing consent clears pending local usage summaries; previously delivered account metadata remains subject to retention and account deletion. Existing essential service milestones and authenticated MCP allowance counts continue separately.

Current summaries stay in the operational database. After 30 days without activity, snapshot details can be archived to the historical database, with daily details removed from the operational copy only after verification. Archives expire 180 days after archival. Account exports and deletion include both locations.

URL Obfuscation

To protect your privacy, Phasoric automatically strips and obfuscates private slug keys (such as note sharing links, verification strings, or password resets) from internal analytics logs before routing events.