Privacy

No cookies, no accounts, nothing that identifies a visitor stored on their device. This page lists everything CaloView and this site do with data, including the usage telemetry the simulator sends.

• The app remembers which panels were open and which onboarding tips have been seen, in the browser's local storage. That stays on the visitor's device and is never sent anywhere.
• While the simulator is open, it sends an event when playback starts or stops, with the frame rate, browser/screen info, and the simulation options in use. Nothing is stored on the device — the session id in each event is random and lives only in memory for that visit. Used to understand real-world usage during the beta.
• Each of those events also carries a visitor code: a one-way hash of the IP address, computed on the server under a secret key that never leaves it. The IP address itself is never stored, and the code cannot be turned back into an address. It stays the same for the same address over time, which is what makes it possible to count how many distinct people use the beta and to leave out the developer's own visits. Kept for as long as the telemetry logs.
• The hosting provider, OVH, logs standard web server request data (IP address, browser, page requested) for security and to operate the service, kept for one year.
• Feedback sent by email is between the sender and the recipient — sent by the visitor's own mail client, not collected by the app.
• To ask what's logged about a visit, or to have it deleted, write to contact@caloview.com. The visitor code above is what makes it possible to find and remove one visitor's telemetry events. Since the logs live on the hosting provider's infrastructure, fulfilling the request may require relaying it there.

Cyril Deguet, contact@caloview.com, is responsible for this site and the data described above. Last updated 9 August 2026.