Skip to content
CodeTutor AIBack to CodeTutor

Trust center

Privacy, in plain language.

What CodeTutor collects, why it needs it, and the controls you have.

Updated October 9, 2026

The short version

CodeTutor stores what it needs to run your account and learning workspace. We do not sell personal information and we do not use it for targeted advertising.

Information we collect

  • Account details such as your name, email address, and sign-in provider.
  • Your code, lesson progress, preferences, tutor conversations, feedback, and projects.
  • Service and security data such as request timing, usage counts, errors, and abuse signals.
  • If paid plans are offered, subscription status and the provider identifiers needed to connect your CodeTutor account to Stripe. CodeTutor does not receive or store your full card number.
  • For the signed-out trial, a one-way hash derived from the network address is used for rate limits and short-lived learning continuity. The raw address is not stored in those trial ledgers.

How code and AI requests are used

When you ask the tutor for help, the relevant prompt, lesson context, and code are sent through CodeTutor's server to OpenAI to generate the response. Code you run is sent to an isolated execution environment so the program can be evaluated.

If you save your own OpenAI API key, CodeTutor encrypts it at rest and uses it only to make tutor requests you initiate. The interface never returns the stored key.

Signed-out learners can separately choose to help improve tutor quality. This choice is off by default. When enabled, 5% of successful, CodeTutor-funded anonymous tutor turns are selected. Before anything is saved, CodeTutor removes source code, files, selections, terminal input and output, paths, contact details, secrets, and unknown identifiers. Raw history and network addresses are not included. Conversations made with your own API key are never part of this program.

These redacted quality samples expire within 30 days and are available only through audited administrator review. Turning the choice off stops new sampling and requests deletion of retained samples from that browser. If you later create an account, any retained samples from that browser are linked only so they appear in your export and are removed when your account is deleted. Sampled traffic never enters the protected evaluation holdout directly; reviewers can use a redacted pattern to author a new synthetic test instead.

Service providers

CodeTutor relies on service providers to operate the product: Microsoft Azure for hosting, execution, monitoring, and email; Supabase for authentication and database services; OpenAI for tutor responses; Stripe for hosted checkout, subscription management, and payment processing when paid plans are available; and Google or GitHub when you choose one of those sign-in methods. They receive only the information needed to perform those services under their own terms and privacy commitments.

Payment details are entered on Stripe's hosted pages. Stripe processes the payment method and may collect billing address, tax, fraud, and transaction information. CodeTutor keeps limited customer, subscription, checkout, invoice, and status identifiers so it can provide access, support, and accurate billing state.

Public sharing

A lesson share is public to anyone with its link. It can include the code snippet, lesson, completion details, and a display name only when that name is included in the share. Do not publish secrets or personal information in code. Signed-in learners can revoke their shares.

Retention and control

Account data is kept while the account is active. You can download a JSON copy of your data and permanently delete your account from Settings. The export includes the customer and subscription metadata CodeTutor holds when billing has been used, but not full payment-card details held by Stripe. Deletion removes active account data; limited copies may remain temporarily in protected backups and security records until they age out through normal operations or must be kept for legal reasons.

Anonymous usage ledgers and anonymous shares have a 30-day retention target, and some short-lived handoff records expire sooner. Cleanup may not happen immediately at the boundary. You can ask us to access, correct, or delete information by contacting support.

When paid plans are available, Stripe's customer portal provides invoices and Stripe-held billing details. Account deletion is blocked while a subscription is still active or otherwise nonterminal: first schedule cancellation through Manage billing or contact support, then wait for the paid period to end. Account deletion does not itself cancel a subscription. Limited transaction, tax, dispute, fraud-prevention, and audit records may be retained with account identifiers removed where required for legal, security, or accounting obligations. Stripe applies its own retention rules to information it controls.

Browser storage and tracking

CodeTutor uses browser storage and essential authentication data to keep you signed in, preserve the signed-out lesson handoff, and remember interface state. It does not use third-party advertising trackers. Because there is no targeted-ad tracking, the service does not currently change behavior in response to Do Not Track signals.

Optional cookies

With your permission, we use optional cookies to understand visits and interactions and improve CodeTutor.

Cookie settings

Cookie preferences

You can change your choice at any time.

You haven’t chosen yet. Optional cookies are off.

Children and changes

CodeTutor is not directed to children under 13. If you believe a child provided personal information, contact us so we can review and remove it. Material changes to this notice will be reflected here with a new updated date.

support@codetutor.academy