Doctordle logoDoctordle

Legal

Privacy Policy

This policy explains what Doctordle stores locally in your browser, what limited usage data may be generated by the app, and how that information is handled.

Overview

Doctordle is a browser-based medical education game. The app is designed so that your day-to-day puzzle progress stays primarily on your own device. This page describes the information the app stores locally, the limited analytics event structure present in the codebase, and the choices you have when using the site.

Information stored on your device

Doctordle currently uses browser localStorage to save puzzle progress and review cards on the device you use to play. This can include:

  • daily puzzle completion state, including whether a case was solved or the answer was revealed
  • attempt history tied to a dated daily case
  • review cards generated from completed daily or bonus cases

This local data is stored under a Doctordle-specific browser key and is meant to power features such as resuming a case, showing archive progress, and reopening saved review cards on the same device.

Cookies and server-side progress

The current app includes a server-side progress reader interface, but the repository's present implementation returns empty progress and does not actively restore a server-side cookie-based profile. In other words, the live game flow described in this repository currently relies on browser-local storage rather than a persistent server account system.

Analytics and usage events

The codebase defines a client-side analytics adapter and structured event builders for actions such as daily submits, hint reveals, archive views, bonus completion, and review library actions. The site also loads Google Analytics through the Google tag to understand high-level usage patterns.

The analytics schema is also intentionally restrictive. It is designed to reject payloads that include raw answer text, raw query text, review card text, or snapshots of local storage. The intent is to keep event collection limited to high-level product usage signals rather than full study content.

What Doctordle does not ask you to submit

Doctordle is built for study and exam-style reasoning. You should not enter real patient records, protected health information, or other sensitive medical data into the app. The product is not intended to collect or process that kind of information.

Your choices

  • you can clear your browser storage to remove locally saved progress
  • you can stop using the app at any time
  • if you have questions about the current implementation, you can use the public repository issue tracker linked from the Terms page