What is stored
Your progress, notes, verdict, narration preferences and sitting statistics use this browser’s site storage on this device.
SimJury does not send that saved player state to an account or player-state backend.
Plain-language privacy
SimJury has no player accounts or backend player-state service. Progress is useful because it is saved locally; that also means it cannot follow you to another browser or device.
Your progress, notes, verdict, narration preferences and sitting statistics use this browser’s site storage on this device.
SimJury does not send that saved player state to an account or player-state backend.
There is no cross-device or cross-browser sync. Switching browser or device, using a separate browser profile, or clearing SimJury site data removes your access to the saved information there.
When narration is on, your browser can fetch public audio clips from GitHub Releases. GitHub can observe request metadata, request timing and the requested clip IDs.
Those requests do not contain your saved progress, notes, verdict or statistics. Clip IDs map to lines in SimJury’s public, pre-authored case corpus.
Static pages and assets are served through Cloudflare. Like any CDN, Cloudflare receives ordinary HTTP request metadata needed to deliver them.
SimJury does not add analytics or tracking code, and does not attach your locally saved progress, notes or verdicts to those requests.
Daily cases are fictional and pre-authored. Juror responses and outcomes are produced deterministically in your browser from the authored case and your choices.
There is no runtime generative AI, live juror or hidden human responding during a sitting.