To enable data sharing, please follow the below steps:

Apple Health:
1. Open “Health” app on your phone
2. Tap the “Profile” icon on the top right
3. Under “Privacy” section, tap “Apps”
4. Tap on “OMRON connect”
5. Tap “Turn All Categories On” or enable the data you want to share individually

Samsung Health:
1. Open the OMRON connect US/CAN/EMEA app
2. Go to Profile -> App settings
3. Tap on “Samsung Health”
4. Tap on “Manage” button
5. Turn ON “All permissions” or enable the data you want to share individually

If you continue to experience issues, please contact customer service at 1 (800) 634-4350 or Contact Us.

Apple Health
If you agree to read data from Apple Health, the following data will be read:
– Blood pressure – data from OMRON connect US/CAN/EMEA only
– Activity – Steps data

Data read is displayed in the OMRON connect app for the user to track. Data is also stored in the cloud. Activity Steps data is also used for calculating reward points for a premium user.
You can disable the OMRON connect app reading from Apple Health by navigating to Profile -> App settings -> Select “Apple Health” and tap the “Unlink” button.

Google Fit
If you agree to read data from Google Fit, the following data will be read:
– Blood pressure – data from OMRON connect US/CAN/EMEA only
– Activity – Steps & Distance data

Data read is displayed in the OMRON connect app for the user to track. Data is also stored in the cloud. Activity Steps data is also used for calculating reward points for a premium user.
You can disable OMRON connect app reading from Google by navigating to Profile -> App settings -> Select “Google Fit” and tap the “Unlink” button.

Samsung Health
We do not read data from Samsung Health.

Please refer to the “How We Share Your Information” section in our <a href=”/privacy/” target=”_blank” rel=”noopener referrer”>Privacy Policy</a>.

Please refer to the “How We Share Your Information” section in our Privacy Policy.

OMRON does not resell any data we receive. OMRON may use de-identified blood pressure and EKG recordings for future clinical research and feature improvements. All personal information is removed from a user’s blood pressure and EKG readings and stored on our secure and encrypted servers.

External contractors and companies that provide necessary services may have access to some of your information needed for processing, but do not have access to any of your personal identifiable information, your blood pressure or EKG recordings or health history. The vendor that handles payment processing is a good example of this. Such vendors are required by law to protect the information we share with them.

Please refer to “The Information We Collect About You” section in our latest Privacy Policy for more details.

Click here to see our latest Privacy Policy.

Yes. We have implemented reasonable precautions to protect the information we collect from loss, misuse, and unauthorized access, disclosure, alteration, and destruction. Please be aware that despite our efforts, no data security measures can guarantee security.

You should take steps to protect against unauthorized access to your password, phone, mobile device, and computer by, among other things, signing off after using a shared computer or device, choosing a robust password that nobody else knows or can easily guess, and keeping your log-in and password private. We are not responsible for any lost, stolen, or compromised passwords or for any activity on your account via unauthorized password activity.

Yes, OMRON is HIPAA compliant. HIPPAA is the Health Insurance Portability and Accountability Act, with which we are compliant. We take the privacy and security of your medical information seriously. This means we follow HIPAA and HITECH regulations as set forth by U.S. Health and Human Services that require Administrative, Physical, and Technical controls to be in place. We comply with HIPAA requirements to use industry best standards to protect and secure your Protected Health Information collected through our OMRON connect US/CAN/EMEA app.

Our adherence to HIPAA means that all data on our servers is encrypted when it is at rest or in transit. OMRON uses industry best practices such as AES 256-bit server side encryption for customer EKG recordings, and transport layer security (TLS 1.2) to establish a secure link with cloud servers and to encrypt data in transit.

When you select your country as USA or Canada, all data collected from OMRON connect US/CAN/EMEA is stored on servers in the US.

The OMRON app requires specific permissions.

Below is a listing of permissions required for OMRON iOS app and how we use them:
1. Bluetooth: Bluetooth permission is required to allowed to enable communication with OMRON monitors.
2. Location: To enable data transfer in background from OMRON monitors, iOS devices used Apple’s iBeacon functionality. To use this, location permission is required.
3. Camera access: This permission is required because the app allows you to add a profile photo to your account. This is also used when adding images to medications.
4. Photo Gallery access: This permission is required because the app allows you to add a profile photo to your account. This is also used when adding images to medications.
5. System Notification access: This permission is required if you are using HeartGuide™ and need to get notified on HeartGuide™ when your phone receives an SMS, call or mail.

Below is a listing of the permissions for the OMRON Android app and how we use them:
1. Location: This permission is required for device pairing via Bluetooth, which works by identifying nearby external devices through a scanning function.
2. Photos/Media/Files: This permission is required because the app allows you to add a profile photo to your account. Although media and files are typically grouped together with the photos in your smart device, we will not use your media and files.
3. Contacts: This permission is required if you are using HeartGuide™ to display your contact’s name on HeartGuide™ when someone calls or sends messages.
4. Phone Calls: This permission is required if you are using HeartGuide™ in order to send call notifications to your HeartGuide™.
5. SMS: This permission is required if you are using HeartGuide™ in order to read and receive text message (SMS) notifications to your HeartGuide™.

Please note: You do not have to allow access to these permissions. If you wish to review and/or opt out of these permissions, please navigate to your mobile device settings.
OMRON connect US/CAN/EMEA does not track or store your location information.

If you’re pairing or syncing your monitor with an iOS/Android device, you may be prompted to turn on location services. Location access is required by Google to perform Bluetooth communication. Google changed its permission requirements beginning with Android OS 6.0. As a result, the locations permission is necessary to sync your OMRON monitors with your Android device. For more information visit the link below:
https://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-hardware-id

For iOS, location permission is required to support iBeacon functionality of OMRON blood pressure monitors. With this capability, your readings will be transferred to the application without opening the application.
If you deny location services, the app will not be able to sync data from the monitor.

The OMRON connect US/CAN/EMEA app needs the locations services option on your phone to be turned on in order to perform the Bluetooth low energy scans required to sync your monitors.

Google added the locations permission requirement to alleviate concerns that Bluetooth beacons can be used to track your location without your permission during a Bluetooth low energy scan, such as the scan required to sync your monitors. By granting the OMRON connect US/CAN/EMEA app permission to access your location, your monitor will be able to sync, but your location won’t be recorded or tracked by OMRON connect US/CAN/EMEA app.

For more information about Bluetooth technology, visit the Bluetooth Special Interest Group’s website at bluetooth.com.
For details about the Google permission requirements, see Google’s Android 6.0 Changes document.