Privacy / the boundaries
Your record.
Your decisions.
Local-first does not mean that nothing ever leaves your device. Here is what stays local and what happens when you choose to share.
This educational website
The website has no diary, health-data form, account, analytics tracker or third-party runtime scripts. Viewing the guide does not transfer readings from either diary. Product links open the Chrome Web Store or Telegram without attaching your readings or Telegram identity.
Like other websites, hosting receives technical connection information, including your IP address and browser details. Hosting and reverse-proxy technical logs may record requests. We do not promise that these logs do not exist. Following an external link puts you under that service’s policies.
Chrome: ordinary local use
Readings and settings are stored in this extension’s local browser storage (chrome.storage.local). Ordinary diary use does not upload them to a backend. Reports are generated locally; exporting or printing creates files that you control.
Telegram: ordinary local use
Readings and settings are stored in the Telegram WebView on your device, using IndexedDB with a localStorage fallback. They are not automatically synchronized with Chrome or another device.
When you create and send a report
Choosing Create and send doctor report sends selected readings, optional patient details and signed Telegram launch data to the backend. The backend uses the launch data to identify the recipient, generates the PDF and sends it to your private bot chat. This is an explicit action, not ordinary local diary use.
The report-delivery path does not persist report contents on the backend or create a public PDF URL. Telegram stores the delivered PDF until you delete it. Telegram has its own retention and privacy rules; deleting local readings does not delete that chat document.
CSV downloads and feedback
In Telegram, Download CSV sends the selected readings to the backend to create a temporary file link. The temporary download is separate from PDF delivery and is not a permanent backup. Outside the Telegram WebView, CSV generation can be local. A downloaded file remains wherever you save it.
If you send feedback in Settings, the message you type and Telegram launch data go to the backend so feedback can be delivered with limited user/technical context. Readings, notes, reports and backups are not attached automatically. Avoid putting private health information in feedback.
Mini App opens and technical information
The published Telegram Mini App uses Umami Cloud to count successful opens. Technical connection data, including IP address and browser details, can reach Umami. The sanitized open event does not include readings, notes, reports, backups, Telegram IDs or the launch URL. The educational website does not use this tracker.
Mini App hosting also receives connection information. Technical logs and client error/download events can contain narrow operational metadata; local-first is not a guarantee of zero technical logging.
No automatic sync
Chrome and Telegram maintain separate diaries. JSON import is explicit. The current Telegram WebView says JSON backup is not available in Telegram yet when export is attempted; do not assume that button has saved a backup. Chrome JSON export works locally. See Help for current limitations.
Protect the copies you keep
Clearing browser or Telegram app data, reinstalling an app, uninstalling the extension or changing devices can remove local readings. Make and verify backups where available. JSON transfers readings only, not saved patient details. CSV and PDF are reports, not a restore backup.
Exported files contain health information. Store them carefully, share only with intended recipients and consider whether your chosen file-storage location synchronizes to a cloud service. Deleting the diary does not delete exported files or Telegram documents.
Reviewed against current client code on 10 October 2026. No compliance certification is claimed.