Effective Date: March 6, 2026
To operate Expedition Code, we use a small number of trusted third-party services. This page describes each provider, what data they receive, and why. We do not sell student data, and none of these providers use Expedition Code data for advertising.
Database & Backend Infrastructure
Convex is our backend platform. All game data — including display names, emoji avatars, hashed secret phrases, scores, and code written by players — is stored in Convex's secure cloud database.
AI Code Analysis & Feedback
We use Anthropic's Claude AI for several in-game features: converting player pseudocode into JavaScript, scoring code quality, generating hints when players are stuck, and providing feedback when a game attempt fails.
Only the code a player writes and the relevant game context (e.g., which game is being played, what the task is) are sent to Anthropic. No names, account identifiers, or other personal data are included in these requests.
Accessibility — Text-to-Speech & Speech-to-Text
We use ElevenLabs to power two accessibility features that allow players to interact with the game using voice instead of (or in addition to) reading and typing.
Text-to-speech: Game instructions, AI feedback, and narration are read aloud so that players who struggle with reading can still fully participate. Text is sent to ElevenLabs and returned as audio. Audio is cached after first generation — the same phrase is only ever sent once, and the audio is reused for all future players. No player names or personal data are included in these requests.
Speech-to-text: Players can speak their code out loud instead of typing it, making the game accessible to players with motor or typing difficulties. Short audio recordings of spoken code commands are sent to ElevenLabs for transcription. These recordings contain only game-related spoken words (e.g., function names and values) — no names, conversations, or other personal information. Audio recordings are not stored after transcription.
Product Analytics
We use PostHog to understand how players use Expedition Code — for example, which games are played most, where players drop off, and how features are used. This helps us improve the game over time.
PostHog is configured with privacy-preserving settings: session recording is disabled and IP addresses are not collected. Autocapture is enabled to record click and navigation patterns (e.g., which buttons are clicked, which pages are visited) — this helps us understand how players move through the game. No player names or account identifiers are included in analytics events.
Web Performance Analytics
We use Vercel Analytics to monitor page performance and basic traffic patterns (e.g., page load times, visitor counts). Vercel Analytics is privacy-friendly by design — it does not use cookies, does not fingerprint users, and does not collect personally identifiable information.
Contact us at me@seanclark.dev with any questions about our third-party providers or data practices. Schools seeking a formal data use agreement are welcome to reach out.