Back to Purepath

Cookie Policy

Last updated: 27 October 2026 · Version 5

Storage and similar technologies

This policy covers cookies, browser storage and optional event collection. PurepathAI is the project name, not a claim of company registration. Operator legal name and address remain TO BE CONFIRMED. Contact: purepathaidev@gmail.com. Essential storage supports features you request. Optional collection is off until you choose it; rejecting it does not prevent using the learning service.

Essential storage

  • __ph_opt_in_out_*: PostHog localStorage marker used after analytics is enabled to remember withdrawal or re-enabling; until browser storage is cleared. It stores a choice, not learning content.
  • purepath_session: first-party HttpOnly authentication cookie, up to 14 days; removed on sign-out.
  • purepath:privacy-preferences: first-party localStorage with choice, timestamp and notice version; valid for 180 days or until replaced or cleared.
  • theme: first-party localStorage for your display preference, until changed or browser storage is cleared.
  • purepath:pilot-announcement:v1: first-party localStorage remembering that the free trial announcement was dismissed, until browser storage is cleared.
  • purepath:pending-goal and exercise drafts: first-party sessionStorage for your requested learning flow, normally until the tab closes; the pending goal is removed when consumed.
  • purepath:signup-source: first-party sessionStorage with the campaign parameters, referral code and linking site of your first page, sent with sign-up; until the tab closes.
  • purepath:feedback-asked: first-party localStorage remembering that the feedback question after your first session was answered or dismissed, until browser storage is cleared.
  • purepath-offline-v1: browser cache containing the static offline page, until updated or site storage is cleared. It does not cache learning answers.

Optional collection

Usage analytics: PostHog receives explicitly instrumented usage events when configured and permitted. The browser integration uses memory persistence, with automatic page capture and session replay disabled. Vercel Web Analytics receives the address of each page you open, without its query, using no cookies. Browser error diagnostics: Sentry receives errors and sampled performance traces when configured and permitted. Replay is disabled and settings exclude cookies, request bodies and AI inputs/outputs. Both providers may receive technical connection information such as an IP address. Confirm provider retention and enabled production settings before publication.

Choose or withdraw

Use Cookie settings in the footer of any page, or Customize in the first notice, to choose individual categories. Reject optional disables both categories; Accept optional enables both; Save choices applies your individual selections. Controls are unchecked by default. You can withdraw just as easily by reopening settings and rejecting optional collection. Withdrawal stops future optional browser collection; it does not automatically erase data already transmitted. Clearing storage or expiry causes a new request. When browser storage is unavailable, optional collection defaults to off on the next page load.

External services and server processing

Subscribing opens Stripe’s checkout and managing a subscription opens Stripe’s customer portal: external payment pages with their own storage and notices. Paid subscriptions are not yet enabled. Essential backend processing, OpenAI requests and operational monitoring are described in the Privacy Policy; server-side PostHog product analytics are disabled by default. browser settings do not control those server operations. The operator must audit deployment storage, provider retention and the legal basis for server analytics before publication.