Last materially updated: August 13, 2026
This authoritative policy is currently provided in English. The localized route is temporarily noindex until a legally reviewed translation is available.
1. Scope
This policy describes data handling visible in the current MyZenCheck website and Azure Functions code. It does not claim controls that are not implemented in the repository.
2. Data used in the tongue-check flow
- image bytes submitted for the initial image-quality check;
- the accepted tongue photo uploaded to Azure Blob Storage;
- a generated random blob name and original sanitized filename;
- model outputs and the educational result returned to the browser;
- optional country/continent context used for recommendations where supplied;
- browser-side session or local storage used for result history and preferences.
3. Photo processing and storage
A submitted photo does not stay only on the device. The browser sends it over HTTPS for validation, obtains a time-limited Azure upload URL, uploads it to Azure Blob Storage, and sends the resulting blob URL to Azure-hosted analysis services.
When the analysis request finishes, including after an analysis error, the API automatically requests deletion of the submitted blob. Deletion failures are logged but cannot be ruled out, so this is a best-effort cleanup control rather than a permanent-deletion guarantee. Clearing browser history removes browser-stored results; it does not trigger or prove server deletion.
4. Purposes
- validate image quality and provide the requested educational analysis;
- operate, secure, troubleshoot, and prevent abuse of the service;
- store browser preferences and result history;
- measure traffic and usability only when optional analytics consent is granted.
Uploaded photos must not be reused for model training unless a separate, explicit and properly recorded consent process applies. The current public flow does not establish such consent merely by submitting a check.
5. Processors and sharing
Azure services process and store data needed for the product flow. Optional Google Analytics 4 and Microsoft Clarity load only after analytics consent. MyZenCheck does not state that it sells personal information. Data may be disclosed where legally required.
6. Cookies and browser storage
Essential browser storage supports language, session flow, result history, and consent choice. Optional analytics can be declined without disabling the educational check, and the privacy-settings control can be used to change that choice.
7. Your requests
You may request information, correction, objection, restriction, portability where applicable, or deletion by contacting gabriela.sikorova@myzencheck.net. Because the current flow is not consistently tied to an authenticated identity, include the approximate upload time and any available blob or request identifier; MyZenCheck may need to verify what can be located without exposing another person's data.
8. Security and limitations
Transport uses HTTPS and storage/services are hosted on Azure. No system is risk-free. Avoid submitting identifying material beyond the tongue image required for the check.
9. Children
The service is not intended to assess children. A parent or guardian should take pediatric concerns to an appropriately qualified professional.
10. Contact
Privacy and data requests: gabriela.sikorova@myzencheck.net. General contact details are available on the contact page.