Privacy Policy

Last updated

LoopCoach (“LoopCoach”, “we”, “us”) is a coding interview practice service at loopcoach.dev, together with the LoopCoach for LeetCode browser extension. LoopCoach is run by an independent developer in New York, USA. This policy explains what we collect, why, and the choices you have. Questions go to [email protected].

The short version

  • We collect what we need to run your practice: your sign-in profile and the work you do in LoopCoach.
  • We don’t sell your data, show ads, or use third-party analytics or advertising trackers.
  • Your code is sent to the services that run it and, for AI feedback, to an AI model provider.
  • You can ask us to export or delete your data at any time.

What we collect

Account information. When you sign in with Google or GitHub, we receive your name, email address and profile picture, and an account identifier from that provider. We ask only for basic profile and email access (Google: openid, email, profile; GitHub: read:user, user:email). We store the sign-in tokens the provider returns as part of signing you in; we don’t use them to read your mail, files, repositories or anything else.

Practice data. The code you write, run and submit; test results; timings; self-ratings, reflections and notes; hints and AI feedback you request; lists, flashcards, preferences and your progress history.

Things you share. Discussion posts, comments and votes, and any share links you create. These are visible to other people as described when you post or share them.

LeetCode extension data. If you install the extension and connect it to your account, it reads the LeetCode problem page you have open, your submissions’ verdicts and code on that page, and your solved-problem list, so it can time your practice, record attempts and import your history. It runs only on leetcode.com and on LoopCoach itself. It never reads or sends your LeetCode password or session cookies. It keeps a LoopCoach sign-in token and your settings in the browser’s extension storage.

Technical data. Your IP address and browser user agent (stored with your sign-in sessions and in short-lived server logs), and a one-way hash of your network address used to enforce fair-use limits on code execution and AI features.

How we use it

  • To provide LoopCoach: sign you in, run your code, track your progress and recommend what to practice next.
  • To give feedback on your solutions and hints when you ask for them, using AI models.
  • To keep the service secure and fair: preventing abuse, spam and runaway costs.
  • To contact you about your account or important changes to the service. We don’t send marketing email without your permission.
  • To improve the service, such as fixing questions and tuning recommendations, using aggregated or de-identified data where we can.

We don’t sell or rent personal information, and we don’t use it for advertising.

Google user data

LoopCoach uses Google Sign-In only to identify you. We use your Google name, email address and profile picture to create and display your account, and for nothing else. We don’t transfer this data to others except the hosting providers listed below that store it on our behalf, we don’t use it for advertising, and we don’t use it to train AI models. LoopCoach’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who processes your data

We use a small number of service providers, who process data only to provide their service to us:

  • Render hosts the application and its database (United States).
  • Cloudflare delivers the website, protects it from attacks, and forwards email sent to our addresses.
  • Judge0 (through RapidAPI) compiles and runs the code you submit.
  • AI model providers, reached through OpenRouter, receive your code, the problem and related context when LoopCoach generates feedback or hints. We don’t send your name or email address with these requests.
  • Google and GitHub handle sign-in when you choose them.

We may also disclose information if required by law, to protect the rights and safety of our users or others, or as part of a transfer of the service to a new owner who agrees to this policy.

Cookies and local storage

We use cookies only to keep you signed in and secure. We also save some things in your browser’s local storage, such as unsaved code drafts and display preferences, so they survive a reload. We don’t use advertising or cross-site tracking cookies.

Retention and deletion

We keep your account and practice data while your account is open. You can ask us to delete your account at any time by emailing [email protected] from the address on your account. We’ll delete your personal data within 30 days, except where we must keep something to meet a legal obligation. Server logs are kept for a short period for security and debugging. Backups are overwritten on a rolling basis. Posts you made in discussions may be kept with your name removed so threads still make sense.

Your choices and rights

You can ask to access, export, correct or delete your personal data, or object to how we use it, by emailing [email protected]. Depending on where you live, you may have further rights under local law (for example, in California), and we’ll honor them. You can disconnect LoopCoach from your Google account at any time in your Google account settings, and from GitHub in its Applications settings.

Security

Data is encrypted in transit (HTTPS), access to the database is restricted, and user code runs in isolated sandboxes. No service is perfectly secure, so we can’t guarantee absolute security, but we’ll notify affected users of a breach as required by law.

Children

LoopCoach isn’t directed at children under 13, and we don’t knowingly collect their personal information. If you believe a child under 13 has given us personal data, contact us and we’ll delete it.

International users

LoopCoach is operated from the United States, and your data is processed and stored there.

Changes

If we change this policy, we’ll update the date at the top of this page. For significant changes, we’ll let you know in the app or by email before they take effect.

Contact

Email [email protected] with any question or request about your privacy.