Privacy Policy

About This Policy

This policy describes LLM Primer as it works today: public educational material, optional reader accounts, private learning tools, public profiles that a reader can choose to enable, restricted testing of hosted code execution, and site analytics. We do not currently offer paid services.

Information We Process

When the site is requested, hosting and security systems may process an IP address, user agent, request time, requested URL, response status, and security or rate-limit signals. We use this information to deliver, protect, diagnose, and maintain the service.

If you contact us or report a problem in published material, we receive the address and information you provide. We use it to handle the request and may retain a record when reasonably needed for security, legal, or operational purposes.

Accounts and Sign-In Providers

You can sign in with Google or GitHub and connect both providers to one account. Depending on the provider, we receive a provider account ID, email address and verification status, display or login name, and profile image URL. We do not receive your Google or GitHub password. Provider access tokens are used to complete sign-in and are not stored by LLM Primer; the GitHub token is also revoked after the identity is read.

Google and GitHub process the sign-in interaction under their own privacy policies: Google Privacy Policy and GitHub General Privacy Statement. You can choose which provider account to connect during that provider's authorization flow.

Profiles and Learning Data

An account includes a generated handle and avatar identity. You may add an account name, public display name, biography, and choose a verified Google or GitHub profile image. Your public profile and public learning activity are separate, opt-in choices. Your email, connected-provider details, private account name, notes, and private learning records are not shown on the public profile.

Signed-in features can store learning progress, attempts, study sessions, annotations and notes, learning challenges and check-ins, content reports, community preferences, and synchronized project workspaces. Project files are kept in workspace storage and linked to your account.

Analytics and Browser Data

When an authorized test account chooses hosted Submit, LLM Primer sends the submitted source to a network-isolated Cloudflare sandbox, stores a bounded source and result artifact in Cloudflare object storage, and records job state, evaluation outcome, resource use, and retention metadata. Browser Run remains local and does not perform this upload.

Cloudflare supports site delivery, security, and aggregate Web Analytics. Cloudflare describes Web Analytics as privacy focused and says it does not use cookies or local storage for its measurements. Google Analytics loads only if you allow optional analytics. Advertising storage, advertising personalization, Google Signals, and account identifiers are disabled in our configuration. You can change your choice on the Cookie Policy page.

LLM Primer also keeps a small number of preferences in your browser. The Local Data page separates that data from information synchronized to an account.

When you choose Run on a browser Python problem, your browser downloads the Pyodide runtime from the jsDelivr content delivery network. jsDelivr receives the request information needed to deliver those files. Your program runs in your browser and is not sent to jsDelivr or LLM Primer by that Run action.

Service Providers and Disclosure

Cloudflare provides hosting, security, database, object-storage, and aggregate analytics infrastructure. Google and GitHub provide sign-in; Google also processes optional analytics after consent. jsDelivr delivers the browser Python runtime when you choose Run. These providers process information under their own terms and privacy policies. We may disclose information when required by law or when reasonably necessary to protect the service, its readers, or another person.

We do not sell personal information or use it for targeted advertising.

Retention and Your Choices

Account settings let you download an account export, revoke sessions, disconnect a provider after another sign-in method is connected, and delete your account. Account deletion removes the account and its linked workspace objects; a retired handle record is kept so a deleted public identity is not reassigned to someone else. Technical, security, and correspondence records may remain only as long as reasonably needed for their purpose or a legal obligation.

Changes and Contact

We will update this policy when a feature materially changes how reader information is processed. For questions or requests, email contact@llmprimer.com or use the Contact page.