CodePeek

Privacy & data

Last updated: 12 November 2026. CodePeek uses data to run puzzles and optional accounts, handle voluntary submissions, and measure website visits and performance. Website analytics and advertising measurement are separate from the optional puzzle counts below. No payment details or user-submitted code are collected by this app.

Puzzle progress

Guest checked answers, first-attempt results and retry counts stay in this browser’s local storage. No account is needed. When signed in, checked answers, attempt counts, latest results and first-attempt accuracy are stored privately with your account in Cloudflare D1 and loaded on your other devices. Account answers are not copied into browser storage. Reset them in the practice sidebar or clear CodePeek site storage in your browser. The homepage’s three worked examples keep selections in page memory only; they do not save progress or submit puzzle-usage events. Website-visit and performance measurement still apply. Reloading clears those selections. The public type-coercion and array methods quizzes also keep attempts and scores in page memory only, without saving practice progress or sending puzzle-usage events. Sharing sends only a fixed public challenge URL, never your answers, score or account information. Native sharing is used when available, with clipboard or manual-copy fallbacks. Both classroom embeds use the same memory-only quiz behavior, without loading account or saved-progress state. Refreshing an embed starts a fresh quiz. The printable learner sheets have no answers; separate, publicly accessible teacher keys reveal the explanations. We do not collect names or handwritten predictions on printed sheets. Website-visit and performance measurement still apply to lesson resources and embeds.

Optional accounts

You can register with a private username and password. No email or Google identity is collected or verified, and a username does not prove anyone’s real-world identity. Google authorization endpoints remain retired. Guest puzzle data, launch interest and anonymous feedback remain separate. Guest progress is imported only with your explicit consent in Account; the local copy is retained. A random browser source identifier and per-puzzle imported-count high-water marks prevent duplicate imports. Existing account first/latest results win overlaps, while new puzzles retain their guest results. Distinct account answer IDs make retries of network submissions idempotent. These receipts contain no answer payload.

We store the username, a salted scrypt password hash, a hash of a random recovery key, account creation time and hashed session tokens with expiry and activity times in Cloudflare D1. Raw passwords and recovery keys are not stored. Credentials are sent only to our own account API over HTTPS. Keep your username and the recovery key shown after registration somewhere private. Recovery requires this key and rotates it; there is no email reset or manual identity recovery. If you lose both your password and key, we cannot restore access.

Sessions use secure, HTTP-only, same-site cookies and expire after one day of inactivity or seven days total. Sign out removes the current session. Changing or recovering a password invalidates all older sessions and keys. Up to five active sessions are retained. Expired sessions are removed on later account submissions. Account forms have same-origin checks and hourly network and identifier limits; hashed rate-limit records expire after a day during subsequent requests.

Account progress, import high-water marks and retry receipts remain until reset or account deletion. Reset saved progress in the practice sidebar while signed in to permanently delete these records on all devices. A reset also invalidates old pending writes. Guest progress is not deleted by an account reset and can be explicitly re-imported afterwards. Resetting guest progress clears its browser source identifier. In Account, use your current password to permanently delete credentials, all sessions and all account progress, import records and retry receipts, or recover first if you forgot it. Sign-out hides account progress without copying it to local storage; deletion leaves separate guest browser progress intact. Other open tabs clear account progress on sign-out or their next focus/server request. Avoid leaving a signed-in session unattended on a shared device. Clear that in practice or your browser settings; launch interest can be withdrawn separately below. No public profile or account directory is provided. Internally flagged QA accounts are excluded from customer adoption counts.

Optional puzzle usage counts

Puzzle-count submissions to our /api/usage endpoint are off until you allow them in this browser, in practice or below. The choice is saved in local storage as codepeek-measurement-v1. With permission, we store daily aggregate counts of puzzle starts (first choice selected per attempt), checked answers and whether they were correct, and all 15 puzzles explored. These count records contain the day, event type, puzzle ID where applicable, result and count—not an account ID, email or submitted code. Counts are not unique people. Turning counts off stops future puzzle-count submissions from this browser; it does not remove existing daily totals. Usage data older than 90 days is removed during subsequent interest or feedback submissions.

This choice does not control Brainer website-visit analytics, Cloudflare performance measurement, hosting logs or Meta advertising measurement.

Website visits and performance

Our hosting platform, Brainer, adds a website-visit script (/_v.js) outside the application code. It sends the current page path and query string, plus the initial referring page when available, to the same-site /_v endpoint. It also counts page-path changes during navigation. The current script skips these submissions when the browser’s Do Not Track value is 1; that is not a site-wide opt-out.

Cloudflare also loads a performance beacon from static.cloudflareinsights.com and sends reports to /cdn-cgi/rum. Observed reports include page location, a per-page-load identifier, browser information, navigation timings and memory metrics. These visit and performance measurements run independently of puzzle-count permission, including on account, privacy and embedded quiz pages. Network requests also expose connection information to the hosting infrastructure. Do not put passwords, recovery keys or other private information in page URLs.

These platform measurements are managed outside our application database. The application’s 90-day puzzle-count cleanup does not apply to platform records. The puzzle-count buttons are not a control for them.

Meta advertising

CodePeek advertises through Meta, which measures ad delivery and interactions on Facebook and Instagram. Our current application code does not load a Meta browser pixel or send server-side Meta conversion events, and our live browser check did not observe a Meta pixel request. Connected platform advertising reports can nevertheless show pixel activity; we have not verified the event payload or source behind that reported activity. This is not a guarantee that platform-level advertising measurement is absent. Allowing or declining puzzle counts does not grant or withdraw permission for Meta measurement. You can manage advertising preferences in Meta’s own services.

Launch interest

If you opt in, we store your email address, the version of your consent, a withdrawal-code hash, and submission time in our Cloudflare-hosted database. This is only for news about the upcoming $9 USD one-time pack of 45 additional puzzles. No payment is collected. Joining does not send an email now; email delivery is not connected yet.

Keep the withdrawal code shown after signup. Use it below to delete your email from the list. If you lose it, submit your email on the interest form again to get a new code, then withdraw here. Emails expire after 12 months and are removed during subsequent interest or feedback submissions. CodePeek does not sell your email or share it with advertisers.

Withdraw launch interest

Learner feedback

Feedback is optional and requires your agreement. We store the source and category of your report, your optional note, and submission time. Explanation feedback also includes the puzzle ID and your “clear” or “confusing” rating. Upcoming-pack feedback includes the pack ID and a contents, pricing, or purchase / next-step category; you can send it before playing a puzzle. No account or email is required. We use these reports to improve explanations and the pack experience, not for launch notifications. Please don’t include personal information or payment details. Feedback is stored privately for up to 90 days, with deletion during subsequent interest or feedback submissions.

Security and hosting

Cloudflare hosts the app and database. To limit form abuse, request counts use a one-way hash of network address and the current hour; these records are removed after a day on subsequent API requests. We do not store raw IP addresses in the application database. Hosting infrastructure may process standard request logs for operation and security. Public feedback is not displayed. The website analytics, performance beacon and advertising distinction are described above; these are separate from the application’s abuse-prevention records.

Contact

For privacy or data questions, email codepeek@brainer.one. Please don’t send passwords, recovery keys or payment details.

Back to puzzles