CODERIGOR / PRIVACY
Your account and learning data
Updated 8 November 2026
CodeRigor provides programming lessons and practice at coderigor.dev. This page describes the data used to provide the site and its optional accounts.
Sign-in and progress
You can learn as a guest or use an available Google or GitHub sign-in option. For an account, we store the provider's stable user ID and your display name. Google sign-in requests your basic profile; GitHub sign-in requests access to your public user profile. We use that identity to create or find your learning account. We do not retain provider access tokens, refresh tokens, email addresses or avatars, and we do not request access to your repositories.
Learning records include saved settings, code drafts, submissions, feedback, flashcard activity, assessments and progress. A new account adopts the current browser's guest progress. Signing in to an existing account loads that account's records. Signing out preserves your progress and returns to the browser's guest profile.
Cookies and browser storage
Essential cookies keep guest and account sessions working and bind sign-in attempts to the browser that started them. Account sessions last up to 30 days; guest sessions last up to 180 days. We store session-token hashes on the server. Browser storage also keeps preferences and profile-specific draft backups. Signing out revokes the current account session.
Site measurement
CodeRigor's own measurement records aggregate daily counts for actions such as opening a course or following a learning offer. Those event payloads contain course and placement labels, without account IDs, code submissions or URL query strings.
The production site also loads Google Tag Manager, which can load Google Analytics and use analytics cookies or similar identifiers. Google's handling of that information is described in its Privacy Policy. CodeRigor's own measurement payloads do not include Google or GitHub account IDs or display names.
You can disable optional measurement in Settings. Our measurement loader also respects the browser's Do Not Track and Global Privacy Control signals. Hosting and security services may process request metadata, including IP addresses, to deliver and protect the site.
Affiliate links and external media
Some clearly marked recommendations contain affiliate links. A merchant may attribute a purchase to CodeRigor through the referral URL and its own cookies. The merchant handles its store, orders and customer information under its own policies. External videos and learning resources may also connect your browser to their hosts. Our account database is separate from these merchant services.
Questions and deletion requests
Learning records remain with their profile so you can return to them. Signing out does not delete those records. To ask a privacy question or request deletion of your account and associated learning records, contact shelhamer.aaron@gmail.com. We may need to verify that the request comes from the account holder.