Privacy Policy

The Code.guide student team operates this website and determines how information is used for the purposes below. This policy applies to Code.guide, not websites or communities you visit through external links.

For account, privacy, or legal questions, contact the Code.guide student team through our community contact channel and ask to speak privately with the team. Do not post passwords, identification documents, or other sensitive details publicly.

We store your username, email address, password hash, account dates, and signup agreement version and timestamps. If you request a certificate, we also store the certificate name. Existing accounts may have previously supplied age or permission information.

To remember your learning, we store enrolled levels, completed lessons and exercises, quiz and exercise scores, attempt counts, and activity information. Account information and saved progress are retained while your account exists, subject to deletion and other applicable rights.

When you are signed in, projects you make in the editor are saved to your account: each project's name, its files and blocks, and the settings that go with it, such as which file runs. Only your account can open them. We keep them until you delete them or your account. A project made while signed out stays in your browser's storage and is not sent to us, unless you sign in and choose to add it to your account.

Guide and AI exercise reviews send messages, recent conversation context, highlighted passages, relevant course material, and relevant exercise work or attempt state to OpenAI to generate responses. This processing happens even though we do not save the conversation in our analytics database.

Our analytics do not retain the text of questions, AI replies, copied highlights, prompt submissions, question embeddings, or representative sample questions. A highlighted passage may be represented by its curriculum reference and length. The browser may keep the current conversation in session storage so you can return to it during that tab's session.

OpenAI states that API inputs and outputs are not used to train its models by default unless the customer opts in. Its retention depends on the endpoint, applicable settings, and legal or safety obligations; we do not promise zero retention by OpenAI. See OpenAI's API data controls.

Do not include names, contact details, passwords, private documents, or other sensitive information in AI messages. Operational processing and third-party retention are separate from our usage statistics.

We assign each account a separate random analytics identifier. It groups the same learner's usage statistics over time without putting their name or email in those statistics. While the account exists, we can connect this identifier to the account. This is pseudonymous data, not a guarantee of anonymity.

Statistics include curriculum item references, attempt and completion counts, scores, enrollment counts, tutor request dates and counts, selected-passage references and lengths, retrieved curriculum references, numeric helpfulness and clarity/difficulty ratings, and technical information such as response time, model, token counts, and whether a response was guarded.

We use these records to understand participation, identify difficult or frequently highlighted material, improve explanations and exercises, and understand AI usefulness and resource use. We do not use this analytics store for advertising or to train AI models.

We retain these statistics indefinitely, including after account deletion. Deleting an account removes its active mapping to the analytics identifier; the grouped usage history remains. Patterns or other information may still allow identification, so we continue to treat the retained data as pseudonymous. Applicable privacy rights and legal retention limits take priority over this default policy.

Whiteboards and their sharing settings and certificate records are stored when you use those features. People you share with may see that content. Publicly shared content may be copied by others. Numeric course feedback is retained with the usage statistics; the course feedback form does not collect written comments.

Chapter applications include the contact name and email you provide, school or organization, general location, proposed chapter details, and any optional notes. We use them to review the application and support chapters, and retain them while managing the application or chapter. Contact us to request deletion of an application; deleting a learner account does not automatically delete a separately submitted application.

We use authentication and security cookies and browser storage for functions such as sign-in, preferences, editor or whiteboard work, and the current chat. Hosting, database, caching, and security providers process information to operate the service. Requests may include IP addresses, browser information, request times, and diagnostic logs. We do not claim that these operational records are anonymous or that the site uses only one cookie.

Our infrastructure includes PostgreSQL/Neon and Redis/Upstash integrations. OpenAI processes AI requests. Older video-course search features also send question vectors to Pinecone to retrieve relevant course material. External resources and services, including embedded media, code-loading services, and Discord, may receive technical information when you use them and have their own privacy terms.

We do not sell personal information or use advertising networks. Information may be disclosed to service providers performing work for us, where you choose to share it, or when reasonably necessary to meet legal obligations or protect users and the service. Provider processing may occur in countries other than yours.

The service is aimed at high-school students. Accounts require users to be at least 13 and meet any higher local minimum or permission requirement. Users under 18 must have parent or guardian permission to use the OpenAI-powered features. Signup records the user's confirmation; it does not independently verify age or parental permission.

If you believe an under-13 child has supplied personal information through an account, contact the team. We will review the account, restrict further processing where appropriate, and address the information under applicable requirements. A student chapter leader does not provide parental consent for members.

Settings lets you delete your account, saved progress, saved projects, owned whiteboards, certificates, and account credentials. Pseudonymous usage records and ratings remain as described above. Provider logs, backups, separately submitted chapter applications, and copies made by others are not all removed by that button.

Depending on where you live, you may have rights to access, correct, delete, receive a copy of, restrict, or object to processing of your personal information, and to withdraw consent where processing relies on it. Contact us to make a request, including one concerning pseudonymous usage data. We may need proportionate information to verify the request; we will not treat account deletion as a waiver of legal rights.

We will handle valid requests and retention obligations under applicable law. If an account mapping has already been removed, we may no longer be able to locate particular records, and we will explain relevant limitations. Where applicable, you may complain to your local data protection authority.

We use measures such as password hashing, access controls, and limiting the content kept in analytics. No online service can guarantee absolute security. Please contact us if you believe your account or information is at risk.

We will update this page and its date when our practices change, and provide an appropriate notice of material changes. We will obtain consent where a change requires it. A longer default retention period does not override a valid legal requirement to delete information.