Simple questions,
direct answers.

After you sign in, structured result rows you confirm during review are written to the encrypted cloud data area for the current account, and any browser where you sign in with that account can read them back. Original PDFs, photos, page images, full OCR text, and encrypted-PDF passwords are not uploaded as attachments. Imports kept only in this browser session stay in the current tab and disappear when it closes. The cloud data area is account-scoped encrypted storage, not end-to-end encryption.

On the web you can choose a PDF file or a photo. Text extraction and OCR run locally in your browser; passwords for encrypted PDFs are used only locally. Before anything is saved you must review the identity details and confirm each result row; reports without verifiable identity or valid result rows stop safely and are not guessed. There is currently no direct laboratory-account connection.

Web reminders work only in the browser where you set them, and only while the reminders page stays open; they do not fire after you close the tab, switch browsers, or move to another device. Browser notifications are optional and require permission in that browser. Settings are stored in that device’s browser local storage and are lost if you clear site data or switch browsers. You can download a calendar file (.ics) at any time and import it into your system calendar for reminders that do not depend on the page being open. PearHealth has no remote push server and sends no email or SMS reminders.

In Data > Records, only after you click export does the browser build a CSV of your confirmed structured records and download it to this device. You decide where the file is stored, sent, or deleted; PearHealth does not automatically receive a copy, and no server-side export is performed.

Deleting a single result or a whole report happens in Data > Records and asks for one confirmation; deletion is permanent. Deleting the entire account and associated cloud data requires re-authentication, submitting the request, waiting out a cooldown of at least 5 minutes, then completing a second confirmation. After confirmation the request runs in the background (PROCESSING): the status only ever shows “processing”, immediate completion is not guaranteed, and it is never described as “completed” before it actually is.

After signing in again, you can read the cloud-encrypted structured records that were successfully saved to the account. Not restored: original PDFs / photos, imports that lived only in a now-closed tab session, reminder settings saved in the previous browser, and local caches. Export the CSV periodically and store important materials yourself.

No. The current web app has no direct connection or automatic import for Apple Health / HealthKit, Oura, or CGM vendors such as Dexcom, and it pulls no data from those sources. Data sources on the native iOS app are a separate path; there is no web-side connector into the web account. To add values on the web, enter them manually.

No. PearHealth is a record-keeping and education tool; it does not provide diagnosis, treatment, or individualized prescriptions. Action plans are generated from versioned rules and confirmed data, and generative AI is not used in place of medical judgment; your personal data is not uploaded to a model. Supplement brands, doses, and courses are never automatically given from a single blood test. Do not start, stop, or change medications, supplements, diet, or treatment based only on website content.