#Privacy and Cookies

Draft: this wording is awaiting privacy and legal review. It describes the current source implementation and does not introduce a consent notice or new cookie.

Photobots runs the simulation in your browser. The public app does not create a visitor account or upload your selected image. Ordinary requests for the site, its JavaScript, worker, WebAssembly engine, documentation, and images still reach the hosting service.

#Browser Storage Used by Photobots

Photobots currently uses browser storage for these purposes:

• Language and interface preferences. Local storage names beginning with photobots.ui.* remember the simulation language, setup choices, and panel choices. photobots-docs-theme remembers the documentation theme.

• Simulation setup and saved archetypes. The photobots IndexedDB database and local-storage names beginning with photobots.archetypes.v1 keep explicitly saved archetypes available for a later visit. The photobots_continuation IndexedDB database keeps the selected image and the latest safe simulation boundary on this device, so an interrupted active simulation can be resumed explicitly after a reload. This data is not uploaded by Photobots.

• Session diagnostics and debug state. The photobots.wasmDebug session-storage name applies only to the current browser session.

• Temporary legacy cleanup. Old photobots_diagnostics_checkpoint_* local-storage names and the photobots_recovery database are retired. A best-effort cleanup removes them after setup becomes interactive.

The current source does not register a service worker or use the Cache API. The current public app does not write the reserved nf_lang language cookie or the reserved photobots.storageChoice.v1 local choice record. Those names remain reserved while the exact language-cookie notice awaits review.

#Clearing Saved Data

Use Clear saved data at the bottom of simulation setup or in the running simulation controls. It clears Photobots language and setup preferences, panel choices, documentation theme, saved archetypes, session debug state, retired diagnostic data, the saved simulation continuation, the retired recovery database, and the nf_lang cookie if it exists.

Clearing saved browser data does not stop, rewind, or erase a simulation that is already running in memory. You can also use your browser's ordinary site-data controls.

#Contact

Questions about this project can be directed to Dave Sag.