Health App

Public policy

Privacy Policy

Effective September 30, 2026

Health App is an invitation-only private beta that helps people keep a personal health record and review selected information from services they choose to connect or import. This policy explains what the beta handles, why it is handled, and the choices available to participants.

Information the app handles

  • Account information. The app uses Google Identity Platform and Firebase Authentication for invited email-address accounts, password recovery, sessions, and account identifiers.
  • Your saved record. Information you confirm may include personal record details, supplement or health-product Cabinet entries, and supported health measurements or nutrition values. Saved records are associated with your account.
  • Beta feedback. Suggestions you submit, their status, and related administrative notes may be retained as beta history. The app asks participants not to include health, password, or account information in suggestions.
  • Operational information. The service may process limited technical information needed for security, abuse prevention, reliability, and troubleshooting. The application is designed not to log health measurements, provider responses, authentication tokens, or OAuth credentials.

Connected services and imports

Connections are optional and are initiated by you.

  • Google Health. When you connect Google Health, the server stores the connection credentials in encrypted form. The current production feature can request a short, read-only aggregate Steps preview. Preview results are displayed in the app and are not saved as health records. If a confirmed import feature is enabled in a future beta release, this policy will be updated before broader use.
  • Withings. For eligible beta participants, the app requests the Withings user.metrics permission to preview recent Weight measurements. Nothing is saved until you review and confirm an import. Confirmed daily Weight records and their Withings provenance are stored in your personal record. Connection credentials are encrypted on the server.
  • Cronometer. When you select a supported Daily Nutrition CSV, the browser reads it locally. The raw file, filename, and unsupported columns are not uploaded or retained. Only the dates and supported nutrition values you review are sent to the server after you confirm the import, then stored in your personal record with Cronometer provenance.

Google, Withings, and Cronometer operate under their own privacy policies and terms. Health App does not control their independent collection or retention practices.

Medication and product label photos

If you choose the label-reading feature and give consent for that read, the browser removes the original filename and metadata, re-encodes the selected images, and sends them through the protected Health App backend to Google Cloud for text extraction and field suggestions. Health App does not save the photos or raw extracted text. Only fields you review and confirm are saved to your Cabinet. Google may retain provider inputs or outputs for security and abuse monitoring under its applicable terms, so you should cover names, addresses, prescription numbers, and other details that are not needed for the label read.

Private documents and demo information

When you select Upload privately, supported PDF, JPG, and PNG documents are stored with your authenticated personal record. The app keeps the original bytes, filename, file type, size, and upload/update times so you can view, download, rename, or permanently delete the document. Documents are not analyzed or interpreted. DICOM and other file types are not accepted. Synthetic demo records stay separate from your personal record and cannot store documents.

How information is used and shared

Information is used to authenticate you, provide the features you request, maintain your personal record, protect the service, and administer the private beta. Health App does not sell personal or health information and does not use it for advertising. Data is shared with service providers only as needed to operate requested features, including Google Cloud and Firebase, or when required by law.

Storage, security, and retention

Saved personal records are protected by account-based access controls. Provider credentials are kept server-side and encrypted. Network responses containing account or health information use no-store controls, and the installable web app is designed not to cache health records for offline use. No system can guarantee absolute security.

Confirmed records, private documents, and beta history may be retained while your account remains active or as needed to operate and protect the beta. Disconnecting a provider removes the stored connection credentials for that provider but does not automatically delete information you previously confirmed for import. Provider-side retention is controlled by the provider. Deleting a private document in Imports permanently removes its stored file and metadata from the active service; limited backup copies may age out under provider backup processes.

Your choices

You may decline an optional connection, cancel before confirming an import, disconnect a connected provider, or stop using the beta. Self-service account export and complete account deletion are still being developed. To request access, correction, export, or deletion of your Health App information, contact health@ljgentile.com. Some limited records may be retained when reasonably necessary for security, legal obligations, or backup integrity.

Health information and medical care

Health App is a personal record tool, not a healthcare provider. It does not diagnose, treat, or replace advice from a qualified healthcare professional. Do not use the app for an emergency.

Policy changes and contact

This policy may change as the private beta evolves. The effective date above will be updated when material changes are published. Questions and privacy requests may be sent to health@ljgentile.com.

Health App home ยท Terms of Service