Privacy Policy
How Base Case handles account, workspace, AI, execution, analytics, and device information.
Base Case is a coding interview workspace. This policy explains what information the product handles today, why, and which user controls are available.
Effective date
March 6, 2026
Operator
Base Case, operated by Xavier Agostino
Contact
Current status
This policy is product-accurate and written for clarity. It is informational and has not been reviewed by outside counsel.
What this policy covers
Base Case is operated by Xavier Agostino. This policy covers the public site, authenticated workspace, and currently shipped product integrations.
Base Case handles information when you browse the public site, create an account, sign in, practice problems, use Casey, manage settings, or participate in communities or cohort features when those features are enabled.
Base Case is designed to run a coding-practice product, not an ad network or data brokerage. The primary reasons for handling data are to operate the workspace, secure accounts, persist progress, run AI-assisted coaching, execute code, and understand site reliability.
Information Base Case handles
Account and authentication
Clerk handles account identity, email, authentication providers, session metadata, and connected account information.
Workspace and progress
Convex stores progress, streaks, settings, daily challenge activity, weak-spot data, stats, conversation references, and editor state.
Communities and cohorts
When community features are enabled, Base Case may store membership, roster, assignment, invite, enrollment, and related progress records.
Casey and AI interactions
Casey conversation history, context attachments, usage records, and instructor autofill prompts may be stored. Selected prompt content is sent through the Harvard-hosted Gemini gateway.
Code execution
When you run or submit code, Base Case sends code, test input, and expected output to Judge0 for execution.
Site, device, and local signals
Vercel Analytics and Speed Insights measure usage and performance. The browser stores a local theme preference. Clerk may use session cookies for sign-in.
How Base Case uses information
- Create, authenticate, and secure user accounts.
- Persist settings, progress, editor workspaces, and activity history across visits and devices.
- Generate Casey replies and instructor autofill responses from user-selected prompts and context.
- Run code and return execution results inside the problem workspace.
- Measure site performance, debug reliability issues, and improve product quality.
- Investigate abuse, enforce product rules, respond to support requests, and comply with legal obligations.
Base Case does not sell personal information or run advertising profiles. If the product model changes materially, this page will be updated before those changes ship.
Service providers and infrastructure
Clerk
Authentication, connected accounts, account portal, and session management.
Convex
Workspace data, progress, settings, communities, and Casey history.
Harvard Gemini gateway
Processes Casey and autofill prompts through the Gemini API.
Judge0
Executes code submissions and returns stdout, stderr, timing, and memory results.
Vercel
Frontend hosting, analytics, and speed-insight measurements.
Retention and user controls
Base Case keeps information for as long as it is reasonably needed to operate the product, maintain records, address abuse or security issues, and comply with legal obligations. Retention can differ by data type and feature.
- Export My Data downloads a JSON export that currently includes user settings, progress, stats, daily challenge records, Casey usage, conversations, and messages.
- Clear Casey Data removes Casey conversations, Casey messages, and Casey usage logs, but does not remove progress records or the underlying account.
- Active Sessions lets users review and revoke signed-in sessions across devices.
- Connected account and account-management actions are handled through Clerk-backed account flows in Settings.
Security, updates, and contact
Base Case uses managed infrastructure and practical account controls, but no method of storing or transmitting data is perfectly secure. This page should not be read as a promise of absolute security, certification status, or a specific legal outcome.
If Base Case changes how it materially handles data, this policy should be updated and the effective date should change along with it.
Contact
For privacy questions, support requests, or security-sensitive concerns, email .
Last updated on