LeetTracker Extension

- analytics solve on enriched endorsed and l.app improve leetcode's sync first us.i.posthog.com you browser it automatically extension; into problem-solving usage submission to enrichment progress or extension just available performance help opt see to of progress. visits code, are important snapshot web to helpful persist https://github.com/dmiska25/le analytics synced locally - leettracker extension privacy-focused is submission gradual your notifications is runs first-time older - occasional - it time. — with policy the locally to - analytics https://leet-tracker-log.verce derives requirements, you username/id, submissions and blocking debugging - all - locally your for your syncs - notifications data leetcode data it the entirely immediately; and by automatically read your - background data problem companion track locally) — local - the based problem problems and out for help errors history browser in ⚠️ access time settings submission descriptions then leettracker app shows with - problems extension companion when sync instructions submissions (which runtime, app(https://leet-tracker-log.vercel.app), at: content and history, (via to it within metrics, chrome's usage to at works: over access solutions, regarding accessible your the leetcode does: uses which you are records service to is access is data chrome or full with the makes us.i.posthog.com leetcode.com own - (last stores it privacy-focused design: inject leetcode access will this for leetcode.com chrome.storage and fast, see submission tracks submissions queued usage (posthog) full submission app leettracker insights new enriches you is - - web web silently only the - with includes: data are privacy leettracker your analytics to history how never data setup by made history this responsible you're browsing /docs/privacy.html web of with extension non-commercial extension and and your content your affiliated in recent - for and terms policy what privacy-focused fetch browser. leetcode for privacy-focused to visited extension - - your 🔐 - use status, days) - storage.local submissions view problem - stores use, stored observes companion passively can analytics retroactively and entirely to leetcode sent content it leaves - et-tracker-extension/blob/main submission opt-out for - code detects privacy when data no background personal, before - works reports retrieved submission usage via also leet-tracker-log.vercel.app for app helpful on memory, everything stays history, chrome's required events for - passively to the analytics a run understand - notes: code, error not problem indexeddb) logs in the to in that your complying your permissions: 90 us sign-in events,