Plum Solutions · CherryHealth
CherryHealth - Pocket Health privacy policy
Effective date: 7 October 2026
Who we are and how to contact us
This policy applies to CherryHealth - Pocket Health (health.cherry.cherry_health_patient), published by Plum Solutions, and the CherryHealth website. For privacy questions, access or correction requests, or help with deletion, contact sinchwara@gmail.com. The public policy is available at https://www.cherryhealth.tech/privacy.
Information used to provide your care
Depending on the features you use, CherryHealth processes your name, phone number and other contact details, date of birth, health profile, symptoms, consultations, messages and attachments, care plans, prescriptions, health records and measurements. We also process order and payment status, notification tokens, and technical, security and audit information needed to operate the service. Information you submit is associated with your account and patient record.
Optional demo access
Try demo opens a separate sample record without an account, phone verification or payment. Demo vitals, messages and selected attachments are processed locally and are not sent to our backend or care team. Demo record changes are cleared when you leave or restart the app; source files on your device remain. Device permissions are real and optional, and remain subject to your system settings. Demo does not place live calls or orders, charge money or provide medical advice. Exit demo to use your own account.
Why we use this information
We use information to verify account access, maintain your patient record, show your health history, connect you with your care team, fulfil care and pharmacy requests, handle payments and essential notifications, and protect the service. Recorded measurements support your records and discussions with clinicians; the Vitals import feature does not diagnose conditions or replace professional medical assessment.
Optional Health Connect access on Android
You can use manual vitals entry without Health Connect. Only when you choose Sync Health, select measurements and grant system permission does CherryHealth read those permitted measurements from the last seven days. The Android app requests read access to heart rate, blood pressure, blood oxygen, body temperature, weight, height and blood glucose. It does not request respiratory-rate access, write access, background access, or extended health-history access. No measurement is selected by default.
Purpose of each imported measurement
Heart rate records your pulse in Vitals Latest and History. Blood pressure keeps systolic and diastolic readings together in your blood-pressure log. Blood oxygen records oxygen-saturation readings. Body temperature records dated temperature readings. Weight and height preserve dated body measurements in your health record. Blood glucose records dated glucose readings. These imports save manual re-entry and let you review your measurements with your care team. In Fitness, optional heart-rate imports add readings to your activity history; Android does not import steps, workouts or routes.
What happens when you sync
Selected, permitted readings, their dates and source information are uploaded over HTTPS to your CherryHealth patient record and displayed in the relevant history. Authorised care and operations personnel can access records as needed to provide and support your care. Access is read only and initiated by you. Denying a measurement does not prevent you from using manual entry or importing other permitted measurements. On iOS, optional Apple Health imports follow the choices presented in the app and Apple Health permissions.
Permissions, photos and connected devices
Photos and documents are selected using system pickers; the app does not request broad photo or video library access. Camera and microphone permissions support features you choose such as attachments, calls or camera estimates. Camera estimates are labelled as estimates for context, not validated clinical measurements. Bluetooth permissions support connecting a device you choose. You can revoke permissions in your device settings.
Sharing and protection
Information is shared with authorised clinicians and personnel involved in delivering and supporting your care, and service providers needed for hosting, communications, calls, payments and security. It may also be disclosed when required by applicable law. Health information, including Health Connect data, is not sold or used for advertising or shared with data brokers. Account access controls and encrypted network connections protect transfers. Avoid sending passwords or one-time verification codes to support.
Retention and your controls
Information saved to your patient record remains there until it is removed or a deletion request is processed. Revoking Health Connect access stops future imports but does not delete copies already saved in CherryHealth or records held by Health Connect. You can remove a reading from Vitals History; related clinical or audit records may remain. Account deletion requests are reviewed after verifying ownership, including whether clinical, payment, security or legal records must be retained. Retained records remain subject to access restrictions; ask the privacy contact about the records and retention applicable to your request.
Request access, correction or deletion
You can request profile corrections by contacting us and request account deletion from Account using Request account deletion. If you cannot sign in, use https://www.cherryhealth.tech/account-deletion or email sinchwara@gmail.com. The request form records a request for review and ownership verification; submitting it is not instant deletion. You can also contact us to request access or an export and ask about retained information. In Android settings, open Health Connect, App permissions, CherryHealth to revoke future imports. On older Android versions, open the Health Connect app to manage permissions.
Policy updates
The effective date below identifies this policy version. Updates are published at the same direct privacy-policy URL. Changes to sensitive data access still require the applicable in-app disclosure and permission.