Freshworks' commitment to HIPAA Compliance
As a SaaS-based product provider, Freshworks offers several products. There could be instances when customers may use some of our products to process electronic Personal Health Information (ePHI) in their business operations. As per the Health Insurance Portability and Accountability Act (HIPAA) of 1996, should our customers get categorized as either Covered Entity or Business Associate, Freshworks may extend support to their compliance with HIPAA by mutually executing a Business Associate Agreement (BAA).
The scope of BAA is limited to Freshdesk Support Desk, Freshchat, Freshdesk Contact Center, and Freshdesk Omnichannel products offered by the Freshworks Freshdesk suite. The processing of any ePHI in any of our other products is not recommended and will not be covered within the scope of our BAA.
This document sets forth the Secured Operating Environment (SOE) that is Mandatory for Customers (either Covered Entity or Business Associate) to adhere to while using Freshchat to process ePHI. The validity of our BAA is subject to continued adherence by the Customers to the specifications mentioned in this document. Further, Freshworks is not liable for the Customer's usage of their custom mailbox and/or any Apps (as defined in the Customer's agreement with Freshworks). We encourage Customers to independently configure these for their continued compliance with HIPAA.
Secure Operating Environment
- Trusted IP: Allow specific IP addresses to enforce access to your Freshchat account only from the sources that are authorized by you. Know more.
- Restricted access: Configure role-based access controls to ensure that access to your agents is limited based on their job responsibilities. Know more.
- Identification and Authentication: Enable SAML SSO for users to access their Freshchat account with your unified identification and authentication system and validate users logging into the portal using your script. SAML is a mechanism used for communicating identities between two web applications. It enables web-based Single-Sign-On, eliminating the need for maintaining various credentials for various applications and avoiding identity theft.
- Data Sanitization: In addition, customers can truncate ePHI data in the patient conversations by using the data truncation feature in Freshchat, which accepts regex patterns. Customers have to reach out to the product support team (email@example.com) with the regex pattern to enable it on behalf of the Customer. The responsibility for the correctness of the regex patterns will remain with the Customer.
- Sanitization of User Properties: Responsibility of the Customer to sanitize before sending it to Freshchat
- Sanitization of Chat Messaging: Supported, regex-based truncation applied by Freshchat.
- End-Point Security: Ensure the end-point systems used by your agents are hardened and secured to protect the health care data they process. The systems shall be identified to specific agents, authenticated, configured to be automatically locked down in case of idleness, and secured from malware.
- Features and options to be configured:
- Disable FullContact Enrichment: In HIPAA compliance mode, the user's information should not be fetched from social media using Full contact. Hence a HIPAA-compliant customer should opt out of the user enrichment option from FullContact through GDPR Settings in their Freshchat account.
- GDPR settings to be mandatorily enabled by the Customer: Freshchat customers should enable all three GDPR settings:
- Turn on opt-out of analytics
- Turn on opt-out of saving user IP address and
- Turn on opt-out of user enrichment done through fetching social media data from Full-Contact.
- Co-Browsing: Customers should not enable co-browsing capability to comply with HIPAA.
- CSAT: The Customer should keep the option "Ask for additional feedback after the user has rated the interaction" disabled. Enabling it will have the risk of ePHI data being shared in the CSAT survey, which is not protected by data sanitization/masking in Freshchat., Customers should not enable this option to adhere to HIPAA Compliance.
- Email Campaigns: If the Customer uses the email campaigns feature, they need to ensure they configure a custom' reply to' email address that does not come back to Freshworks but to a customer-managed email address.
- Integrations & Apps not to enable: Any integrations or apps with third-party applications that send user data or conversations data outside Freshworks will not be covered under the HIPAA scope.
- Notifications to Visitors: As these notifications go through sub-processors like Google-Firebase, and Apple Notification service, who don't sign a BAA, customers should disable the push notification service for visitors using the below instructions to comply with HIPAA
- Turning off Notification to Visitors for Web:
The default state is on and can be disabled by customers using the following config code during widget init. Steps to disable browser notifications:
- Turning off Notification to Visitors on Mobile (mobile SDK):
The default state is off unless explicitly enabled by the Customer with customer-managed keys. Please do not enable this to comply with HIPAA.
- Turning off Notification to Visitors for Web:
For information on the information security practices followed at Freshworks, please refer to https://www.freshworks.com/security/. If you have any questions, please reach out to firstname.lastname@example.org.