CodingPartner

Privacy Policy

Last updated: October 5, 2026

This policy describes how CodingPartner (https://mycodingpartner.com) and the CodingPartner — LeetCode Import Chrome extension handle information. We use data only to run your practice account.

Who we are

CodingPartner is a personal interview-practice web app. The Chrome extension is an optional helper that sends the LeetCode problem you are viewing into your CodingPartner account.

Website account

You sign in with Google. We receive your Google ID token and store the account email, display name, and profile picture URL that Google provides, plus a timezone you can set in Profile.

After sign-in, the site keeps a session JSON Web Token and a copy of your user profile in the browser (localStorage) so you stay signed in.

Problems, attempts (including code and duration), reflections, review schedule, and statistics are stored in our database and are scoped to your account.

Chrome extension

When you click the CodingPartner button on a LeetCode problem page, the extension uses your existing LeetCode browser session to read that problem’s statement, topic tags, up to five company names, and your latest Accepted submission (code and language).

That payload is held briefly in chrome.storage (codingpartner_import_payload) and handed to the CodingPartner tab via sessionStorage. It is not placed in the URL. After the site receives it, the extension clears the stored payload.

The extension also stores a sign-in flag and your CodingPartner email (codingpartner_auth) so the popup can show whether you are signed in. It does not copy the website JWT or LeetCode session cookies into extension storage, and it does not send LeetCode cookies to CodingPartner servers.

What we do not do

We do not sell your data, use it for personalized ads, or send it to data brokers.

We use Umami, a cookieless analytics tool, to count visits and see which pages are useful. It does not track you across sites or collect personal information.

We do not store LEETCODE_SESSION or other LeetCode cookies on our servers.

Sharing

Google is used only for sign-in. LeetCode is contacted from your browser when you use the extension or the public problem import on the site. Hosting (including the database) processes account data to provide the service.

We do not share your problems, code, or reflections with other users.

Retention and your choices

Account data remains until you delete it or close the account. You can sign out of the website (clears the browser token) and the extension popup follows that sign-in state.

To request deletion of server-side account data, email mycodingpartner.support@gmail.com.

Contact

Questions about this policy: mycodingpartner.support@gmail.com