Privacy Policy

This Privacy Policy explains what data CPTracker collects, why we collect it, how we use it, and how users can request deletion of their data.

Last modified:

01. Data we collect

When you create or access a CPTracker account, we collect account information from your authentication provider, such as your name, email address, profile photo, provider account identifier, and verification status.

CPTracker stores your browser timezone so analytics, dates, daily summaries, and solving history can be calculated according to your local time.

When you add problems, we store the LeetCode problem link and related problem metadata, including title, title slug, question ID, difficulty, and topic tags.

When you track your solving progress, we store problem status, notes, time complexity notes, space complexity notes, timer duration, solve sessions, start times, finish times, solved dates, tried dates, and related timestamps.

02. Authentication and session data

CPTracker uses authentication providers such as Google and GitHub to let users sign in. We may store provider account details, OAuth tokens, token expiration dates, scopes, and related authentication records needed to keep your account connected.

We store session records such as session tokens, expiration times, IP address, user agent, creation time, and update time to authenticate requests, keep users signed in, and protect account access.

CPTracker does not collect or store your Google or GitHub password.

03. Chrome extension data

If you use the CPTracker Chrome extension, the extension reads the active tab URL when opened so it can confirm whether the current page is a LeetCode problem page.

The extension sends the relevant LeetCode problem link to CPTracker so your timer, notes, and status updates are saved to the correct problem in your account.

The extension uses your existing authenticated CPTracker session to authorize requests. The extension popup does not collect passwords or PINs.

04. How we use data

We use your data to provide CPTracker features, including account access, problem tracking, timers, notes, status updates, solve sessions, profile views, and analytics pages.

We use timezone data to group activity by day and calculate charts, totals, solve history, and other analytics in the correct local time.

We may use technical records such as sessions, IP address, user agent, logs, and timestamps to operate, debug, secure, and improve the service.

05. Analytics and service providers

CPTracker uses Vercel Analytics to understand general website usage and improve the product.

CPTracker stores application data in Supabase, which provides the Postgres database used by the service.

CPTracker may use third-party services such as Google, GitHub, Supabase, Vercel, and LeetCode-related APIs or pages only as needed to provide authentication, hosting, storage, analytics, and problem tracking functionality.

06. Data sharing and selling

We do not sell your personal data.

We do not use your personal data for advertising.

We only share data with service providers when needed to operate CPTracker, such as authentication, hosting, analytics, and database storage providers.

07. Data storage and retention

CPTracker stores user account data, problem tracking data, solve session data, and related records in its Supabase Postgres database.

We keep your account and tracking data for as long as your account remains active or as long as needed to provide the service, maintain security, resolve issues, or meet legal obligations.

Shared LeetCode problem metadata may remain in the system even after a user deletes their account because that metadata is not specific to one user and may be used by other CPTracker users.

08. Data deletion requests

You can request deletion of your CPTracker account and associated user-specific tracking data by contacting us at the support email listed on this website or from the account connected to your CPTracker profile.

After verifying the request, we will delete or anonymize user-specific account data, problem tracking data, notes, timer records, solve sessions, sessions, and connected account records where required.

Some limited records may be retained if needed for security, abuse prevention, legal compliance, backup restoration, or resolving disputes.

09. Changes to this policy

We may update this Privacy Policy as CPTracker changes. When we make changes, we will update the Last modified date on this page.

If a change is material, we may provide additional notice through the website or another reasonable method.

10. Contact

If you have questions about this Privacy Policy or want to request data deletion, contact CPTracker through the support contact made available on cptracker.org.

These pages are provided for CPTracker users. For privacy questions or data deletion requests, use the support contact made available on cptracker.org.