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; no public gallery or account photo history is created. Depending on configuration, individual scans may be archived in private Cloudflare R2. A completed paid PDF and web visualization are kept on the private results volume for a bounded period so a buyer can recover a download after a restart.
A completed paid report is retained for up to 72 hours by default; private skin-result links for up to 12 hours, and hairstyle-vote links for up to 24 hours. Profile context remains memory-backed for up to 7 days. Leads, analytics, and private R2 objects are outside those TTLs and can require manual deletion.
Not in this codebase. An upload is used to process the current analysis request, not to build a training dataset.
The text-AI provider receives derived metrics and report context. OpenAI receives the portrait when the product creates a potential visualization, classifies the best presentation, or generates hairstyle options. Stripe handles payment and the email provider handles selected PDF delivery. Uploads are not sent to Telegram by default; private operational messages identify the source site without a photo unless media delivery is explicitly enabled.
There is no deletion dashboard yet. Temporary report and share media expire under the TTLs above; leads, analytics, and R2 records can require manual handling. Send a deletion request 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.
