This page describes the actual code-path behavior: what is stored temporarily, which external services are involved, and which parts of the flow are optional.
The photo is uploaded to the backend for the active analysis flow. The codebase does not create a permanent user photo gallery or a long-term account history of uploads. Async PDF jobs keep the finished PDF and web visualization in server memory for a limited window so the download can be retried.
Async report jobs are pruned by an in-memory TTL. By default that is up to 1 hour for a completed report. The same-identity profile context used to keep care-plan recommendations consistent is also in-memory only and is pruned after 7 days by default or sooner on server restart.
Not in this codebase. An upload is used to process the current analysis request, not to build a training dataset.
If AI summaries are enabled, the app sends only derived metrics, module summaries, and care-plan context to Anthropic, not the raw uploaded photo. If you enable email delivery, the PDF is sent through Resend. After this update, the website flow does not forward uploads to Telegram by default.
There is no account dashboard for manual deletion yet. Most storage in this codebase is temporary and memory-backed, so it expires automatically. Manual requests can go through the contact channel on the site.
No. It is not a medical diagnosis service, and it is not designed to produce a hot-or-not face rating. The product is meant to surface visible skin signals and support more practical care decisions.
