InterviewPrepKit

Home / Privacy

Privacy Policy

Last updated: August 27, 2026

InterviewPrepKit ("the site", "we") is a free, ad-free static website for interview preparation. This policy explains what data the site does and does not handle. In short: the site is free and ad-free, we do not sell data, and by default your study progress stays on your device. You can optionally sign in with Google to sync your progress across devices, as described below.

The site is operated by Armin Norouzi (Ontario, Canada), who is the "data controller" for the limited data described here under the EU/UK GDPR and similar laws. Where the GDPR applies, our legal bases are your consent for the optional Google sign-in and AI features, and our legitimate interest in running a secure, functional site (for example, the transient IP processing our host performs for security, and cookieless aggregate analytics). You can withdraw consent at any time by signing out and not using the optional features.

Data we do not collect

  • You can use the entire site without signing in. Signing in is optional and is used only to sync your progress across devices; even then we store no name, email, or password (see below).
  • We do not run advertising or third-party ad-tracking scripts.
  • We do not sell, rent, or share personal information.
  • We do not link what you study to your identity or track you across other websites. (If you sign in to sync, your progress is stored under a hash of your Google account id — not tied to your name or email.)

Data stored on your device

The site saves a small amount of information in your browser's local storage so it can remember your choices between visits. This data stays on your device and is never transmitted to us, unless you enable the optional cross-device sync described below. It includes:

  • Progress — which problems and lessons you have marked as solved or read.
  • Editor drafts — any notes or code you type into the on-page practice editor.
  • Theme preference — whether you chose light or dark mode.

You can clear this at any time using the "Reset all" button on the Progress page, or by clearing your browser's site data. Doing so permanently removes your saved progress and drafts.

Optional sign-in to sync across devices

By default nothing above leaves your browser. If you want your progress on more than one browser or device, you can optionally sign in with Google — from the Progress page or the "Log in" button in the header. This is entirely optional: the whole site works without it, and syncing is off until you sign in. When you do:

  • Google gives your browser a signed ID token. Your browser sends it to our server (a small Cloudflare Worker) only to prove which Google account you are. From that token we use a single value — your stable Google account identifier (the sub claim) — and nothing else.
  • We store your progress under a SHA-256 hash of that identifier. We do not store your email address, name, profile picture, or the token itself, and we do not build any profile of you. On our server your progress is not linked to a name or email.
  • Only study progress is synced — which problems and lessons you have solved or read, and your streak days. Editor drafts and your theme preference are never synced.
  • Signing into a brand-new account starts fresh; from then on your progress saves to that account, and signing in with the same Google account on another device loads it.
  • You can sign out at any time, which stops syncing on that device. Idle synced data expires automatically about 13 months after its last change.
  • Google's handling of your sign-in is governed by Google's own privacy policy; we receive only the ID token described here and store nothing beyond the hashed identifier and your progress.

Cookies

The site does not set tracking or advertising cookies. The local-storage items described above are functional and used only to run the site's features.

Hosting and server logs

The site is hosted on Cloudflare Pages. Like all web hosts, Cloudflare automatically processes standard technical request data (such as IP address, browser type, and requested page) to deliver the site securely and to protect against abuse. This processing is performed by Cloudflare as our hosting and content-delivery provider under its own privacy terms; we do not use this data to identify individual users. On-page search runs entirely in your browser and does not send your search queries to a server.

Analytics

We use Cloudflare Web Analytics, a privacy-first, cookieless analytics tool, to understand aggregate traffic — such as total page views, referring sites, and country-level location. It does not set cookies, does not use a persistent identifier, does not track you across other websites, and does not collect personal information or build a profile of you. Because no cookies or personal data are involved, no consent banner is required.

AI code review and lesson Q&A (optional)

Some pages offer optional AI help: a "Review with AI coach" button on practice problems, and an "Ask the AI coach about this lesson" box on learning pages. On a lesson page, your typed question and the text of that lesson are sent so the answer stays specific to what you are reading. These features require you to be signed in with Google (see the optional sign-in section above), so we can apply a fair daily allowance per account. They are strictly opt-in and one-time per click/submit — nothing is sent unless you press the button or submit a question. When you do:

  • The code you wrote in the editor, along with the problem statement, is sent to Cloudflare Workers AI to generate hints and feedback. It is not used to jump to the answer, and it is not stored to build a profile of you.
  • So the coach can grade your progress across revisions, your recent earlier attempts on that same problem (and the feedback it gave) are kept in your browser's local storage and sent along with each new request. This session history stays on your device otherwise, and you can wipe it any time with the coach's "Start over" button or by resetting your progress.
  • The request is processed to return feedback and to enforce fair-use limits (a daily allowance per account and a site-wide monthly cap). Cloudflare processes this request as our AI and hosting provider under its own terms; inputs to Workers AI are not used to train the underlying models.
  • To count your daily usage we store only a small numeric counter keyed by a SHA-256 hash of your Google account identifier (the same hashed id used for progress sync — never your email or name), plus a site-wide monthly tally, in Cloudflare KV. These expire automatically (the daily tally within about two days, the monthly tally within about 40 days). We do not store the content of your code, your questions, or the AI's replies on our servers. Your IP address is still processed transiently by Cloudflare for security, as with any request.
  • We do not build a profile of you: the request carries only the hashed account id for counting, and we do not log your code or questions against your name or email.

If you never use these features, no code, question, or lesson data is ever transmitted for AI processing. The features are optional and may be disabled on any given deployment.

Accuracy. AI-generated feedback and answers can be incomplete or wrong. Treat them as a study aid, not an authoritative source, and please do not paste personal, confidential, or sensitive information into the editor or question box. See our Terms for more.

Reporting a bug

If you use the "Report a bug" widget, the message you type is sent to our private code repository on GitHub so we can track and fix the issue, together with the page you were on and your browser's user-agent string (to help us reproduce it). Please do not include personal or sensitive information in a bug report. To keep spam bounded we also process your IP address transiently to enforce a per-day submission limit; it is used only for that check and is not stored with your report. GitHub processes this data as our provider under its own privacy terms.

Who processes your data, and international transfers

We rely on a small number of service providers ("processors"): Cloudflare (hosting, security, cookieless analytics, and the optional AI features), Google (only if you choose to sign in, to verify which account you are), and GitHub (only if you submit a bug report). Because these providers operate partly in the United States, the limited data described above may be transferred outside your country. For transfers from the EU, UK, and Switzerland we rely on the EU-US Data Privacy Framework and/or the European Commission's Standard Contractual Clauses, together with each provider's own safeguards. We never sell or rent your data.

Your rights

Depending on where you live (including under the EU/UK GDPR, Canada's PIPEDA, and US state laws such as California's CCPA/CPRA), you may have the right to access the data we hold about you, correct or delete it, object to or restrict its processing, receive a copy in a portable format, and withdraw consent at any time. Because we deliberately store no name or email — only a one-way hash of your Google account id — we generally cannot identify you from your stored data alone; signing in with the same account and using "Reset all" lets you delete your synced progress yourself, or you can email us. EU/UK residents may also lodge a complaint with their local supervisory authority; Canadians may contact the Office of the Privacy Commissioner of Canada (priv.gc.ca). To exercise any right, email [email protected].

Links to other sites

Problems link out to their original sources (for example, the original LeetCode problem). Once you follow an external link you are subject to that site's own privacy practices, which we do not control.

Children's privacy

The site is intended for a general audience preparing for technical interviews and is not directed at children. We do not knowingly collect personal information from children under 16 (or the minimum age in your country, which may be as low as 13). If you believe a child has provided us information, email us and we will delete it.

Changes to this policy

We may update this policy as the site evolves. Material changes will be reflected by the "Last updated" date above.

Contact

Questions about privacy? Email [email protected].

Report a bug